Messaging API Latency

What to do

• Check whether your product depends on Telnyx. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 9h 50m it lasted.

  Anything that failed between 2026-11-02 15:36 UTC and 2026-11-03 01:26 UTC may need a replay.

• Subscribe to Telnyx's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=telnyx works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Telnyx 5

1. investigatingNov 2, 2026, 3:36 PM UTC

   We’re investigating a brief blip in API latency on the Messaging API.

   provider

2. investigatingNov 2, 2026, 3:44 PM UTC

   We’re investigating delays in webhook delivery latency, this is not affecting message sending.

   provider

3. investigatingNov 2, 2026, 8:56 PM UTC

   We’re still investigating issues with webhook latency for delivery receipts. Message sending still remains unaffected.

   provider

4. monitoringNov 3, 2026, 12:48 AM UTC

   A fix has been implemented and we’re monitoring the results. Messages on a go forward basis are having their webhook delivery receipts returned in a timely manner. Delayed webhooks from earlier today are being replayed to customer endpoints to ensure customers can tie out their messages.

   provider

5. resolvedNov 3, 2026, 1:26 AM UTC

   The issue is now resolved, webhook production has now caught up. We have been replaying some delayed webhooks where possible throughout the day. Message delivery remains unaffected.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.