Messaging API Latency
Telnyx reports delays on the Messaging API. The delay affects webhook delivery. The Messaging API stayed slow for at least 9 minutes. Telnyx investigates the problem. Message sending is not affected.
State
Investigating
Started
1 h ago
2026-11-02 15:36 UTC
Ongoing for
1 h 3 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
1 h 3 min 100%
Updates
Times in UTCAs posted by Telnyx
We’re investigating delays in webhook delivery latency, this is not affecting message sending.
We’re investigating a brief blip in API latency on the Messaging API.
Follow Telnyx
Your coding agent knows when Telnyx is down, and tells you when a failure is theirs, not yours. You can also get Telnyx incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "telnyx" and tell me if Telnyx has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=telnyx/feed subscribe https://outages.cc/feed.xml?providers=telnyxFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane