The service we use to auto-renew certificates throttles aggressively. When a request to renew a cert is throttled or failed, we automatically retry to renew the certificate. This process usually resolves and the cert is renewed. However, in some cases the renewal process can get stuck; we have alerting set up to catch these instances. Unfortunately a logic error was introduced into this alert and in this case a stuck renewal process did not alert and the certificate eventually expired.
We have validated that no other certs are currently in this state. We have also resolved the issue with the alerting. In the future, we'll ensure to monitor changes made to this alerting process to ensure this does not happen again.
Posted Dec 28, 2025 - 10:23 PST
Resolved
we've resolved the root cause of the expiring cert. service has been fully restored.
this impacted core connectivity and API in the US Central (Chicago) region, including RTC, SIP, Phone numbers, Egress, and Ingress
post mortem will follow shortly.
Posted Dec 27, 2025 - 16:37 PST
Identified
the error is due to an expired certificate in the US Central cluster, we are routing traffic around the region
Posted Dec 27, 2025 - 16:34 PST
Investigating
we are investigating reports of connection failures originating from the Chicago region.
Posted Dec 27, 2025 - 16:29 PST
This incident affected: Regional Real Time Communication (US Central - Real Time Communication).