Some test calls failed in the last 24 hours

35 of 44 test calls answered in the last 24 hours.

04:00 UTC: 1 of 1 answered
05:00 UTC: 1 of 1 answered
06:00 UTC: 1 of 1 answered
07:00 UTC: 1 of 1 answered
08:00 UTC: 1 of 2 answered
09:00 UTC: 2 of 2 answered
10:00 UTC: 1 of 2 answered
11:00 UTC: 1 of 2 answered
12:00 UTC: 1 of 2 answered
13:00 UTC: 1 of 2 answered
14:00 UTC: 1 of 2 answered
15:00 UTC: 1 of 2 answered
16:00 UTC: 1 of 2 answered
17:00 UTC: 2 of 2 answered
18:00 UTC: 2 of 2 answered
19:00 UTC: 1 of 2 answered
20:00 UTC: 2 of 2 answered
21:00 UTC: 2 of 2 answered
22:00 UTC: 2 of 2 answered
23:00 UTC: 2 of 2 answered
00:00 UTC: 2 of 2 answered
01:00 UTC: 2 of 2 answered
02:00 UTC: 2 of 2 answered
03:00 UTC: 2 of 2 answered

24 hours agoNow

All answered
Some missed
None answered
No test calls

Vicem places automated test calls into its call-answering service around the clock and checks that each one is answered. This page shows those results as they come in, not a self-reported uptime figure. It never shows anything about the people who use Vicem.

Part by part

Answering calls (phone network)Some checks failed in the last 24 hoursDegraded
Answering calls (app and web)Calls are answeredOperational
Live asks to your phoneNot enough recent activity to measureUnknown
Messages and InboxNot enough recent activity to measureUnknown
Owner appThe app is reachableOperational

Incidents, updates and RSS: status.vicem.ai. It is hosted apart from Vicem, so it stays up when we are down.