Elevated API errors and missing cost data

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.

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.

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.

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.

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.