OneSignal incident
Intermittent errors from Notification Create endpoint
Affected components
Update timeline
- 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)
Looking to track OneSignal downtime and outages?
Pingoru polls OneSignal's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when OneSignal reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track OneSignal alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required