All Systems Operational

About This Site

This page is dedicated to keeping you informed on status updates from Telnyx.

Uptime over the past 90 days. View historical uptime.
Telephony SIP Regions ? Operational
90 days ago
100.0 % uptime
Today
US ? Operational
Europe ? Operational
Australia ? Operational
Canada ? Operational
90 days ago
100.0 % uptime
Today
Telephony Anchorsites ? Operational
Chicago, IL Operational
Ashburn, VA Operational
San Jose, CA Operational
Vancouver, Canada Operational
London, UK Operational
Amsterdam, Netherlands Operational
Sydney, Australia Operational
Frankfurt, Germany Operational
Other Telephony Systems Operational
Messaging Operational
Call Control Operational
Mission Control API ? Operational
East Region Operational
Central Region Operational
West Region Operational
CNAM API Operational
Central Region ? Operational
West Region Operational
LRN Lookup API ? Operational
East Region Operational
Central Region Operational
Switch Data API Operational
East Region ? Operational
Central Region Operational
Intercom Intercom Web Application Operational
Slack Messaging Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
had a major outage
had a partial outage

No incidents or maintenance related to this downtime.

Scheduled Maintenance
Non-disruptive Scheduled Telephony Engine Maintenance Jun 1, 06:00-08:00 UTC
Our Telephony Engineers will be performing maintenance on the Telephony Engine. This maintenance will not disrupt service, however you may notice re-registration of your devices during the maintenance, as our primary SIP proxy is replaced temporarily by our secondary SIP proxy.
Posted on May 29, 16:03 UTC
System Metrics Month Week Day
Mission Control API Response Time ?
Fetching
CNAM API Response Times
Fetching
LRN Lookup API Response Times
Fetching
Switch Data API Response Times
Fetching
Past Incidents
Jun 1, 2020

No incidents reported today.

May 31, 2020

No incidents reported.

May 30, 2020

No incidents reported.

May 29, 2020

No incidents reported.

May 28, 2020
Intermittent failures to our LRN service (lrnlookup.telnyx.com) located in our US east coast
Resolved - Engineers have confirmed no new failures to the lrn service in US east coast since the fix was implemented at 19:59 PM UTC. Thank you for your patience, this incident is now resolved.
May 28, 19:30 UTC
Monitoring - We can confirm that our engineers have implemented a recent fix, at 19:59 PM UTC, and the LRN service has been restored. Monitoring will continue to ensure requests are no longer intermittently failing.
May 28, 19:00 UTC
Investigating - We are currently investigating an issue with intermittent failures when requesting an LRN lookup.

These failures are occurring in our US east coast region only at this time.

If you are located on the east coast and making these requests, you may notice intermittent failures with a 400 status code response error.
May 28, 18:57 UTC
May 27, 2020

No incidents reported.

May 26, 2020

No incidents reported.

May 25, 2020

No incidents reported.

May 24, 2020

No incidents reported.

May 23, 2020

No incidents reported.

May 22, 2020

No incidents reported.

May 21, 2020
Outbound termination call failures
Resolved - This incident has been resolved.
May 21, 15:01 UTC
Update - We continue to monitor the services at this time and continue to see stability.
May 21, 14:28 UTC
Monitoring - A fix has been implemented since 13:45 PM UTC and we have observed general improvements. The services are being monitored closely at this time.
May 21, 13:58 UTC
Identified - The issue has been identified and the engineers are working on a fix.
May 21, 13:46 UTC
Investigating - We are currently investigating an issue where outbound calls through the Telnyx network are failing intermittently.
May 21, 13:38 UTC
Non-Disruptive Scheduled Telephony Engine Maintenance
Completed - Maintenance was completed as scheduled.
May 21, 08:54 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 21, 08:01 UTC
Scheduled - Our Telephony Engineers will be performing maintenance on the Telephony Engine in Canada region.

This maintenance will not disrupt service, but you may notice re-registration of your devices during the maintenance, as our primary SIP proxy is replaced temporarily by our secondary SIP proxy.
May 19, 17:52 UTC
Scheduled Telephony Engine Maintenance
Completed - The maintenance was completed successfully, without issue.
May 21, 07:23 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 21, 06:02 UTC
Scheduled - Our Telephony Engineers will be performing maintenance on the Telephony Engine, to update the TLS certificate *chain* used on our SIP proxy servers at sip.telnyx.com:5061 and sip.telnyx.eu:5061.
The server (leaf) certificate will remain unchanged; the change is to remove one (redundant) intermediate certificate from the chain.

For most customers, this maintenance should not disrupt service; however, you may notice re-registration and re-connection (TCP and TLS) of your devices.
The work is being done only on the sip proxy servers, not on any media servers.
Inbound and outbound calling (and SIP registration) should work without disruption throughout the maintenance window.

Extra information
The change being made here affects TLS traffic only; there's no change to non-TLS (TCP or UDP) transports.

The intermediate certificate is redundant because a more-recently-issued Root CA certificate replaces it.
For customers who use a SIP appliance that needs a TLS certificate explicitly loaded, this may require some maintenance in advance. If you've explicitly installed the root CA certificate, then maintenance may be necessary because the chain of trust will come via a different Root CA certificate, and it's available at https://crt.sh/?id=1199354.

For any queries about any of this, please contact us by email to support@telnyx.com.
May 18, 19:40 UTC
May 20, 2020
Non-Disruptive Scheduled Telephony Engine Maintenance
Completed - The scheduled maintenance has been completed.
May 20, 21:22 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 20, 18:00 UTC
Scheduled - Our Telephony Engineers will be performing maintenance on the Telephony Engine in Sydney, Australia.

This maintenance will not disrupt service, but you may notice re-registration of your devices during the maintenance, as our primary SIP proxy is replaced temporarily by our secondary SIP proxy.
May 19, 17:32 UTC
Partial failures with requests to call control & TeXML based endpoints
Resolved - This incident has been resolved.
May 20, 19:22 UTC
Update - We are continuing to monitor the call control / texml services and have continued to see improvements since the initial fixes that were implemented at 16:30 PM UTC.
May 20, 18:46 UTC
Update - We are continuing to monitor the call control / texml services and have continued to see improvements since the initial fixes that were implemented at 16:30 PM UTC.
May 20, 17:42 UTC
Monitoring - We have been informed that our engineers have implemented several fixes and that there has been a decrease in 5XX responses, since 16:00 PM UTC. They still have a few remaining action items, which are currently in progress. Further updates to be provided in the next hour.
May 20, 16:43 UTC
Update - Our engineers continue to work on resolving the issue.
May 20, 15:32 UTC
Identified - The issue has been identified and the engineers are working on a fix.
May 20, 14:53 UTC
Investigating - We have identified partial failures with requests to call control & TeXML based endpoints that started occurring at 13:00 PM UTC and at 14:00 PM UTC.

Users may have seen a 5XX response from our API proxies when attempting to initiate new control & TeXML requests. Calls that were already in progress, where new commands were issued, may have failed to have been processed during this time-frame.

Our engineers continue to investigate in order to mitigate the issue fully.
May 20, 14:21 UTC
May 19, 2020

No incidents reported.

May 18, 2020

No incidents reported.

← Incident History Powered by Statuspage