Checked every minute from 3 places around the world, outside Voznest's own servers. Last check: 27 Oct, 08:02 UTC (DFW · MIA · LHR).
Systems
90-day uptime
Core
Website & web app99.43%Operationalvoznest.com and the app in the browser, desktop and phone apps
API99.45%OperationalSign-in, hubs, channels, settings — everything the apps ask for
Database100%OperationalWhere accounts, messages and hubs are stored
Messages & realtime
Realtime connection99.45%OperationalNew messages, typing, presence and notifications as they happen
Message servers99.81%OperationalThe processes that deliver messages and keep everyone in sync
Voice & video
Voice & calls99.45%OperationalJoining voice rooms and calls, streams and watch together
Voice relay (TCP fallback)99.70%OperationalHow calls connect from networks that block UDP (most calls use UDP, which can't be tested from here)
Media server100%OperationalForwards voice, cameras and screens between participants
Files, downloads & email
Files & media100%OperationalUploads, images, avatars and video (cdn.voznest.com)
Downloads & updates99.45%OperationalInstallers and automatic app updates
Email100%OperationalVerification, sign-in and security emails
90 days agoToday
From around the world
What each monitoring location saw in the latest check.
Website & web app
API
Realtime connection
Voice & calls
Voice relay (TCP fallback)
Files & media
Downloads & updates
Email
US West DFW
✓ Answering
✓ Answering
✓ Answering
✓ Answering
✓ Answering
✓ Answering
✓ Answering
✓ Answering
US East MIA
✓ Answering
✓ Answering
✓ Answering
✓ Answering
✓ Answering
✓ Answering
✓ Answering
✓ Answering
Europe LHR
✓ Answering
✓ Answering
✓ Answering
✓ Answering
✓ Answering
✓ Answering
✓ Answering
✓ Answering
Insights
99.70%Uptime, last 30 days
12 minAverage time to recover
3Incidents, last 30 days
Daily summary · 27 Oct, 00:10 UTC
The Voznest platform has been available with high uptime over the last 24 hours. All services have been performing normally, with no notable slowdowns. There were no incidents reported during this period.
Started 25 Oct, 18:15 UTC · Lasted 9 min · Affects: Website & web app, API, Realtime connection, Voice & calls, Downloads & updates, Voice relay (TCP fallback) · Detected automatically
Users were unable to access Voznest services, including the website, API, and voice features, due to an issue with the machine or its network at the hosting provider. The disruption lasted for a period of time and affected multiple regions. The cause of the issue is still being investigated as the server and its components were unresponsive. The issue has been resolved and services are now available.
Timeline (4)
Resolved
Resolved. It lasted 9 min; everything has been working normally since.
Monitoring
Recovered — everything answers again. Watching it for a few minutes before closing (9 min so far).
Investigating
Update: Nothing on the server answers — not the website, not the API, not the voice relay that's reached directly. The machine or its network at the hosting provider is down. • Website & web app: failing from US West (Cloudflare error 530 (tunnel down)), US East (Cloudflare error 530 (tunnel down)), Europe (Cloudflare error 530 (tunnel down)) • API: failing from US West (Cloudflare error 530 (tunnel down)), US East (Cloudflare error 530 (tunnel down)), Europe (Cloudflare error 530 (tunnel down)) • Realtime connection: failing from US West (Cloudflare error 530 (tunnel down)), US East (Cloudflare error 530 (tunnel down)), Europe (Cloudflare error 530 (tunnel down)) • Voice & calls: failing from US West (Cloudflare error 530 (tunnel down)), US East (Cloudflare error 530 (tunnel down)), Europe (Cloudflare error 530 (tunnel down)) • Voice relay (TCP fallback): failing from US West (no answer within 8 s), US East (no answer within 8 s), Europe (no answer within 8 s) • Downloads & updates: failing from US West (Cloudflare error 530 (tunnel down)), US East (Cloudflare error 530 (tunnel down)), Europe (Cloudflare error 530 (tunnel down))
Investigating
We're looking into it. Nothing on the server answers — not the website, not the API, not the voice relay that's reached directly. The machine or its network at the hosting provider is down. • Website & web app: failing from US West (Cloudflare error 530 (tunnel down)), US East (Cloudflare error 530 (tunnel down)), Europe (Cloudflare error 530 (tunnel down)) • API: failing from US West (Cloudflare error 530 (tunnel down)), US East (Cloudflare error 530 (tunnel down)), Europe (Cloudflare error 530 (tunnel down)) • Realtime connection: failing from US West (Cloudflare error 530 (tunnel down)), US East (Cloudflare error 530 (tunnel down)), Europe (Cloudflare error 530 (tunnel down)) • Voice & calls: failing from US West (Cloudflare error 530 (tunnel down)), US East (Cloudflare error 530 (tunnel down)), Europe (Cloudflare error 530 (tunnel down)) • Voice relay (TCP fallback): failing from US West (no answer within 8 s), US East (no answer within 8 s), Europe (no answer within 8 s) • Downloads & updates: failing from US West (Cloudflare error 530 (tunnel down)), US East (Cloudflare error 530 (tunnel down)), Europe (Cloudflare error 530 (tunnel down))
Started 25 Oct, 17:57 UTC · Lasted 1 min · Affects: Website & web app, API, Realtime connection, Voice & calls, Downloads & updates, Voice relay (TCP fallback) · Detected automatically
Users experienced a major outage of Voznest services, including the website, API, and voice functionality, for a brief period. The issue lasted for 1 minute, during which time users were unable to access or use the platform. The cause of the outage is not specified, but the issue has been resolved and all services are now working normally. Everything has been functioning as expected since the resolution.
Timeline (4)
Monitoring
Recovered — everything answers again. Watching it for a few minutes before closing (4 min so far).
Investigating
Update: Nothing on the server answers — not the website, not the API, not the voice relay that's reached directly. The machine or its network at the hosting provider is down. • Website & web app: failing from US West (Cloudflare error 530 (tunnel down)), US East (Cloudflare error 530 (tunnel down)), Europe (Cloudflare error 530 (tunnel down)) • API: failing from US West (Cloudflare error 530 (tunnel down)), US East (Cloudflare error 530 (tunnel down)), Europe (Cloudflare error 530 (tunnel down)) • Realtime connection: failing from US West (Cloudflare error 530 (tunnel down)), US East (Cloudflare error 530 (tunnel down)), Europe (Cloudflare error 530 (tunnel down)) • Voice & calls: failing from US West (Cloudflare error 530 (tunnel down)), US East (Cloudflare error 530 (tunnel down)), Europe (Cloudflare error 530 (tunnel down)) • Voice relay (TCP fallback): failing from US West (no answer within 8 s), US East (no answer within 8 s), Europe (no answer within 8 s) • Downloads & updates: failing from US West (Cloudflare error 530 (tunnel down)), US East (Cloudflare error 530 (tunnel down)), Europe (Cloudflare error 530 (tunnel down))
Investigating
We're looking into it. Nothing on the server answers — not the website, not the API, not the voice relay that's reached directly. The machine or its network at the hosting provider is down. • Website & web app: failing from US West (Cloudflare error 530 (tunnel down)), US East (Cloudflare error 530 (tunnel down)), Europe (Cloudflare error 530 (tunnel down)) • API: failing from US West (Cloudflare error 530 (tunnel down)), US East (Cloudflare error 530 (tunnel down)), Europe (Cloudflare error 530 (tunnel down)) • Realtime connection: failing from US West (Cloudflare error 530 (tunnel down)), US East (Cloudflare error 530 (tunnel down)), Europe (Cloudflare error 530 (tunnel down)) • Voice & calls: failing from US West (Cloudflare error 530 (tunnel down)), US East (Cloudflare error 530 (tunnel down)), Europe (Cloudflare error 530 (tunnel down)) • Voice relay (TCP fallback): failing from US West (no answer within 8 s), US East (no answer within 8 s), Europe (no answer within 8 s) • Downloads & updates: failing from US West (Cloudflare error 530 (tunnel down)), US East (Cloudflare error 530 (tunnel down)), Europe (Cloudflare error 530 (tunnel down))
Resolved
Resolved. It lasted 1 min; everything has been working normally since.
Started 25 Oct, 16:20 UTC · Lasted 52 min · Affects: Voice relay (TCP fallback) · Detected automatically
Some users experienced issues with voice, video, and streams not being able to connect due to a problem with the private voice relay. The issue started and was resolved on October 25. The private voice relay not answering from the internet is being looked into as the likely cause. The issue has been resolved and services are now available.
Timeline (5)
Resolved
Resolved. It lasted 52 min; everything has been working normally since.
Monitoring
Recovered — everything answers again. Watching it for a few minutes before closing (51 min so far).
Identified
Update: Part of the message servers stopped. Delivery can be slow or uneven until they restart (they restart on their own). • Message servers: 3/4 message servers, 3/3 socket edges • Voice relay (TCP fallback): failing from US West (no answer within 8 s), US East (no answer within 8 s), Europe (no answer within 8 s)
Identified
Identified: calls over UDP connect normally. The server's firewall is dropping the relay's TCP fallback (port 3478/TCP), so only people on networks that block UDP (some offices, schools, public Wi-Fi) can't join voice. A firewall change is pending.
Investigating
We're looking into it. The private voice relay (TURN) doesn't answer from the internet. Voice, video and streams can't connect until it's back. • Voice relay: failing from US West (no answer within 8 s), US East (no answer within 8 s), South America (no answer within 8 s)
Voznest Status