Last checked
Global AI-powered connectivity and communication infrastructure for businesses.
Experiencing an issue?
Czy Telnyx nie działa?
Status unavailable
Share your experience to help others stay informed.
Status verification pending
The latest official observation is not fresh enough to confirm current service health.
Official provider statusOfficial incident resolved
MMS API Delivery Issues — We observed some queueing as it relates to delivery receipts over MMS which has since been drained, sending remained unaffected during this period.
Official provider statusOfficial maintenance scheduled
Upcoming TLS Certificate renewals for SIP Trunking Signaling - US and EU regions — Our Telephony Engineers will perform maintenance on our inbound SIP proxy servers in the US ([sip.telnyx.com](http://sip.telnyx.com)) and Europe ([sip.telnyx.eu](http://sip.telnyx.eu)) regions. During this maintenance, our TLS certificate for each proxy server will be renewed; the four proxy servers will get the update on separate days. These important changes will happen. - We'll switch Certificate Authority from Digicert to LetsEncrypt (which means that the entire certificate chain will be changed). - The "clientAuth" EKU is being deprecated, which may affect customers who use mTLS (mutual TLS) for SIP signaling. This change may be important for any customer who has our old (current) TLS certificate or root-CA certificate (or chain) loaded into an SBC/appliance/phone. A notification was sent to customers earlier this year (21st July, subject "Action may be required: TLS certificate changes for Telnyx SIP proxies"); more-detailed information can be found online here. - Important: the schedule for this maintenance is changed slightly from what was published on our website (which has been updated with this new schedule). - Mon 09 November (0900 to 1200 UTC) - 64.16.250.10 ([sip.telnyx.com](http://sip.telnyx.com) IP2) - Thu 12 November (0900 to 1200 UTC) - 192.76.120.10 ([sip.telnyx.com](http://sip.telnyx.com) IP1) - Mon 16 November (0900 to 1200 UTC) - 185.246.41.141 ([sip.telnyx.eu](http://sip.telnyx.eu) IP2) - Thu 19 November (0900 to 1200 UTC) - 185.246.41.140 ([sip.telnyx.eu](http://sip.telnyx.eu) IP1) For any customer seeking to test TLS compatibility before the renewal, note that our Staging SIP proxy server at sipstaging.telnyx.com:5061 can be used to test both inbound and outbound calls (and registrations); it has a certificate from the same certificate authority. For any customer not using TLS, the change is expected to be completely seamless.
Official provider status0 individual report entries in the last 24 hours. This list includes legacy imports; external source aggregates are shown in the chart.
Official status observations, not measured service uptime.
Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.
| Incident name | Duration | StartedUTC | Acknowledged | Severity |
|---|---|---|---|---|
| 2h 33m | Yes | Minor | ||
| 5h 2m | Yes | Minor | ||
| 29h 17m | Yes | Unknown | ||
| 16h 13m | Yes | Major | ||
| 0m | Yes | Unknown | ||
| 5h 46m | Yes | Critical | ||
| 21h 35m | Yes | Unknown | ||
| 0m | Yes | Unknown |
Uptimus monitoruje Telnyx przez oficjalne źródło i normalizuje incydenty, konserwacje oraz komponenty do jednego spójnego statusu.
Strona zawiera obecnie 92 komponentów, 82 incydentów, 41 konserwacji i 52 dni znanej historii.
Uptimus jest niezależny i nie jest powiązany z Telnyx. Prawidłowy status nie gwarantuje braku problemów u każdego użytkownika, urządzenia lub regionu.
Otrzymuj alerty, gdy Telnyx lub monitorowany komponent zgłasza poważną albo krytyczną awarię. Alerty mogą trafiać przez kanały włączone w workspace, w tym e-mail, push i skonfigurowane integracje. Dostępna historia zawiera 82 incydentów i zapewnia kontekst wykraczający poza bieżący status. Ostatni zarejestrowany incydent to „MMS API Delivery Issues”.
Otrzymuj alerty o obniżonej wydajności, częściowym wpływie i mniejszych incydentach. Uptimus monitoruje obecnie 92 komponentów Telnyx: Mission Control Portal UI, US East Region, US Central Region, US West Region. Alerty mogą trafiać przez kanały włączone w workspace, w tym e-mail, push i skonfigurowane integracje.
Planned work published by the official provider.
This maintenance has been rescheduled from September 18th to September 21st (06:00-09:00 UTC). The scope of work is unchanged.
Started 27 paź 2026, 20:27 UTC · Ongoing
The Wireless team will be performing scheduled maintenance on the US packet core sites, applying configuration updates to session management and charging, one site at a time. Some devices may see a brief interruption to data sessions while sessions re-establish; any disruption is not expected to last more than 5 minutes. This affects users in North, Central and South America as well as the Caribbean.
Started 27 paź 2026, 20:27 UTC · Ongoing
`Our Telephony Engineers will perform maintenance on our Programmable Voice services in the Europe/US region. This maintenance should not disrupt service.`
Started 27 paź 2026, 20:27 UTC · Ongoing
The Wireless team will be performing a UDSF (Unified Data Storage Function) software version rollback across all three sites (Chicago, Ashburn, and Sydney). This is a precautionary alignment to a Mavenir-supported version. The UDSF pods will restart during the maintenance window. No customer impact is expected. The maintenance is not expected to last more than 2 hours.
Started 27 paź 2026, 20:27 UTC · Ongoing
The Wireless team will perform maintenance on our GTP proxy infrastructure in the US region. During this time there is a potential for brief service disruption for connectivity sessions in the affected region (North, Central and South America as well as the Caribbean). This maintenance is not expected to last more than 5 minutes.
Started 27 paź 2026, 20:27 UTC · Ongoing
Our Telephony Engineers will perform maintenance on our inbound SIP proxy servers in the US ([sip.telnyx.com](http://sip.telnyx.com)) and Europe ([sip.telnyx.eu](http://sip.telnyx.eu)) regions. During this maintenance, our TLS certificate for each proxy server will be renewed; the four proxy servers will get the update on separate days. These important changes will happen. - We'll switch Certificate Authority from Digicert to LetsEncrypt (which means that the entire certificate chain will be changed). - The "clientAuth" EKU is being deprecated, which may affect customers who use mTLS (mutual TLS) for SIP signaling. This change may be important for any customer who has our old (current) TLS certificate or root-CA certificate (or chain) loaded into an SBC/appliance/phone. A notification was sent to customers earlier this year (21st July, subject "Action may be required: TLS certificate changes for Telnyx SIP proxies"); more-detailed information can be found online here. - Important: the schedule for this maintenance is changed slightly from what was published on our website (which has been updated with this new schedule). - Mon 09 November (0900 to 1200 UTC) - 64.16.250.10 ([sip.telnyx.com](http://sip.telnyx.com) IP2) - Thu 12 November (0900 to 1200 UTC) - 192.76.120.10 ([sip.telnyx.com](http://sip.telnyx.com) IP1) - Mon 16 November (0900 to 1200 UTC) - 185.246.41.141 ([sip.telnyx.eu](http://sip.telnyx.eu) IP2) - Thu 19 November (0900 to 1200 UTC) - 185.246.41.140 ([sip.telnyx.eu](http://sip.telnyx.eu) IP1) For any customer seeking to test TLS compatibility before the renewal, note that our Staging SIP proxy server at sipstaging.telnyx.com:5061 can be used to test both inbound and outbound calls (and registrations); it has a certificate from the same certificate authority. For any customer not using TLS, the change is expected to be completely seamless.
Started 27 paź 2026, 20:27 UTC · Ongoing
The Wireless team will be performing maintenance on network signalling infrastructure in the Chicago (CH1) and Ashburn (DC2) sites. During this window, some wireless subscribers in North, Central and South America as well as the Caribbean may experience brief interruptions to SMS delivery. Data and voice services are not expected to be affected. The maintenance is expected to take up to 3 hours, with impact to individual subscribers not expected to last more than 15 minutes at a time.
Started 27 paź 2026, 20:27 UTC · Ongoing
The Wireless team will move voice (IMS) session handling at our US core site to upgraded infrastructure to improve VoLTE call reliability. During the window, new voice registrations may briefly fail and retry while traffic is moved; existing sessions and data services are not expected to be affected, and any disruption is not expected to last more than 5 minutes. Affected users are in North, Central and South America and the Caribbean.
Started 27 paź 2026, 20:27 UTC · Ongoing
Publiczne strony Downdetector opierają się głównie na zgłoszeniach użytkowników. Uptimus łączy je z oficjalnymi incydentami, pracami serwisowymi i stanem komponentów, gdy dostawca je publikuje.
| Kryteria porównania | Uptimus | Downdetector |
|---|---|---|
| Zgłoszenia społeczności dotyczące Telnyx | Dostępne | Dostępne |
| Adaptacyjna baza odróżniająca pojedyncze zgłoszenia od większej awarii | Dostępne | Dostępne |
| Aktywność z 24 godzin i regionalna mapa awarii | Dostępne | Dostępne |
| Jeden obszar dla stron, dostawców statusu, gier Steam oraz aplikacji i gier Android | Dostępne | Oddzielny produkt |
| Alerty e-mail, push i webhook z tego samego obszaru | Dostępne | Oddzielny produkt |
| Oficjalne aktualizacje i historia statusu Telnyx | Dostępne | Oparte na zgłoszeniach |
| Stan komponentów i prace serwisowe pokazane osobno | Dostępne | Ograniczone publicznie |
The current official status of Telnyx cannot be verified. The latest stored provider observation indicated ongoing maintenance. 0 reports were recorded for Telnyx in the last 24 hours. Last official check: .
Odkryj inne popularne usługi i ich aktualny stan
Oceń tę usługę
Brak recenzji
Podziel się swoimi przemyśleniami na temat Telnyx
Bądź pierwszą osobą, która skomentuje!
