Skip to main content
Telnyx logo

Is Telnyx Down?

No — Telnyx is up

Reachable from all 8 checked regions

Average response time: 239ms

Last checked · checks run every 6 hours

Official status page: https://status.telnyx.com

Components the vendor reports as affected: Mumbai, India Under Maintenance

A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical and our own checks also saw Telnyx fail from enough regions to rule out probe noise.

Telnyx uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
270ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 53 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

53-day clean streak
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 42 checks
Sep 12: 100.00% uptime, 31 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 31 checks
Sep 15: 100.00% uptime, 31 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 24 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 31 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 24 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 30 checks
Oct 1: 100.00% uptime, 29 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 24 checks
Sep 10 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

fra
95ms
DNS 29ms TCP 2ms TLS 10ms TTFB 82ms
gru
53ms
DNS 6ms TCP 2ms TLS 9ms TTFB 39ms
iad
64ms
DNS 13ms TCP 2ms TLS 8ms TTFB 47ms
jnb
52ms
DNS 8ms TCP 0ms TLS 9ms TTFB 42ms
lax
102ms
DNS 58ms TCP 2ms TLS 10ms TTFB 92ms
lhr
370ms
DNS 30ms TCP 2ms TLS 20ms TTFB 230ms
nrt
1125ms
DNS 495ms TCP 1ms TLS 9ms TTFB 795ms
ord
55ms
DNS 8ms TCP 2ms TLS 13ms TTFB 45ms

What Telnyx does

Telnyx sells voice, SMS and connectivity APIs on infrastructure it owns rather than reselling another carrier's. Developers use it for programmable calling, SIP trunking, phone numbers, two-factor delivery, and increasingly for realtime voice agents. Applications that send verification codes or route customer calls depend on it in the path of every message and every call.

What an outage looks like

Outbound SMS returns accepted by the API but never arrives, so signup and password-reset codes silently stop. Calls fail to connect or drop after a few seconds, and SIP registrations flap. The API gateway returns 5xx or times out. Because Telnyx reports per-datacentre, a fault often hits one region such as Ashburn or Sydney while others carry traffic normally.

What to do about it

status.telnyx.com breaks the platform down by datacentre and by product, so confirm whether your traffic's region is the affected one before changing anything. Resending a message the API already accepted risks delivering twice once a backlog clears, so check delivery receipts before retrying. For verification codes, an alternate channel such as email keeps signups working while messaging recovers.

Is it down for everyone, or just you?

If this page says Telnyx is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Telnyx outage FAQ

Is Telnyx down or is it just my region?
Check the region before anything else. Telnyx publishes status per datacentre, listing locations such as Ashburn, Chicago, San Jose, Toronto, London, Sydney and Chennai separately, and a fault frequently affects one while the rest carry traffic. Find the datacentre your numbers and SIP connections are homed to, and compare that against the component list rather than the overall banner.
My SMS says accepted but never arrived. Is that an outage?
It can be. An accepted response means Telnyx took the message, not that a handset received it. During a messaging incident, or when a carrier downstream is the problem, messages sit undelivered while the API keeps returning success. Check delivery receipts rather than the send response before assuming the number or campaign registration is at fault.
Should I resend verification codes during a Telnyx incident?
Resend sparingly. If the original messages were accepted and are queued somewhere downstream, a second send can arrive alongside the first and leave users holding two codes with no idea which is valid. Where the signup flow allows it, switch verification to email for the duration, which keeps registrations moving without stacking duplicates against one number.
Does a Telnyx outage affect voice and SMS together?
Not necessarily. The status page reports the Voice API, SMS, SIP trunking and the API gateway as distinct components, and incidents often touch one product in one location. Calls can drop while messaging is unaffected, or the reverse. Match the component to the symptom instead of assuming everything on the account has failed.

How we measure this

  • We request Telnyx's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Telnyx publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Telnyx goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required