Historial de interrupciones de Onesignal

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

   **What’s happening:** Apple push notifications are failing in about 3% of cases. "Unknown delivery error" or "APNS failed to provide a response" error responses may be seen. **Who’s affected:** • Customers using Apple Push Notifications **Current Status:** We are investigating the issue and will provide an update in 20

2. August 4, 2026 at 6:45 PM UTCidentified

   We have identified the root cause and are working towards a resolution. There was a slight change in how Apple's push notification connections work. We will provide another update in 20 minutes.

3. August 4, 2026 at 6:46 PM UTCmonitoring

   We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. We will provide another update in 20 minutes.

4. August 4, 2026 at 7:24 PM UTCresolved

   The issue has been resolved. All impacted systems are now operating normally.

1. July 30, 2026 at 4:52 PM UTCinvestigating

   **Qué está pasando:** Carga de mensajes eventos en el usuario y perfiles de suscripción es el momento oportuno. **Quién está afectado:** • Algunos clientes pueden experimentar tiempos de carga lentos o timeouts al cargar eventos de mensajes en el perfil de usuario **Estado actual:** Estamos investigando el problema y proporcionaremos una actualización en 30 minutos

2. July 30, 2026 at 5:32 PM UTCresolved

   La cuestión se ha resuelto. Todos los sistemas impactados están operando normalmente.

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

1. July 20, 2026 at 5:56 PM UTCidentified

   Hemos identificado la causa raíz y estamos trabajando para una resolución.

2. July 20, 2026 at 5:56 PM UTCmonitoring

   Hemos aplicado una mitigación que resuelve el impacto.

3. July 20, 2026 at 5:57 PM UTCresolved

   La cuestión se ha resuelto. Todos los sistemas impactados están operando normalmente.

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

1. July 20, 2026 at 4:16 PM UTCidentified

   Hemos identificado la causa raíz y estamos agregando recursos adicionales para manejar mejor la carga. Actualmente los componentes afectados son viajes, corrientes de eventos e integraciones de datos desbordadas.

2. July 21, 2026 at 5:24 PM UTCresolved

   La cuestión se ha resuelto. Todos los sistemas impactados están operando normalmente a partir del lunes 11:00 AM PDT.

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

1. July 20, 2026 at 2:51 PM UTCinvestigating

   **Qué está pasando:** Los viajes y las integraciones de webhook están experimentando un procesamiento retrasado. **Quién está afectado:** Todos los clientes que utilizan las integraciones de Viajes o Webhook son impactados. **Estado actual:** Estamos investigando el problema y proporcionaremos una actualización en 20 minutos.

2. July 20, 2026 at 3:16 PM UTCinvestigating

   Todavía estamos investigando el tema. Vamos a proporcionar otra actualización en 20 minutos

3. July 20, 2026 at 3:27 PM UTCinvestigating

   Todavía estamos investigando el tema. Los viajes y las corrientes de eventos / las integraciones de datos de salida se retrasan. Proporcionaremos otra actualización en 20 minutos.

4. July 21, 2026 at 3:39 PM UTCresolved

   La cuestión se ha resuelto. Todos los sistemas impactados funcionan normalmente desde las 11:00 AM PT Lunes.

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

1. July 16, 2026 at 3:32 PM UTCinvestigating

   **Qué está pasando:** El procesamiento de los viajes se retrasa **Quién está afectado:** • Todos los clientes usando la función Viajes **Estado actual:** Estamos investigando el problema y proporcionaremos una actualización en 15 minutos.

2. July 16, 2026 at 3:45 PM UTCinvestigating

   **Qué está pasando:** El procesamiento de los viajes se retrasa **Quién está afectado:** • Todos los clientes usando la función Viajes **Estado actual:** Estamos investigando el problema y proporcionaremos una actualización en 15 minutos

3. July 16, 2026 at 4:11 PM UTCidentified

   Hemos identificado la causa raíz y estamos trabajando para una resolución. Vamos a proporcionar otra actualización en 20 minutos

4. July 16, 2026 at 5:10 PM UTCmonitoring

   Hemos aplicado correcciones. • Los viajes se retrasan entre 30 y 45 minutos • Los segmentos del evento del mensaje podrían tardar ~45 minutos en llegar en línea

5. July 16, 2026 at 6:27 PM UTCmonitoring

   Además de los retrasos del segmento de viajes y mensajes, los retrasos de entrega de Webhook son actualmente ~1.2h. Vamos a proporcionar otra actualización en 20.

6. July 16, 2026 at 7:46 PM UTCmonitoring

   Seguimos experimentando retrasos en el rendimiento a medida que se añaden más recursos a nuestros sistemas.

7. July 16, 2026 at 11:15 PM UTCmonitoring

   Seguimos monitoreando el sistema a medida que los datos se replican a través de recursos adicionales.

8. July 17, 2026 at 9:07 AM UTCresolved

   La cuestión se ha resuelto. Todos los sistemas impactados están operando normalmente.

9. July 17, 2026 at 5:03 PM UTCmonitoring

   Estamos monitoreando el sistema a medida que los datos se replican a través de recursos adicionales.

10. July 17, 2026 at 8:52 PM UTCmonitoring

    Actualmente estamos añadiendo más recursos, pero sabemos que estamos experimentando corrientes de eventos y retrasos de integración de la exportación de datos.

11. July 17, 2026 at 10:12 PM UTCmonitoring

    Actualmente estamos añadiendo más recursos, pero sabemos que estamos experimentando viajes, secuencias de eventos y retrasos de integración de la exportación de datos.

12. July 17, 2026 at 11:06 PM UTCresolved

    La cuestión se ha resuelto. Todos los sistemas impactados están operando normalmente. Las corrientes de eventos, la integración de la exportación de datos y los viajes funcionan normalmente ahora.

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

1. July 6, 2026 at 5:05 PM UTCinvestigating

   **What’s happening:** Some customers are experiencing delayed delivery of event streams and webhooks **Who’s affected:** All customers using event streams and webhooks **Current Status:** We are investigating the issue and will provide an update in 15 minutes

2. July 6, 2026 at 5:11 PM UTCmonitoring

   We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. We will provide another update in 15 minutes.

3. July 6, 2026 at 6:20 PM UTCresolved

   The issue has been resolved. All impacted systems are now operating normally.

1. July 1, 2026 at 10:11 PM UTCidentified

   We have identified the root cause and are working towards a resolution. Customers may experience users not progressing through their Journeys We will provide another update in 30 minutes.

2. July 1, 2026 at 10:39 PM UTCmonitoring

   We have performed the necessary mitigation and customer journeys are now progressing successfully. Some customers may experience a 5-10 minutes lag

3. July 1, 2026 at 10:50 PM UTCresolved

   The issue has been resolved. All impacted systems are now operating normally.

1. June 25, 2026 at 8:11 AM UTCinvestigating

   **What’s happening:** Analytics and reporting could be delayed. **Who’s affected:** All customers _may_ be affected **Current Status:** We are investigating the issue and will provide an update in 15m

2. June 25, 2026 at 8:34 AM UTCmonitoring

   We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. Analytics are delayed, but we’re processing the lag. We will provide another update in 15 minutes.

3. June 25, 2026 at 8:49 AM UTCresolved

   The issue has been resolved. All impacted systems are now operating normally. The analytic lag is totally processed.

1. June 22, 2026 at 7:20 AM UTCresolved

   Due to an infrastructure issue, some customers were temporarily unable to view message events on the user and subscription profile pages. The issue has since been resolved.

1. June 17, 2026 at 6:24 AM UTCinvestigating

   **What’s happening:** Delivery of inteligent/timezone notifications will be delayed, we’re investigating the situation **Who’s affected:** • All customers _may_ be affected **Current Status:** We are investigating the issue and will provide an update in 10 minutes

2. June 17, 2026 at 6:38 AM UTCidentified

   We have identified the root cause and are working towards a resolution. We will provide another update in 15 minutes

3. June 17, 2026 at 6:55 AM UTCresolved

   We have applied a mitigation that resolves the impact. We are monitoring to confirm effectiveness. Intelligent/timezone notifications were delayed for 45m. **No** regular direct notifications were impacted.

1. June 9, 2026 at 7:01 PM UTCinvestigating

   **What’s happening:** Users may be experiencing issues interacting with the dashboard **Who’s affected:** • Customers interacting with the dashboard **Current Status:** We are investigating the issue and will provide an update in [2 minutes]

2. June 9, 2026 at 7:13 PM UTCresolved

   The issue has been resolved. All impacted systems are now operating normally. The root cause of the issue was a faulty configuration change to our authentication system. The change has been reverted and all systems now operational.

1. June 1, 2026 at 11:28 PM UTCinvestigating

   **What’s happening:** We are currently investigating an issue affecting Dashboard login. Users attempting to authenticate may experience login failures or be unable to access their accounts. Our team is actively working to identify the root cause and restore normal functionality. **Who’s affected:** Users who need to sign into the dashboard-It may be unable to log in. **Current Status:** We are investigating the issue and will provide an update in 30 minutes

2. June 1, 2026 at 11:46 PM UTCidentified

   We have identified the root cause and are working towards a resolution. We will provide another update in 20 minutes.

3. June 2, 2026 at 12:12 AM UTCresolved

   The issue has been resolved. All impacted systems are now operating normally. Dashboard logins are now resolved.

1. May 22, 2026 at 8:50 PM UTCmonitoring

   Event Streams, Journey Webhooks, and Data Warehouse exports are delayed. We have identified the cause and resolved the issue. Systems are working through the backlog of events.

2. May 22, 2026 at 10:16 PM UTCresolved

   The issue has been resolved. All impacted systems are now operating normally.

1. May 22, 2026 at 7:37 PM UTCinvestigating

   **What’s happening:** Timezone based and intelligent deliveries impacted because of backlog of messages. **Who’s affected:** • Any free customers using Timezone-based Delivery, Intelligent Delivery, or Retry Delivery. **Current Status:** We are investigating the issue and will provide an update in 30 minutes

2. May 22, 2026 at 7:46 PM UTCidentified

   We've identified the root cause and are actively implementing mitigations.

3. May 22, 2026 at 8:23 PM UTCresolved

   The necessary mitigations have been applied and all systems are now operating normally.

1. May 11, 2026 at 6:19 PM UTCinvestigating

   **What’s happening:** Some customers are unable to access the dashboard or API **Who’s affected:** • Customers with an app id starting with 2 **Current Status:** We are investigating the issue and will provide an update in 15 minutes

2. May 11, 2026 at 6:36 PM UTCmonitoring

   We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. We will provide another update in 30 minutes.

3. May 11, 2026 at 6:44 PM UTCresolved

   The issue has been resolved. All impacted systems are now operating normally.

1. April 24, 2026 at 6:25 PM UTCinvestigating

   **What’s happening:** Dashboard and API users currently experiencing sporadic instability **Who’s affected:** • All customers using the dashboard, creating messages in the dashboard **Current Status:** We are investigating the issue and will provide an update in a few minutes Update: we are scaling hardware resources to resolve this issue.

2. April 24, 2026 at 7:16 PM UTCresolved

   The issue has been resolved. All impacted systems are now operating normally. Hardware resources have been scaled up.

1. April 13, 2026 at 10:00 PM UTCmonitoring

   We have applied a mitigation that should resolve the impact of degraded dashboard user experience and potential delivery failure for dashboard users. We are monitoring to confirm effectiveness. We will provide another update in 5.

2. April 13, 2026 at 10:07 PM UTCresolved

   Incident is resolved.

1. April 9, 2026 at 6:58 PM UTCmonitoring

   During a brief period, some customers may have experienced errors while loading their app metrics. We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. During this period, some customers may have experienced errors loading app metrics on the OneSignal dashboard for analytics. We will provide another update in 30 minutes.

2. April 9, 2026 at 7:37 PM UTCmonitoring

   Our engineering team continues to monitor our systems. We are no longer seeing any impact and all systems are operational.

3. April 9, 2026 at 7:54 PM UTCresolved

   The issue has been resolved. All impacted systems are now operating normally.

1. April 9, 2026 at 2:46 PM UTCinvestigating

   **What’s happening:** Customers attempting to use the dashboard and API are encountering errors. **Who’s affected:** All customers attempting to use the dashboard and API **Current Status:** We are investigating the issue and will provide an update in 10 minutes

2. April 9, 2026 at 2:55 PM UTCidentified

   We have identified the root cause and are working towards a resolution. We will provide another update in 10 minutes.

3. April 9, 2026 at 2:59 PM UTCmonitoring

   We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. We will provide another update in 10 minutes.

4. April 9, 2026 at 3:06 PM UTCresolved

   The issue has been resolved. All impacted systems are now operating normally.