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.

1. Resolved25 Oct, 17:16 UTC

   Resolved. It lasted 52 min; everything has been working normally since.

2. Monitoring25 Oct, 17:11 UTC

   Recovered — everything answers again. Watching it for a few minutes before closing (51 min so far).

3. Identified25 Oct, 17:09 UTC

   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)

4. Identified25 Oct, 16:28 UTC

   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.

5. Investigating25 Oct, 16:21 UTC

   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)