OneSignal Status
System status
View historical uptime →Incident overview
Total incidents
9
Active now
0
Resolved
9
Avg. resolution
4h 28m
Recent incidents
View all →Database incident - impacting app IDs starting with e
Subscription API - Creation Failures
Intermittent errors on /api/v1/notifications api
Apple push notifications failing in about 3% of cases
Message events on user and subscription profiles slow and timing out
Issue has been identified
Issue identified and additional resources being added
Journey / Event Streams/Outbound Data Integrations - delayed processing
Journeys - delayed processing
Frequently asked questions
Is OneSignal down right now?
OneSignal is currently operational. DevHelm monitors OneSignal's official status page continuously and updates this page every 5 minutes.
What is OneSignal's current uptime?
OneSignal has a measured 30-day uptime of 100.00%. Over the last 24 hours, uptime is 100.00%, and over 7 days it is 100.00%. These figures are computed from OneSignal's official status page data.
How many incidents has OneSignal had recently?
OneSignal has experienced 9 incidents in the recent monitoring window. Resolved incidents were fixed in an average of 4h 28m. All incidents are currently resolved.
What components does OneSignal monitor?
DevHelm tracks 9 individual components for OneSignal, including Dashboard / UI, APIs & SDK Endpoints, Push, Email, SMS, and 4 more. Each component has its own status and 90-day uptime history shown above.
How can I get notified about OneSignal outages?
You can subscribe to OneSignal's incident feed via Atom/RSS at devhelm.io/status/onesignal/feed.xml for use in any feed reader. For real-time alerts via Slack, email, PagerDuty, or webhooks, add OneSignal as a dependency in your DevHelm workspace.
About OneSignal status monitoring
This page provides real-time operational status for OneSignal, powered by DevHelm's continuous monitoring infrastructure. We track OneSignal's official status page and aggregate component-level data into uptime percentages, incident timelines, and historical trends.
OneSignal status data is refreshed every 5 minutes. We currently track 9 individual components, each with its own operational status and 90-day uptime history.
Uptime percentages represent the proportion of time all monitored components reported operational status. Incident data comes from vendor-published incident timelines and includes status updates, affected components, and resolution times.
Track OneSignal in your stack
Get alerted when OneSignal has issues — before your users notice. Set up in 30 seconds.