Intermittent errors on /api/v1/notifications api

What to do

• Check whether your product depends on OneSignal. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 34m it lasted.

  Anything that failed between 2026-09-18 00:48 UTC and 2026-09-18 01:23 UTC may need a replay.

• Subscribe to OneSignal's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=onesignal works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from OneSignal 3

1. identifiedSep 18, 2026, 12:48 AM UTC

   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.

   provider

2. identifiedSep 18, 2026, 1:13 AM UTC

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

   provider

3. resolvedSep 18, 2026, 1:23 AM UTC

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

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.