Historial de interrupciones de Telnyx

1. August 11, 2026 at 8:52 AM UTCinvestigating

   We are currently investigating an increase in calls failing with SIP 503 Service Unavailable errors affecting local outbound call termination to European destinations. Customers may experience Local call failures when attempting to reach European destinations Sweden, Denmark etc. Our telephony team is actively working on a resolution.

2. August 11, 2026 at 10:04 AM UTCmonitoring

   Our telephony team has implemented a fix and we are actively monitoring traffic.

3. August 11, 2026 at 3:05 PM UTCresolved

   This issue was mititaged as of `Tue Aug 11 09:44:44 UTC 2026`

1. August 10, 2026 at 3:47 PM UTCinvestigating

   We are investigating high latency for deepgram flux transcription affecting voice api and voice ai assistants.

2. August 10, 2026 at 4:01 PM UTCmonitoring

   We have mitigated the issue and are monitoring

3. August 10, 2026 at 4:29 PM UTCresolved

   This is resolved

1. August 7, 2026 at 3:02 PM UTCinvestigating

   Nuestro equipo de ingeniería está investigando los informes de problemas que afectan a las llamadas con los siguientes síntomas: - Transmisión de audio muerta/una manera - Caídas de llamadas prematuras - Registros de llamadas perdidos y retrasados Seguiremos actualizando nuestra página de estado con los últimos hallazgos.

2. August 7, 2026 at 3:36 PM UTCidentified

   Our engineering team has identified the root cause of this issue and applied a mitigation. Call audio, call stability, and call recordings should now be operating normally.

3. August 7, 2026 at 3:39 PM UTCmonitoring

   We continue to monitor following the earlier mitigation. Services remain stable and no new reports of impact have been received. A final update will follow once resolution is confirmed.

4. August 10, 2026 at 9:19 PM UTCresolved

   This incident has been resolved now.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 7, 2026 at 1:05 PM UTCmonitoring

   Some outbound calls in Amsterdam and Frankfurt anchorsites began failing with error code TM1 between 9.15 - 12.50 UTC today. Errors have currently ceased and our engineering team is monitoring status at this time.

2. August 7, 2026 at 1:55 PM UTCresolved

   This issue is now confirmed resolved as of 13.25 UTC by our engineering team. We continue to monitor traffic signs.

1. August 5, 2026 at 8:55 PM UTCidentified

   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. August 5, 2026 at 9:39 PM UTCidentified

   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. August 6, 2026 at 2:21 AM UTCidentified

   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. August 6, 2026 at 1:41 PM UTCmonitoring

   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. August 6, 2026 at 2:03 PM UTCmonitoring

   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. August 6, 2026 at 3:30 PM UTCresolved

   This incident has been resolved. All services are operating normally

1. August 4, 2026 at 5:19 PM UTCinvestigating

   customers may receive HTTP 503 responses from the Client Credential API, which can prevent telephony token creation or validation. This may cause Voice SDK authentication failures, failed registrations, and new call setup failures. Existing active calls are likely unaffected unless they require a fresh token/API call.

2. August 4, 2026 at 7:00 PM UTCmonitoring

   We identified a capacity issue in the backend service that manages telephony tokens and client SDK credentials. This caused intermittent failures for some credential-related API requests. We increased the number of service pods and raised CPU and memory allocation to better handle request volume. Since making these changes, we are no longer seeing the related 503 errors at the API gateway. The service is currently stable, and we will continue monitoring closely while the incident remains in the monitoring phase.

3. August 6, 2026 at 9:29 AM UTCresolved

   We identified and mitigated a capacity issue in the backend service that manages telephony tokens and client SDK credentials. This caused intermittent HTTP 503 responses for some credential-related API requests. After increasing service capacity and resource allocation, the service remained stable throughout the monitoring period. We will continue reviewing capacity settings to help prevent recurrence.

1. July 28, 2026 at 7:32 PM UTCinvestigating

   503s en puntos finales relacionados con cuentas, número de configuración y sip config

2. July 28, 2026 at 7:55 PM UTCmonitoring

   Edición identificada y parcheada. Supervisión

3. July 28, 2026 at 9:04 PM UTCresolved

   Tras la vigilancia de las correcciones iniciales aplicadas para resolver la cuestión, no hemos visto ninguna repetición del problema. Estamos marcando esto como resuelto pero seguirá monitoreando.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 27, 2026 at 3:08 PM UTCinvestigating

   Actualmente estamos investigando una cuestión que afecta a los servicios en la región de Australia. Los clientes pueden experimentar problemas de conectividad intermitente, mayor latencia o solicitudes fallidas al acceder a algunos servicios de Telnyx.

2. July 27, 2026 at 3:15 PM UTCidentified

   Nuestros equipos de ingeniería han identificado el problema de infraestructura subyacente y están trabajando activamente para restaurar el servicio completo. Estamos monitoreando la situación de cerca y seguiremos proporcionando actualizaciones a medida que se disponga de más información. Nos disculpamos por la interrupción y apreciamos su paciencia mientras trabajamos para resolver el problema.

3. July 28, 2026 at 9:22 AM UTCmonitoring

   Nuestros equipos de ingeniería han restablecido el problema de infraestructura subyacente a las 22:00 UTC el 27 de julio de 2026. Siguen vigilando el medio ambiente para confirmar que la conectividad y el rendimiento de los servicios siguen siendo estables. Los clientes deben comenzar a ver la recuperación en los servicios afectados en la región de Australia.

4. July 30, 2026 at 8:06 AM UTCresolved

   Tras un período de vigilancia, conectividad y rendimiento de los servicios han permanecido estables. Los clientes ya no deben experimentar problemas en los servicios afectados de la región de Australia. Nos disculpamos por la interrupción y apreciamos su paciencia.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 24, 2026 at 10:46 AM UTCidentified

   las compras de eSIM están fallando actualmente, hemos identificado la causa y estamos trabajando en la resolución

2. July 24, 2026 at 2:13 PM UTCmonitoring

   Piscinas restauradas

3. July 24, 2026 at 2:36 PM UTCresolved

   Stock replenished to healthy levels.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 22, 2026 at 10:15 PM UTCinvestigating

   Actualmente estamos investigando un problema que afecta a la entrega de mensajes de MMS a T-Mobile, donde algunos mensajes están dando lugar a un estado de entrega unconfirmado. La cuestión se ha intensificado en nuestro socio de abajo para seguir investigando, y estamos esperando actualizaciones adicionales. Proporcionaremos más información a medida que esté disponible.

2. July 23, 2026 at 3:31 PM UTCresolved

   Se ha resuelto la cuestión que afecta a los informes de entrega de MMS a T-Mobile. Los informes de entrega de MMS se están procesando según lo previsto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 20, 2026 at 11:25 PM UTCinvestigating

   Somos conscientes de que algunos SIM pueden dejar de pasar datos después de un período de inactividad, aunque el dispositivo todavía muestra la señal completa y una conexión móvil. Cuando esto sucede, los datos no se reanudan por sí mismos. Workaround: la conexión se restaura tan pronto como el dispositivo vuelva a registrar con la red. • En los teléfonos, tabletas y otros dispositivos con una interfaz de usuario, recortar el modo Airplane y lo hace inmediatamente. • En IoT y dispositivos incrustados sin esa opción, el reciclaje de potencia del dispositivo o reiniciar el módem tiene el mismo efecto. Los dispositivos que envían o reciben datos regularmente son mucho menos propensos a verse afectados. Hemos identificado el área responsable y estamos trabajando con nuestro proveedor en una solución. Publicaremos nuevas actualizaciones a medida que avancemos

2. August 1, 2026 at 7:49 AM UTCmonitoring

   Se han adoptado medidas correctivas para abordar estas cuestiones a nivel mundial. Actualmente estamos monitoreando la estabilidad durante las próximas 72 horas para asegurar que no vuelva a repetirse.

3. August 3, 2026 at 10:13 PM UTCresolved

   Esta cuestión se resolvió el viernes 31 de julio, aproximadamente a las 3:00 PM CST.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 17, 2026 at 9:11 PM UTCinvestigating

   Cuestiones de conectividad de datos - Europa

2. July 17, 2026 at 10:23 PM UTCmonitoring

   Se realizó un cambio en la red y se ha restaurado la conectividad.

3. July 18, 2026 at 1:07 AM UTCresolved

   La cuestión se resuelve

Traducido automáticamente desde la actualización oficial del incidente.

1. July 16, 2026 at 12:23 PM UTCmonitoring

   Hay un retraso en el procesamiento de los registros de facturación.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 15, 2026 at 6:21 PM UTCinvestigating

   Tuvimos un problema durante uno de nuestro mantenimiento rutinario que ha causado un incidente que ha afectado a varios de nuestros servicios. Estamos trabajando en resolver esto y seguiremos publicando actualizaciones.

2. July 15, 2026 at 6:30 PM UTCinvestigating

   • Salida parcial en algunas funciones del Portal de Control de Misión; • Rendimiento degradado en Telnyx Inference • Salida parcial en voz AI • Incident being investigated.

3. July 15, 2026 at 6:39 PM UTCinvestigating

   Telnyx Servicios de referencia restaurados.

4. July 15, 2026 at 7:59 PM UTCmonitoring

   Nuestros ingenieros han implementado una solución que parece haber resuelto los problemas. Estamos monitoreando nuestros servicios.

5. August 10, 2026 at 9:22 AM UTCmonitoring

   This incident was resolved on 15th of July but status page incorrectly remained open

Traducido automáticamente desde la actualización oficial del incidente.

1. July 15, 2026 at 5:57 PM UTCinvestigating

   Operaciones de API y dashboard afectados.

2. July 15, 2026 at 6:50 PM UTCidentified

   problema identificado, aplicación de solución.

3. July 15, 2026 at 6:55 PM UTCmonitoring

   Aplicación fija, vigilancia

4. July 15, 2026 at 8:17 PM UTCresolved

   Servicio restaurado

Traducido automáticamente desde la actualización oficial del incidente.

1. July 14, 2026 at 2:32 PM UTCinvestigating

   Todas las solicitudes de API en SY1 están fallando con un 523.

2. July 14, 2026 at 2:50 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 13, 2026 at 8:02 PM UTCidentified

   SMS and MMS messages towards T-Mobile destinations are experiencing delays.

2. July 13, 2026 at 9:22 PM UTCresolved

   SMS and MMS delays resolved downstream with T-Mobile.

1. July 10, 2026 at 7:37 PM UTCmonitoring

   No impact on connectivity services. Usage reporting incorrect. We have identified and addressed an issue affecting WDR processing. This would have resulted in us reporting lower than actual data consumption over the past 3 days. We are currently processing the backlog which will result in the corrected usage being reported on the portal, retrospectively.

2. July 13, 2026 at 9:19 AM UTCresolved

   The record processing laag has been reduced to normal levels.

1. July 7, 2026 at 9:40 PM UTCidentified

   Partial Outage on IMSI2 and IMSI5

2. July 8, 2026 at 1:22 AM UTCresolved

   Issue has been identified, a fix was set in place and service was confirmed to be restored.

1. July 7, 2026 at 12:09 PM UTCinvestigating

   Our engineers are investigating an issue of calls originating via Telnyx SG numbers being rejected with DNO D46.

2. July 7, 2026 at 12:22 PM UTCmonitoring

   A fix has been put in place to resolve the issue as of 12:14pm UTC, and test calls are now routing without DNO rejection. We are continuing to monitor.

3. July 10, 2026 at 11:02 AM UTCresolved

   This issue was resolved.