- Detected by Pingoru
- Jun 17, 2026, 06:55 AM UTC
- Resolved
- Jun 17, 2026, 06:55 AM UTC
- Duration
- —
Affected: PushEmailSMSIn-App Messages
Timeline · 3 updates
-
investigating Jun 17, 2026, 06:24 AM UTC
Status: Investigating 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 Affected components Email (Degraded performance) SMS (Degraded performance) In-App Messages (Degraded performance) Push (Degraded performance)
-
identified Jun 17, 2026, 06:38 AM UTC
Status: Identified We have identified the root cause and are working towards a resolution. We will provide another update in 15 minutes Affected components In-App Messages (Degraded performance) Push (Degraded performance) Email (Degraded performance) SMS (Degraded performance)
-
resolved Jun 17, 2026, 06:55 AM UTC
Status: Resolved 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. Affected components Email (Operational) SMS (Operational) In-App Messages (Operational) Push (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 09, 2026, 07:13 PM UTC
- Resolved
- Jun 09, 2026, 07:13 PM UTC
- Duration
- —
Affected: Dashboard / UI
Timeline · 2 updates
-
investigating Jun 09, 2026, 07:01 PM UTC
Status: Investigating 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] Affected components Dashboard / UI (Partial outage)
-
resolved Jun 09, 2026, 07:13 PM UTC
Status: Resolved 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. Affected components Dashboard / UI (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 02, 2026, 12:12 AM UTC
- Resolved
- Jun 02, 2026, 12:12 AM UTC
- Duration
- —
Affected: Dashboard / UI
Timeline · 3 updates
-
investigating Jun 01, 2026, 11:28 PM UTC
Status: Investigating 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 Affected components Dashboard / UI (Partial outage)
-
identified Jun 01, 2026, 11:46 PM UTC
Status: Identified We have identified the root cause and are working towards a resolution. We will provide another update in 20 minutes. Affected components Dashboard / UI (Partial outage)
-
resolved Jun 02, 2026, 12:12 AM UTC
Status: Resolved The issue has been resolved. All impacted systems are now operating normally. Dashboard logins are now resolved. Affected components Dashboard / UI (Operational)
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 10:16 PM UTC
- Resolved
- May 22, 2026, 10:16 PM UTC
- Duration
- —
Affected: Integrations
Timeline · 2 updates
-
monitoring May 22, 2026, 08:50 PM UTC
Status: Monitoring 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. Affected components Integrations (Degraded performance)
-
resolved May 22, 2026, 10:16 PM UTC
Status: Resolved The issue has been resolved. All impacted systems are now operating normally. [Include any relevant customer facing specifics]. Affected components Integrations (Operational)
Read the full incident report →
- Detected by Pingoru
- May 22, 2026, 08:23 PM UTC
- Resolved
- May 22, 2026, 08:23 PM UTC
- Duration
- —
Affected: PushEmailSMSIn-App Messages
Timeline · 3 updates
-
investigating May 22, 2026, 07:37 PM UTC
Status: Investigating 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 Affected components Email (Degraded performance) SMS (Degraded performance) In-App Messages (Degraded performance) Push (Degraded performance)
-
identified May 22, 2026, 07:46 PM UTC
Status: Identified We've identified the root cause and are actively implementing mitigations. Affected components Email (Degraded performance) SMS (Degraded performance) In-App Messages (Degraded performance) Push (Degraded performance)
-
resolved May 22, 2026, 08:23 PM UTC
Status: Resolved The necessary mitigations have been applied and all systems are now operating normally. Affected components Email (Operational) SMS (Operational) In-App Messages (Operational) Push (Operational)
Read the full incident report →
- Detected by Pingoru
- May 11, 2026, 06:44 PM UTC
- Resolved
- May 11, 2026, 06:44 PM UTC
- Duration
- —
Affected: APIs & SDK EndpointsDashboard / UI
Timeline · 3 updates
-
investigating May 11, 2026, 06:19 PM UTC
Status: Investigating 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 Affected components Dashboard / UI (Partial outage) APIs & SDK Endpoints (Partial outage)
-
monitoring May 11, 2026, 06:36 PM UTC
Status: Monitoring We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. We will provide another update in 30 minutes. Affected components APIs & SDK Endpoints (Operational) Dashboard / UI (Operational)
-
resolved May 11, 2026, 06:44 PM UTC
Status: Resolved The issue has been resolved. All impacted systems are now operating normally. Affected components Dashboard / UI (Operational) APIs & SDK Endpoints (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 07:16 PM UTC
- Resolved
- Apr 24, 2026, 07:16 PM UTC
- Duration
- —
Affected: APIs & SDK EndpointsDashboard / UI
Timeline · 2 updates
-
investigating Apr 24, 2026, 06:25 PM UTC
Status: Investigating 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. Affected components Dashboard / UI (Partial outage) APIs & SDK Endpoints (Partial outage)
-
resolved Apr 24, 2026, 07:16 PM UTC
Status: Resolved The issue has been resolved. All impacted systems are now operating normally. Hardware resources have been scaled up. Affected components Dashboard / UI (Operational) APIs & SDK Endpoints (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 13, 2026, 10:07 PM UTC
- Resolved
- Apr 13, 2026, 10:07 PM UTC
- Duration
- —
Affected: PushEmailSMSIn-App MessagesDashboard / UI
Timeline · 2 updates
-
monitoring Apr 13, 2026, 10:00 PM UTC
Status: Monitoring 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. Affected components Dashboard / UI (Partial outage) Email (Partial outage) SMS (Partial outage) In-App Messages (Partial outage) Push (Partial outage)
-
resolved Apr 13, 2026, 10:07 PM UTC
Status: Resolved Incident is resolved. Affected components Dashboard / UI (Operational) Email (Operational) SMS (Operational) In-App Messages (Operational) Push (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 07:54 PM UTC
- Resolved
- Apr 09, 2026, 07:54 PM UTC
- Duration
- —
Affected: Analytics & ReportingDashboard / UI
Timeline · 3 updates
-
monitoring Apr 09, 2026, 06:58 PM UTC
Status: Monitoring 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. Affected components Analytics & Reporting (Degraded performance) Dashboard / UI (Degraded performance)
-
monitoring Apr 09, 2026, 07:37 PM UTC
Status: Monitoring Our engineering team continues to monitor our systems. We are no longer seeing any impact and all systems are operational. Affected components Analytics & Reporting (Operational) Dashboard / UI (Operational)
-
resolved Apr 09, 2026, 07:54 PM UTC
Status: Resolved The issue has been resolved. All impacted systems are now operating normally. Affected components Analytics & Reporting (Operational) Dashboard / UI (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 03:06 PM UTC
- Resolved
- Apr 09, 2026, 03:06 PM UTC
- Duration
- —
Affected: APIs & SDK EndpointsDashboard / UI
Timeline · 3 updates
-
investigating Apr 09, 2026, 02:10 PM UTC
Status: Investigating What’s happening: Dashboard and API request are increased Who’s affected: All customers may be affected Current Status: We are investigating the issue and will provide an update in 10 minutes Affected components Dashboard / UI (Degraded performance) APIs & SDK Endpoints (Degraded performance)
-
monitoring Apr 09, 2026, 02:33 PM UTC
Status: Monitoring We have identified the root cause and rolled a resolution. We’re currently monitoring and expect dashboard and API to work as expected again, We will provide another update in 5 minutes Affected components Dashboard / UI (Operational) APIs & SDK Endpoints (Operational)
-
resolved Apr 09, 2026, 03:06 PM UTC
Status: Resolved The issue has been resolved. All impacted systems are now operating normally. Affected components Dashboard / UI (Operational) APIs & SDK Endpoints (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 03:04 PM UTC
- Resolved
- Apr 09, 2026, 03:04 PM UTC
- Duration
- —
Affected: APIs & SDK EndpointsDashboard / UI
Timeline · 4 updates
-
investigating Apr 09, 2026, 02:37 PM UTC
Status: Investigating 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 Affected components Dashboard / UI (Full outage) APIs & SDK Endpoints (Full outage)
-
identified Apr 09, 2026, 02:50 PM UTC
Status: Identified We have identified the root cause and are working towards a resolution. We will provide another update in 10 minutes. Affected components Dashboard / UI (Full outage) APIs & SDK Endpoints (Full outage)
-
monitoring Apr 09, 2026, 02:54 PM UTC
Status: Monitoring We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. We will provide another update in 10 minutes. Affected components Dashboard / UI (Full outage) APIs & SDK Endpoints (Full outage)
-
resolved Apr 09, 2026, 03:04 PM UTC
Status: Resolved The issue has been resolved. All impacted systems are now operating normally. Affected components Dashboard / UI (Operational) APIs & SDK Endpoints (Operational)
Read the full incident report →
- Detected by Pingoru
- Apr 08, 2026, 06:34 PM UTC
- Resolved
- Apr 01, 2026, 01:00 PM UTC
- Duration
- —
Read the full incident report →
- Detected by Pingoru
- Mar 20, 2026, 09:01 PM UTC
- Resolved
- Mar 20, 2026, 09:01 PM UTC
- Duration
- —
Affected: APIs & SDK Endpoints
Timeline · 3 updates
-
investigating Mar 20, 2026, 08:13 PM UTC
Status: Investigating Notification#Create is experiencing elevated rates of HTTP 500 status codes. The team is investigating a root cause and is rolling over the faulty pods. We'll give another status update in the next 30 minutes Affected components APIs & SDK Endpoints (Partial outage)
-
investigating Mar 20, 2026, 08:52 PM UTC
Status: Investigating What’s happening: We're still seeing some elevated error rates in the Notification#Create endpoint Who’s affected: • Customers using the public Notifications api endpoint may experience failures when trying to create a new notification Current Status: We are investigating the issue and will provide an update in 1 hour Affected components APIs & SDK Endpoints (Partial outage)
-
resolved Mar 20, 2026, 09:01 PM UTC
Status: Resolved The issue has been resolved. All impacted systems are now operating normally. Over the course of the incident a few thousand HTTP 500s occurred. Affected components APIs & SDK Endpoints (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 20, 2026, 08:28 PM UTC
- Resolved
- Mar 20, 2026, 08:28 PM UTC
- Duration
- —
Affected: Email
Timeline · 4 updates
-
investigating Mar 20, 2026, 05:25 PM UTC
Status: Investigating We are still investigating the issue. Around 9am this morning, we noticed an increase in lag on email deliveries. That has now transitioned into stuck delivery jobs that are not processing. The team is investigating a way to get the delivery jobs to continue, but until then expect potential delays and a potential need to resend emails. We will provide another update in 30 minutes. Affected components Email (Full outage)
-
investigating Mar 20, 2026, 06:07 PM UTC
Status: Investigating The investigation is still ongoing. So far we have 27 delivery jobs that we know are stuck, but we are still still determining the scope of the delays. Affected components Email (Full outage)
-
monitoring Mar 20, 2026, 06:27 PM UTC
Status: Monitoring We have identified a small number of notifications that have been impacted and the delivery jobs have failed. The team is working on retrying those deliveries. The source of the incident is from one of our notifications api instances became unhealthy, causing 27 jobs to remain in a terminating state, and thus they were not able to retry. The incident status is being updated to monitoring, and any new deliveries going out should succeed. Affected components Email (Operational)
-
resolved Mar 20, 2026, 08:28 PM UTC
Status: Resolved The team has been monitoring the delivery pods and is no longer seeing any errors or stuck deliveries. All previously stuck notifications have been successfully retried. Affected components Email (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 10:55 PM UTC
- Resolved
- Mar 19, 2026, 10:55 PM UTC
- Duration
- —
Affected: JourneysDashboard / UI
Timeline · 2 updates
-
investigating Mar 19, 2026, 10:55 PM UTC
Status: Investigating What’s happening: Restart of an internal service caused many connections to be reset at once, which led to errors upon reconnect. Who’s affected: 5% of customers during a 2 min period • The dashboard / UI • Notifications create • Delayed journey messages for 2 min Current Status: This is resolved Affected components Dashboard / UI (Partial outage) Journeys (Partial outage)
-
resolved Mar 19, 2026, 10:55 PM UTC
Status: Resolved The issue has been resolved. All impacted systems are now operating normally. Affected components Dashboard / UI (Operational) Journeys (Operational)
Read the full incident report →
- Detected by Pingoru
- Mar 13, 2026, 04:28 PM UTC
- Resolved
- Mar 13, 2026, 04:28 PM UTC
- Duration
- —
Affected: Journeys
Timeline · 3 updates
-
investigating Mar 13, 2026, 04:10 PM UTC
Status: Investigating What’s happening: We are experiencing delays of 1h in processing of data feeds. Who’s affected: Customers with journeys using data feeds. Current Status: We are investigating the issue and will provide an update in 1h. Affected components Journeys (Degraded performance)
-
monitoring Mar 13, 2026, 04:20 PM UTC
Status: Monitoring We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. We will provide another update in 1h. Affected components Journeys (Degraded performance)
-
resolved Mar 13, 2026, 04:28 PM UTC
Status: Resolved The issue has been resolved. All impacted systems are now operating normally. Affected components Journeys (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 07:05 PM UTC
- Resolved
- Feb 25, 2026, 05:03 PM UTC
- Duration
- —
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 05:03 PM UTC
- Resolved
- Feb 25, 2026, 05:03 PM UTC
- Duration
- —
Affected: Dashboard / UI
Timeline · 2 updates
-
monitoring Feb 25, 2026, 04:54 PM UTC
Status: Monitoring Between 16:54 UTC and 17:03 UTC, some customers may have experienced errors when making requests to OneSignal APIs. Our systems automatically recovered; however, during this brief window, requests to certain APIs experienced degraded performance. This incident impacted only customers with app IDs beginning with the prefix "c". We have implemented a mitigation to address the issue and are actively monitoring to ensure it is fully resolved. We will provide another update in 30 minutes. Affected components Dashboard / UI (Degraded performance)
-
resolved Feb 25, 2026, 05:03 PM UTC
Status: Resolved There is no further impact and the system has been fully operational since 17:03 UTC Affected components Dashboard / UI (Operational)
Read the full incident report →
- Detected by Pingoru
- Feb 14, 2026, 04:10 PM UTC
- Resolved
- Feb 14, 2026, 04:10 PM UTC
- Duration
- —
Timeline · 3 updates
-
investigating Feb 14, 2026, 03:25 PM UTC
Status: Investigating What’s happening: Email and scheduled messages are experiencing a delivery delay Who’s affected: All customers actively sending emails & scheduled messages Current Status: We are investigating the issue and will provide an update in 30 minutes
-
identified Feb 14, 2026, 03:48 PM UTC
Status: Identified We have identified the root cause and are working towards a resolution. We will provide another update in 30 minutes.
-
resolved Feb 14, 2026, 04:10 PM UTC
Status: Resolved The issue has been resolved. All impacted systems are now operating normally.
Read the full incident report →
- Detected by Pingoru
- Feb 13, 2026, 11:18 PM UTC
- Resolved
- Feb 13, 2026, 11:18 PM UTC
- Duration
- —
Timeline · 3 updates
-
investigating Feb 13, 2026, 11:13 PM UTC
Status: Investigating What’s happening: We are experiencing a delay in processing and sending messages. Who’s affected: All messages being delivered are delayed. Current Status: We are investigating the issue and will provide an update in 15 minutes.
-
identified Feb 13, 2026, 11:13 PM UTC
Status: Identified We have identified the root cause and are working towards a resolution. We will provide another update in 10 minutes.
-
resolved Feb 13, 2026, 11:18 PM UTC
Status: Resolved The issue has been resolved. All impacted systems are now operating normally. All delayed messages have been processed.
Read the full incident report →
- Detected by Pingoru
- Feb 13, 2026, 12:30 AM UTC
- Resolved
- Feb 13, 2026, 12:30 AM UTC
- Duration
- —
Timeline · 3 updates
-
investigating Feb 13, 2026, 12:01 AM UTC
Status: Investigating What’s happening: We are seeing elevated error rates sending messages via Journeys. Who’s affected: All customers with Journeys currently processing messages Current Status: We are investigating the issue and will provide an update in 15 minutes.
-
identified Feb 13, 2026, 12:07 AM UTC
Status: Identified We have identified the root cause and are working towards a resolution. We will provide another update in 30 minutes.
-
resolved Feb 13, 2026, 12:30 AM UTC
Status: Resolved The issue has been resolved. All impacted systems are now operating normally.
Read the full incident report →
- Detected by Pingoru
- Feb 10, 2026, 06:00 PM UTC
- Resolved
- Feb 10, 2026, 06:00 PM UTC
- Duration
- —
Timeline · 8 updates
-
investigating Feb 10, 2026, 04:10 PM UTC
Status: Investigating What’s happening: Journey’s/webhooks processing is delayed. Who’s affected: • All customers using Journeys or Webhooks Current Status: We are investigating the issue and will provide an update in 15 minutes.
-
identified Feb 10, 2026, 04:26 PM UTC
Status: Identified We have identified the root cause and are working towards a resolution. Journeys and webhooks processing are interrupted. We will provide another update in 15 minutes.
-
identified Feb 10, 2026, 04:45 PM UTC
Status: Identified We have identified the root cause and are working towards a resolution. Journeys and webhooks processing are interrupted. We will provide another update in 15 minutes.
-
identified Feb 10, 2026, 05:06 PM UTC
Status: Identified We have identified the root cause and are working towards a resolution. Journeys and webhooks processing are interrupted. We will provide another update in 15 minutes.
-
identified Feb 10, 2026, 05:14 PM UTC
Status: Identified We have identified the root cause and are working towards a resolution. Webhooks is processing again and fully caught up. We’re working on a fix for Journeys. Processing for journeys is still interrupted. We will provide another update in 15 minutes.
-
monitoring Feb 10, 2026, 05:31 PM UTC
Status: Monitoring We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. We will provide another update in 10 minutes.
-
monitoring Feb 10, 2026, 05:42 PM UTC
Status: Monitoring We have confirmed the applied mitigation is working as expected. We are processing the backlog of delayed Journeys. We will provide another update in 30 minutes.
-
resolved Feb 10, 2026, 06:00 PM UTC
Status: Resolved The incident has been resolved. All delayed Journeys and Webhooks have been fully processed.
Read the full incident report →
- Detected by Pingoru
- Feb 03, 2026, 05:36 PM UTC
- Resolved
- Feb 03, 2026, 05:36 PM UTC
- Duration
- —
Affected: Dashboard / UI
Timeline · 2 updates
-
investigating Feb 03, 2026, 05:28 PM UTC
Status: Investigating What’s happening: The OneSignal dashboard is currently not loading. Who’s affected: • All customers using dashboard.onesignal.com Current Status: We have identified that Cloudflare is not serving our dashboard to users globally. We're investigating a fix. The outage is only on the dashboard, not on api endpoints. Affected components Dashboard / UI (Full outage)
-
resolved Feb 03, 2026, 05:36 PM UTC
Status: Resolved Cloudflare is having an issue with a recent worker build that rolled out. We have rolled back to a previous build and dashboard.onesignal.com is working again. We will continue to follow along at https://www.cloudflarestatus.com Affected components Dashboard / UI (Operational)
Read the full incident report →
- Detected by Pingoru
- Jan 29, 2026, 11:59 PM UTC
- Resolved
- Jan 29, 2026, 11:59 PM UTC
- Duration
- —
Affected: Dashboard / UI
Timeline · 2 updates
-
monitoring Jan 29, 2026, 11:43 PM UTC
Status: Monitoring For a brief period starting at 3:17 PM PST until 3:33 PM PST, customers were unable to connect to the OneSignal platform and APIs. We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. We will provide another update in 30 minutes. Affected components Dashboard / UI (Full outage)
-
resolved Jan 29, 2026, 11:59 PM UTC
Status: Resolved The issue has been resolved. All impacted systems are now operating normally. Affected components Dashboard / UI (Operational)
Read the full incident report →
- Detected by Pingoru
- Dec 05, 2025, 09:05 AM UTC
- Resolved
- Dec 05, 2025, 09:28 AM UTC
- Duration
- 23m
Read the full incident report →