One Signal Outage History

OneSignal experienced database connectivity issues that caused degraded dashboard performance and potential delivery failures for dashboard users. The service team applied a mitigation to resolve the impact and monitored its effectiveness. The incident lasted 9 minutes and was classified as minor severity.

OneSignal experienced a 58-minute incident where some customers encountered errors while loading app metrics on the analytics dashboard. The engineering team applied a mitigation to resolve the issue and monitored the systems until confirming full operational status. All systems returned to normal operation with no ongoing impact.

OneSignal experienced a major outage affecting their dashboard and API services, causing errors for all customers attempting to access these systems. The incident lasted 21 minutes, during which the team identified the root cause and applied a mitigation to resolve the impact. The service was restored and monitored to confirm the fix was effective.

OneSignal experienced increased latency across their Dashboard and API services, affecting all customers for 47 minutes. The engineering team identified the root cause and deployed a resolution. The services were restored to normal performance and the team continued monitoring to ensure stability.

OneSignal's Notification Create endpoint experienced elevated HTTP 500 error rates for 52 minutes, causing failures when customers attempted to create new notifications through the public API. The engineering team resolved the issue by rolling over faulty pods while investigating the root cause.

OneSignal experienced email delivery delays and failures for 3.1 hours due to an unhealthy notifications API instance that caused 27 delivery jobs to become stuck in a terminating state. The incident began with increased lag in email deliveries around 9am and escalated to completely stuck delivery jobs that were not processing. The team identified the root cause, worked to retry the failed deliveries, and restored normal email delivery functionality.

One Signal experienced 1-hour delays in processing data feeds, affecting customers with journeys that rely on data feeds. The service applied a mitigation after 21 minutes and was monitoring to confirm the resolution's effectiveness.

Between 16:54 UTC and 17:03 UTC, OneSignal APIs experienced errors and degraded performance, specifically affecting customers with app IDs beginning with the prefix "c". The systems automatically recovered after 9 minutes, and additional mitigation measures were implemented to prevent recurrence.