Telnyx incident

Elevated API errors and missing cost data

Minor Resolved

Telnyx experienced a minor incident on August 5, 2026, lasting 18h 34m. The incident has been resolved; the full update timeline is below.

Started
Aug 05, 2026, 08:55 PM UTC
Resolved
Aug 06, 2026, 03:30 PM UTC
Duration
18h 34m
Detected by Pingoru
Aug 05, 2026, 08:55 PM UTC

Update timeline

  1. identified Aug 05, 2026, 08:55 PM UTC

    We are experiencing elevated error rates affecting a small percentage of Messaging API requests. Affected requests may return a 503 or 504 error and can be safely retried. Separately, cost data may be missing or incomplete on some records. This affects the cost field on inbound message webhooks, and call cost for Programmable Voice and TeXML. Message delivery is not affected. We have identified the cause as a degraded internal dependency and are working on a resolution. We will provide an update within 30 minutes.

  2. identified Aug 05, 2026, 09:39 PM UTC

    Error rates remain elevated and intermittent, with periods of improvement followed by renewed impact. A percentage of Messaging API requests may return 503 or 504 errors and can be safely retried. Cost data may still be missing on some records. Message delivery remains unaffected. We have identified the cause and work on a resolution is ongoing. We will update this page as the situation develops.

  3. identified Aug 06, 2026, 02:21 AM UTC

    Inbound Messaging APIs have returned to normal operation. The remaining impact is on retrieving message records. A percentage of GET /v2/messages/{id} requests may return a 503 or 504 error and can be safely retried. Sending messages, message delivery, and delivery webhooks are unaffected. Cost data may be missing on some records created earlier during this incident. Work on a resolution is ongoing.

  4. monitoring Aug 06, 2026, 01:41 PM UTC

    Error rates have returned to normal and message retrieval is operating as expected. Some recently created message records may still take longer than usual to appear while a processing backlog clears. We are monitoring to confirm the fix holds.

  5. monitoring Aug 06, 2026, 02:03 PM UTC

    All services are operating normally. Some message records created earlier during this incident may still take longer than usual to appear while a processing backlog clears. We are monitoring to confirm.

  6. resolved Aug 06, 2026, 03:30 PM UTC

    This incident has been resolved. All services are operating normally