Is Telnyx down right now?

Maintenance. As of 2026-10-10 07:15 UTC, Telnyx is under maintenance. This page reads the status again every 3 minutes.

How long do Telnyx outages usually last?

Of the 3 incidents Telnyx reported in the last 90 days, half were resolved within 46 min; the longest took 25 h 51 min. Incidents rated major or critical typically took 46 min. These are the provider's own start and end times.

Where does this status come from?

From Telnyx's own status page API at https://status.telnyx.com. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are Telnyx's words.

Can I get an alert when Telnyx goes down?

Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Telnyx reports an incident and one when it is over. There is also an RSS feed at https://upbutler.com/status/telnyx/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.

How can my agent or app check Telnyx status?

Fetch https://upbutler.com/status/telnyx/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"telnyx"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Telnyx's?

Add "telnyx" to the dependencies of your UpButler workspace. When one of your monitors fails while Telnyx has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Telnyx down?

Telnyx is under maintenance

Right now

Maintenance. Mumbai, India: Under maintenance.

Last checked 5 min ago (2026-10-10 07:15 UTC) from status.telnyx.com · every 180s

For agents

pause

Pause, next attempt in 300s.

Up right now, same job: Plivo, Sinch, Bird (MessageBird).

GET upbutler.com/status/telnyx/status.agent.json

MCP: upstream_status {"service":"telnyx"}

Voice, messaging and SIP for voice agents.

What Telnyx says

Maintenance

Taken as is from Telnyx's own status page API. Incident titles and component names below are theirs.

Open status.telnyx.com

What UpButler measured

There is no keyless endpoint of Telnyx that says anything useful, so UpButler does not probe it. To check your own Telnyx account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Open at Telnyx

Voice Services Update - Mumbai, Indiamaintenance in progress
Since 2026-10-09 10:46 UTC
The Telnyx anchorsite in "Mumbai, India" is currently out of service, and all voice calls are automatically re-routed to the nearest available anchorsite. No actions required. If you experience any audio issues or dropped calls during this maintenance window, please report them immediately to Telnyx Support.
Wireless Network Signalling Redundancy Testscheduled maintenance
Starts 2026-09-14 11:16 UTC
This maintenance has been rescheduled from September 18th to September 21st (06:00-09:00 UTC). The scope of work is unchanged.
Wireless Maintenance US East Site (DC2)scheduled maintenance
Starts 2026-08-27 13:12 UTC
The Wireless team will be applying configuration updates to Network Functions on the US East site. The work includes UPF configuration changes requiring restarts, timer parameter updates, and logging configuration enablement. There will be rolling restarts of some components, which have the potential to cause disruption to active data sessions. These disruptions are not expected to last more than 5 minutes. This would affect users connected in North, Central and South America as well as the Car…
Scheduled maintenance for Programmable Voice - Voice APIscheduled maintenance
Starts 2026-05-27 08:49 UTC
`Our Telephony Engineers will perform maintenance on our Programmable Voice services in the Europe/US region. This maintenance should not disrupt service.`

Text written by Telnyx, shown unchanged.

Which part of Telnyx?

Mumbai, IndiaMaintenance

Telnyx components

1 of 25 not operational

Mission Control Portal UIOperational
US East RegionOperational
US Central RegionOperational
US West RegionOperational
USOperational
EuropeOperational
AustraliaOperational
CanadaOperational
Middle EastOperational
Asia (Beta)Operational
Chicago, ILOperational
Ashburn, VAOperational
San Jose, CAOperational
Dubai, UAEOperational
London, UKOperational
Amsterdam, NetherlandsOperational
Sydney, AustraliaOperational
Melbourne, AustraliaOperational
Frankfurt, GermanyOperational
Toronto, CanadaOperational
Chennai, IndiaOperational
Mumbai, IndiaMaintenance
Montreal, CanadaOperational
MS Teams Operator ConnectOperational
Zoom Provider ExchangeOperational

Telnyx incidents, last 90 days

2026-07-13: no record
2026-07-14: no record
2026-07-15: no record
2026-07-16: no record
2026-07-17: no record
2026-07-18: no record
2026-07-19: no record
2026-07-20: no record
2026-07-21: no record
2026-07-22: no record
2026-07-23: no record
2026-07-24: no record
2026-07-25: no record
2026-07-26: no record
2026-07-27: no record
2026-07-28: no record
2026-07-29: no record
2026-07-30: no record
2026-07-31: no record
2026-08-01: no record
2026-08-02: no record
2026-08-03: no record
2026-08-04: no record
2026-08-05: no record
2026-08-06: no record
2026-08-07: no record
2026-08-08: no record
2026-08-09: no record
2026-08-10: no record
2026-08-11: no record
2026-08-12: no record
2026-08-13: no record
2026-08-14: no record
2026-08-15: no record
2026-08-16: no record
2026-08-17: no record
2026-08-18: no record
2026-08-19: no record
2026-08-20: no record
2026-08-21: no record
2026-08-22: no record
2026-08-23: no record
2026-08-24: no record
2026-08-25: no record
2026-08-26: no record
2026-08-27: no incident reported
2026-08-28: no incident reported
2026-08-29: no incident reported
2026-08-30: no incident reported
2026-08-31: no incident reported
2026-09-01: no incident reported
2026-09-02: no incident reported
2026-09-03: no incident reported
2026-09-04: no incident reported
2026-09-05: no incident reported
2026-09-06: no incident reported
2026-09-07: no incident reported
2026-09-08: no incident reported
2026-09-09: no incident reported
2026-09-10: no incident reported
2026-09-11: no incident reported
2026-09-12: no incident reported
2026-09-13: no incident reported
2026-09-14: no incident reported
2026-09-15: no incident reported
2026-09-16: no incident reported
2026-09-17: no incident reported
2026-09-18: no incident reported
2026-09-19: no incident reported
2026-09-20: no incident reported
2026-09-21: no incident reported
2026-09-22: no incident reported
2026-09-23: no incident reported
2026-09-24: no incident reported
2026-09-25: no incident reported
2026-09-26: no incident reported
2026-09-27: no incident reported
2026-09-28: major incident
2026-09-29: no incident reported
2026-09-30: no incident reported
2026-10-01: no incident reported
2026-10-02: major incident
2026-10-03: no incident reported
2026-10-04: no incident reported
2026-10-05: no incident reported
2026-10-06: major incident
2026-10-07: major incident
2026-10-08: no incident reported
2026-10-09: maintenance
2026-10-10: maintenance

2026-07-134 of 45 days with an incidenttoday

Each bar is a day, coloured by the worst incident Telnyx reported. It is their incident record, not a measurement of uptime.

Incidents: 3; 3 major or critical
Typical time to resolve: 46 min; median
Nine in ten within: —; major ones: 46 min
Longest: 25 h 51 min; record since 2026-08-27

Started (UTC)	Incident	Impact	Lasted
2026-10-06 17:38	Delayed delivery of 10DLC SMS messages to AT&T destinations	major	25 h 51 min
2026-10-02 14:20	Cloud Storage us-west-1 Region Temporarily Unavailable	major	46 min
2026-09-28 17:09	Errors for K2.6 Chat Completions (Voice AI not affected)	major	12 min

Get alerted when Telnyx goes down

No account. One email when Telnyx reports an incident, one when it is over. You confirm the address first, and every email has a one-click unsubscribe.

Or follow the RSS feed. On UpButler? Add Telnyx as a dependency to route it to Slack, Teams or a webhook.

Status badge

Show Telnyx's current status in a README or an internal wiki. It updates by itself.

[![Telnyx status](https://upbutler.com/status/telnyx/badge.svg)](https://upbutler.com/status/telnyx)

Tell your outage from Telnyx's

Declare that your project depends on Telnyx. When one of your monitors fails while Telnyx has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - telnyx

Ask before you retry

curl -s https://upbutler.com/status/telnyx/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "telnyx",
  "verdict": "pause",
  "status": "maintenance",
  "reason": "Mumbai, India: Under maintenance",
  "retryAfterSec": 300,
  "incident": null,
  "alternatives": [
    "plivo",
    "sinch",
    "bird"
  ],
  "probe": null
}

Questions

Is Telnyx down right now?: Maintenance. As of 2026-10-10 07:15 UTC, Telnyx is under maintenance. This page reads the status again every 3 minutes.
How long do Telnyx outages usually last?: Of the 3 incidents Telnyx reported in the last 90 days, half were resolved within 46 min; the longest took 25 h 51 min. Incidents rated major or critical typically took 46 min. These are the provider's own start and end times.
Where does this status come from?: From Telnyx's own status page API at https://status.telnyx.com. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are Telnyx's words.
Can I get an alert when Telnyx goes down?: Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Telnyx reports an incident and one when it is over. There is also an RSS feed at https://upbutler.com/status/telnyx/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.
How can my agent or app check Telnyx status?: Fetch https://upbutler.com/status/telnyx/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"telnyx"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Telnyx's?: Add "telnyx" to the dependencies of your UpButler workspace. When one of your monitors fails while Telnyx has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Also check

UpButler is not affiliated with Telnyx. Status and incident text belong to Telnyx and are read from their public status source; the probe result is UpButler's own measurement.