CHYP.ai · ORBIT // Cloudy_Day Security Suite

APIs: messaging, media, analytics

Operational OneSignal status

onesignal.com · Official status page (Statuspage-compatible JSON)

FROM ALL SOURCES

No sign of a widespread OneSignal problem right now; every source we read is quiet.

confidence: medium Vendor: operational · users: normal · routing: no data.

Vendor status vs. reality: Vendor status and outside signals roughly agree
The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started64 days
Crowd clock when user reports began rising above normalnot seenn/a
Network clock when routing anomaly data first flagged itnot seenn/a
ORBIT clock when our checker first recorded the changenot seenn/a

Evidence

  • Official page: Operational (“All Systems Operational”). evidence confidence: high
  • Vendor stage: resolved on “Intermittent errors on /api/v1/notifications api”. evidence confidence: high
  • User reports are within normal range (0 in 15 min). evidence confidence: low

What we don't know: what is happening inside OneSignal's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .

Cloudy_Day's take

Stage vs. health

The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.

Who depends on whom

We don't map other services that depend on OneSignal. Dependency chains are where single points of failure hide.

Identity & trust lens

Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.

For users

Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.

For security teams

Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on OneSignal, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).

What to watch next

Any new vendor incident, a jump in user reports above baseline, or trouble at the providers OneSignal may depend on.

Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with OneSignal. No blame or attack claims without an official source. Generated .

INCIDENT REPLAY

Intermittent errors on /api/v1/notifications api

major resolved · started · resolved

3 updates

  1. 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.

  2. identified

    A fix is rolling out now for the affected notifications services that are overloaded. Things should be stable within the next 10 minutes.

  3. resolved

    /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.

Official incident page ↗

Community comments (0)

Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.

No approved comments yet.

How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.

Where to next