All Systems Operational

Dashboard and API ? Operational
90 days ago
99.92 % uptime
Today
Offline Job Processing ? Operational
90 days ago
100.0 % uptime
Today
Delivery ? Operational
90 days ago
99.99 % uptime
Today
Analytics & Update Processing ? Operational
90 days ago
100.0 % uptime
Today
CMS (onesignal.com landing page) ? Operational
90 days ago
100.0 % uptime
Today
Newsroom ? Operational
Documentation Operational
OneSignal Email Outbound Processing Operational
90 days ago
99.92 % uptime
Today
OneSignal Email Outbound Delivery Operational
90 days ago
99.99 % uptime
Today
OneSignal Email Events & Logs Operational
90 days ago
100.0 % uptime
Today
Cloudflare Infrastructure Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

Scheduled Maintenance

StatusPage Migration to Incident.io Apr 15, 2025 13:00-13:30 UTC

We’re reaching out to inform you about important upcoming changes to OneSignal’s StatusPage, status.onesignal.com.

What’s changing?

On 15/04/2025 13:00 UTC, we will migrate our status page from Jira StatusPage to Incident.io StatusPage. This migration is part of our ongoing efforts to enhance monitoring, observability, and platform reliability.
With Incident.io, we’re integrating our incident response, on-call management, and post-incident reviews into a single platform, ensuring a smoother incident response process and the best support for our customers during incidents.


What you need to know

During this migration, the following changes will take effect:

- Our status page URL remains the same. You can still access it at https://status.onesignal.com.
- Email subscribers will be automatically migrated to our new Incident.io StatusPage. No action needed.
- A new RSS subscription option will be available to our subscribers.
- Slack subscriptions will need to be resubscribed after the migration to receive updates in the future.
- SMS and webhook subscription options will no longer be available.
- We will discontinue X (Twitter) updates from our @OneSignalStatus account.


What you need to do

- If you are subscribed to updates with the Email option:
- you will be automatically migrated. No further action is required.

- If you are subscribed to updates via Slack:
- Wait until the migration is complete, after 15/04/2025 13:00 UTC.
- Check the status page for “Powered by Incident.io” at the bottom to confirm the migration is complete.
- Resubscribe our status page to your Slack workspace to ensure you receive future updates.

- If you are subscribed to updates via SMS or Webhook, or X (Twitter):
- Wait until the migration is complete, after 15/04/2025 13:00 UTC.
- Check the status page for “Powered by Incident.io” at the bottom to confirm the migration is complete.
- Choose an alternative subscription option: Email, Slack, or RSS feed.


We’re here to help

We understand this change may require adjustments, and we’re here to help. If you need assistance or have any questions, please contact support at support@onesignal.com.

Thanks for choosing OneSignal!

Posted on Apr 01, 2025 - 08:48 UTC
Apr 2, 2025

No incidents reported today.

Apr 1, 2025
Resolved - This incident has been resolved.
Apr 1, 16:10 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 1, 15:58 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 1, 15:51 UTC
Investigating - We are currently investigating an issue that impacts scheduled messages and retries. This is not impacting new messages.
Apr 1, 15:45 UTC
Mar 31, 2025

No incidents reported.

Mar 30, 2025

No incidents reported.

Mar 29, 2025

No incidents reported.

Mar 28, 2025

No incidents reported.

Mar 27, 2025

No incidents reported.

Mar 26, 2025
Resolved - This incident has been resolved.
Mar 26, 19:15 UTC
Identified - A dependency upgrade deployed during 14:54 UTC to 18:36 UTC triggered a small number of notifications to fail to send.
Mar 26, 19:13 UTC
Investigating - We are currently investigating this issue.
Mar 26, 18:47 UTC
Mar 25, 2025
Resolved - The change has been reverted.
Mar 25, 19:43 UTC
Identified - A bad deployment of our frontend has caused some dashboard downtime. We are reverting the change.
Mar 25, 19:42 UTC
Mar 24, 2025

No incidents reported.

Mar 23, 2025

No incidents reported.

Mar 22, 2025

No incidents reported.

Mar 21, 2025
Resolved - We lost around 10 deliveries around 08:10 UTC. We are communicating with affected customers directly.
A large number of other deliveries had extended retries around that time which caused greater than usual latency.

Mar 21, 08:00 UTC
Mar 20, 2025

No incidents reported.

Mar 19, 2025

No incidents reported.