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 November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · every 60s

Know the moment OneSignal breaks

OneSignal is healthy right now. We keep checking (every 60 seconds) and email you when 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), and outage reports from engineers. How PulsAPI monitoring works

Status report

OneSignal Status Summary

As of 13:06 UTC on 9 November 2026, OneSignal is operational. PulsAPI checked OneSignal's official status page and found 9 of 9 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for OneSignal, counting degraded performance as up. The latest incident, "Intermittent incomplete data in the dashboard and API reads for a subset of apps (starting with app id with 0)", was on Oct 14, 2026 and lasted 24h 20m.

Cite as: PulsAPI, “OneSignal status”, checked 9 November 2026, 13:06 UTC. https://www.pulsapi.com/services/onesignal

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.

Intermittent incomplete data in the dashboard and API reads for a subset of apps (starting with app id with 0)Resolved Oct 14, 2026 · 24h 20mResolved

Between 14:31 UTC on Oct 14 and 14:51 UTC on Oct 15, 2026, a subset of apps (apps whose app ID starts with 0) may have intermittently seen incomplete or inconsistent results. The issue affected read requests only. No data was lost, and our primary systems never had incomplete data. It came from a read-only database used for a limited share of read traffic, which we removed from service at 14:51 UTC on Oct 15. Results have been consistent since then. We are adding automated checks to prevent this from happening again. If you saw unexpected results during this window and need help, please contact support. --- [2026-10-20T20:53:15Z] (identified) We've identified an issue for a subset of apps (app IDs starting with 0).

Database incident - impacting app IDs starting with eResolved Sep 30, 2026 · 24 minResolved

We experienced a database issue that affected our customers. It only impacted apps which IDs start with e. The team has resolved the incident, and traffic is back to normal. --- [2026-09-30T09:22:42Z] (monitoring) We've identified the problem and applied a fix. Traffic is being restored. --- [2026-09-30T09:22:42Z] (investigating) We're investigating the incident

Subscription API - Creation FailuresResolved Sep 22, 2026 · 25 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

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 history91 days observed
Aug 11100.00% average · 1 day with incidentsNov 9

Going further back: OneSignal uptime by month and every recorded OneSignal outage.

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 100.00%. 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 it every 60 seconds.

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 100.00%. 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 it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

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

2660+ 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