rewindex

ChangesTelnyxMessaging API Latency

Telnyx: Incident updated: Messaging API Latency

Incident updateNormal progress (rule, 100%)Changed status.telnyx.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Telnyx removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1
Before: investigating
After: monitoring
AddedUpdatemonitoring#2
Before: not present
After: 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.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

Tuesday, November 3

2 incident changes

Monday, November 2

2 incident changes

Cite this

Incident updated: Messaging API Latency on Telnyx’s status page, changed 2026-11-03 00:53 UTC (change 3 of 4).

Title
Incident updated: Messaging API Latency
Vendor
Telnyx
Date
URL
https://rewindex.com/change/r52329a0e03941c

All Telnyx changesTelnyx profileMarkdownJSON