Skip to main content

Is OneSignal Down?

No — OneSignal is up

Reachable from all 8 checked regions

Average response time: 49ms

Last checked · checks run every 6 hours

Official status page: https://status.onesignal.com

OneSignal uptime

100%
Last 7 days
—
Last 30 days
—
Last 90 days
—
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 4 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

4-day clean streak
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: no data
Aug 16: no data
Aug 17: no data
Aug 18: no data
Aug 19: no data
Aug 20: 100.00% uptime, 16 checks
Aug 21: 100.00% uptime, 39 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
Aug 24: no data
Jul 26 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
53ms
DNS 0ms TCP 2ms TLS 9ms TTFB 32ms
arn
52ms
DNS 0ms TCP 1ms TLS 7ms TTFB 27ms
bom
53ms
DNS 0ms TCP 4ms TLS 9ms TTFB 27ms
cdg
46ms
DNS 0ms TCP 1ms TLS 10ms TTFB 25ms
dfw
58ms
DNS 0ms TCP 2ms TLS 7ms TTFB 25ms
ewr
40ms
DNS 0ms TCP 2ms TLS 10ms TTFB 25ms
fra
46ms
DNS 0ms TCP 1ms TLS 8ms TTFB 35ms
gru
45ms
DNS 4ms TCP 2ms TLS 7ms TTFB 26ms
yyz
29ms
DNS 0ms TCP 1ms TLS 6ms TTFB 18ms

What OneSignal does

OneSignal delivers push notifications, in-app messages, SMS and email for mobile and web applications. It describes itself as serving more than 2 million businesses. Products use it as the delivery layer for transactional alerts and marketing campaigns alike, so an outage shows up as silence, with users simply never receiving the message, rather than as a visible error inside the product.

What an outage looks like

Notifications are accepted by the API but never arrive on devices, which is the hardest failure to notice because nothing errors. Scheduled campaigns and Journeys stall partway through a send. The dashboard is slow or will not load delivery reports, and analytics numbers flatten. In-app messages stop appearing while push still works, since OneSignal tracks those channels separately.

What to do about it

status.onesignal.com separates Dashboard and UI from APIs and SDK Endpoints, Messaging Delivery, Analytics and Reporting, Journeys and Integrations, so a reporting problem is distinguishable from a delivery one. Check Messaging Delivery before resending anything: a queued send that eventually lands will duplicate if you fire it again. Apple and Google push gateways sit downstream and can fail independently.

Is it down for everyone, or just you?

If this page says OneSignal is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

B
Braze
Twilio
Twilio
F
Firebase
K
Klaviyo

OneSignal outage FAQ

My notifications were accepted but never arrived. Is OneSignal down?
Check the Messaging Delivery component first, since the API can accept a send while delivery is degraded. A success response from OneSignal means the message was queued, not that a device received it. Delivery figures under Analytics and Reporting are the confirmation, and that component can itself be down, which makes the numbers look worse than reality.
Should I resend a campaign that appears stuck?
Wait for the incident to clear rather than resending. A stalled send is usually queued rather than lost, and firing it again is how subscribers end up with the same notification twice. If Messaging Delivery recovers and the campaign still shows nothing delivered after that, resending is a much safer call at that point.
Does a OneSignal outage affect push and email the same way?
Not necessarily. OneSignal groups Messaging Delivery as one component with several sub-components, so one channel can degrade while others keep running. Push also depends on Apple and Google gateways that OneSignal does not control, so push can fail while email and SMS go out normally, and that happens in reverse too.
The dashboard will not load. Are my notifications still sending?
Possibly, since Dashboard and UI is a separate component from APIs and SDK Endpoints. Sends triggered by your own backend through the API do not pass through the dashboard, so they can continue while the interface is unavailable. Check whether your send logs show successful API responses rather than judging from the dashboard alone.
Do I need to change anything in my app during an outage?
No. Leave the SDK and your integration alone, since a OneSignal incident is on their side and app-side changes take a release cycle to reach users anyway. If notifications carry time-sensitive alerts, having a fallback channel such as email or SMS ready in advance is the thing that helps, and it cannot be built mid-incident.

How we measure this

  • We request OneSignal's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where OneSignal publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when OneSignal goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required