OneSignal logo

Is OneSignal Down?

CommunicationLive status, outages, and incident history

No. OneSignal is up right now.

Every monitored OneSignal system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment OneSignal breaks

OneSignal is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

Official OneSignal status page
How we know: the official OneSignal status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

OneSignal Component Status

The main OneSignal systems on this page. All 9 are operational right now.

9operational
Analytics & Reporting
Operational
APIs & SDK Endpoints
Operational
Dashboard / UI
Operational

6 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Email, In-App Messages, Integrations, Journeys, Push, SMS.

See all of them free

Component statuses may change independently during partial outages.

Recent OneSignal Outages & Incidents

Incident history from the official OneSignal status page, including resolution updates.

Subscription API - Creation FailuresResolved Sep 22, 2026 · 2 minResolved

The issue has been resolved. All impacted systems are now operating normally. --- [2026-09-22T21:30:23Z] (monitoring) We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. --- [2026-09-22T21:30:17Z] (investigating) **What’s happening:** Customers are unable to create new subscriptions **Who’s affected:** All customers trying to create new subscriptions **Current Status:** We are investigating the issue

Intermittent errors on /api/v1/notifications apiResolved Sep 18, 2026 · 34 minResolved

/api/v1/notifications create endpoint is now stable for all customers. The team has scaled up resources to handle increased load on our notifications service. --- [2026-09-18T01:13:34Z] (identified) A fix is rolling out now for the affected notifications services that are overloaded. Things should be stable within the next 10 minutes. --- [2026-09-18T00:50:16Z] (identified) We have identified the root cause and are working towards a resolution. Heavy load on one of our notification services is causing intermittent errors when trying to create a notification. Not all customers are affected. The team is working on adding more capacity to the affected service. We will provide another update in 15 minutes.

Apple push notifications failing in about 3% of casesResolved Aug 4, 2026 · 2h 4mResolved

The issue has been resolved. All impacted systems are now operating normally. --- [2026-08-04T18:46:33Z] (monitoring) We have applied a mitigation that should resolve the impact. We are monitoring to confirm effectiveness. We will provide another update in 20 minutes. --- [2026-08-04T18:45:08Z] (identified) We have identified the root cause and are working towards a resolution. There was a slight change in how Apple's push notification connections work. We will provide another update in 20 minutes. --- [2026-08-04T17:26:26Z] (investigating) **What’s happening:** Apple push notifications are failing in about 3% of cases. "Unknown delivery error" or "APNS failed to provide a response" error responses may be seen. **Who’s affected:** • Customers using Apple Push Notifications **Current Status:** We are investigating the issue and will provide an update in 20

OneSignal Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a OneSignal incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 1 day with incidentsSep 25

Live OneSignal Outage Reports

Problems reported by engineers using OneSignal. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No OneSignal problems reported yet.

Something wrong with OneSignal on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About OneSignal

OneSignal publishes a public status page at status.onesignal.com covering 9 components, including SMS, In-App Messages and Integrations. PulsAPI tracks OneSignal outages, degraded performance and incident history in real time, alongside the rest of your communications stack.

Over the past 30 days, PulsAPI has measured OneSignal uptime at 99.99%. Response times, incident history, and SLA tracking for OneSignal are available on the PulsAPI dashboard.

OneSignal Status FAQ

Is OneSignal down right now?

The verdict at the top of this page comes from the latest poll of the official OneSignal status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if OneSignal is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until OneSignal recovers.

How do I check OneSignal uptime history?

PulsAPI tracks OneSignal uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.99%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever OneSignal changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect OneSignal outages?

PulsAPI reads the official OneSignal status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual OneSignal components?

Yes. PulsAPI monitors 9 individual OneSignal components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when OneSignal goes down?

Yes. Create a free account and subscribe to OneSignal: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with OneSignal to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot OneSignal problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor OneSignal?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so OneSignal plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track OneSignal with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services