Histórico de interrupções do Onesignal

1. 4 Eost 2026 da 17:20 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. 4 Eost 2026 da 18:45 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. 4 Eost 2026 da 18:46 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. 4 Eost 2026 da 19:24 UTCresolved

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

1. 30 Gouere 2026 da 16:52 UTCinvestigating

   **O que está acontecendo:** Carregar eventos de mensagem no usuário e perfis de assinatura está cronometrando. **Quem é afectado: ** • Alguns clientes podem experimentar tempos de carga lentos ou timeouts ao carregar eventos de mensagem no perfil do usuário ** Estado atual:** Estamos investigando o problema e forneceremos uma atualização em 30 minutos

2. 30 Gouere 2026 da 17:32 UTCresolved

   A questão foi resolvida. Todos os sistemas impactados estão funcionando normalmente.

Traduzido automaticamente da atualização oficial do incidente.

1. 20 Gouere 2026 da 17:56 UTCidentified

   Identificámos a causa principal e estamos a trabalhar para uma resolução.

2. 20 Gouere 2026 da 17:56 UTCmonitoring

   Aplicámos uma mitigação que resolve o impacto.

3. 20 Gouere 2026 da 17:57 UTCresolved

   A questão foi resolvida. Todos os sistemas impactados estão funcionando normalmente.

Traduzido automaticamente da atualização oficial do incidente.

1. 20 Gouere 2026 da 16:16 UTCidentified

   Identificamos a causa raiz e estamos adicionando recursos adicionais para melhor lidar com a carga. Os componentes atualmente afetados são Viagens, Fluxos de Eventos e Integração de Dados de Saída.

2. 21 Gouere 2026 da 17:24 UTCresolved

   A questão foi resolvida. Todos os sistemas impactados estão funcionando normalmente a partir de segunda-feira 11:00 PDT.

Traduzido automaticamente da atualização oficial do incidente.

1. 20 Gouere 2026 da 14:51 UTCinvestigating

   **O que está acontecendo:** Viagens e integrações webhook estão experimentando processamento atrasado. **Quem é afectado: ** Todos os clientes que usam Journeys ou integrações Webhook são impactados. ** Estado atual:** Estamos investigando o problema e forneceremos uma atualização em 20 minutos.

2. 20 Gouere 2026 da 15:16 UTCinvestigating

   Ainda estamos a investigar a questão. Forneceremos outra atualização em 20 minutos

3. 20 Gouere 2026 da 15:27 UTCinvestigating

   Ainda estamos a investigar a questão. Viagens e Fluxos de Eventos/ Integração de Dados de Saída estão atrasados. Forneceremos outra atualização em 20 minutos.

4. 21 Gouere 2026 da 15:39 UTCresolved

   A questão foi resolvida. Todos os sistemas impactados funcionam normalmente desde as 11:00 horas da segunda-feira.

Traduzido automaticamente da atualização oficial do incidente.

1. 16 Gouere 2026 da 15:32 UTCinvestigating

   **O que está acontecendo:** O processamento das viagens está atrasado **Quem é afectado: ** • Todos os clientes usando o recurso Journeys ** Estado atual:** Estamos investigando o problema e forneceremos uma atualização em 15 minutos.

2. 16 Gouere 2026 da 15:45 UTCinvestigating

   **O que está acontecendo:** O processamento das viagens está atrasado **Quem é afectado: ** • Todos os clientes usando o recurso Journeys ** Estado atual:** Estamos investigando o problema e vamos fornecer uma atualização em 15 minutos

3. 16 Gouere 2026 da 16:11 UTCidentified

   Identificámos a causa principal e estamos a trabalhar para uma resolução. Forneceremos outra atualização em 20 minutos

4. 16 Gouere 2026 da 17:10 UTCmonitoring

   Aplicámos correcções. • Viagens é 30-45 minutos de atraso • Segmentos de eventos de mensagens podem levar ~45 minutos para entrar online

5. 16 Gouere 2026 da 18:27 UTCmonitoring

   Além dos atrasos no segmento Journeys and Message Event, os atrasos na entrega do Webhook são atualmente de ~1.2h. Nós forneceremos outra atualização em 20.

6. 16 Gouere 2026 da 19:46 UTCmonitoring

   Continuamos a experimentar atrasos de desempenho à medida que mais recursos são adicionados aos nossos sistemas.

7. 16 Gouere 2026 da 23:15 UTCmonitoring

   Continuamos a monitorar o sistema à medida que os dados são replicados através de recursos adicionais.

8. 17 Gouere 2026 da 09:07 UTCresolved

   A questão foi resolvida. Todos os sistemas impactados estão funcionando normalmente.

9. 17 Gouere 2026 da 17:03 UTCmonitoring

   Estamos monitorando o sistema à medida que os dados são replicados através de recursos adicionais.

10. 17 Gouere 2026 da 20:52 UTCmonitoring

    Atualmente estamos adicionando mais recursos, mas estamos cientes de que estamos passando por fluxos de eventos e atrasos na integração de exportação de dados.

11. 17 Gouere 2026 da 22:12 UTCmonitoring

    Atualmente estamos adicionando mais recursos, mas estamos cientes de que estamos passando por jornadas, fluxos de eventos e atrasos na integração de exportação de dados.

12. 17 Gouere 2026 da 23:06 UTCresolved

    A questão foi resolvida. Todos os sistemas impactados estão funcionando normalmente. Fluxos de eventos, integração de exportação de dados e viagens estão funcionando normalmente agora.

Traduzido automaticamente da atualização oficial do incidente.

1. 6 Gouere 2026 da 17:05 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. 6 Gouere 2026 da 17:11 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. 6 Gouere 2026 da 18:20 UTCresolved

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

1. 1 Gouere 2026 da 22:11 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. 1 Gouere 2026 da 22:39 UTCmonitoring

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

3. 1 Gouere 2026 da 22:50 UTCresolved

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

1. 25 Mezheven 2026 da 08:11 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. 25 Mezheven 2026 da 08:34 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. 25 Mezheven 2026 da 08:49 UTCresolved

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

1. 22 Mezheven 2026 da 07:20 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. 17 Mezheven 2026 da 06:24 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. 17 Mezheven 2026 da 06:38 UTCidentified

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

3. 17 Mezheven 2026 da 06:55 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. 9 Mezheven 2026 da 19:01 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. 9 Mezheven 2026 da 19:13 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. 1 Mezheven 2026 da 23:28 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. 1 Mezheven 2026 da 23:46 UTCidentified

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

3. 2 Mezheven 2026 da 00:12 UTCresolved

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

1. 22 Mae 2026 da 20:50 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. 22 Mae 2026 da 22:16 UTCresolved

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

1. 22 Mae 2026 da 19:37 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. 22 Mae 2026 da 19:46 UTCidentified

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

3. 22 Mae 2026 da 20:23 UTCresolved

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

1. 11 Mae 2026 da 18:19 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. 11 Mae 2026 da 18:36 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. 11 Mae 2026 da 18:44 UTCresolved

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

1. 24 Ebrel 2026 da 18:25 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. 24 Ebrel 2026 da 19:16 UTCresolved

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

1. 13 Ebrel 2026 da 22:00 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. 13 Ebrel 2026 da 22:07 UTCresolved

   Incident is resolved.

1. 9 Ebrel 2026 da 18:58 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. 9 Ebrel 2026 da 19:37 UTCmonitoring

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

3. 9 Ebrel 2026 da 19:54 UTCresolved

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

1. 9 Ebrel 2026 da 14:46 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. 9 Ebrel 2026 da 14:55 UTCidentified

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

3. 9 Ebrel 2026 da 14:59 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. 9 Ebrel 2026 da 15:06 UTCresolved

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