Skip to content
PulseWatchOUTAGE.INTEL
OneSignal logo

Communication

Is OneSignal down right now?

NormalOfficial status last polled Oct 12, 2026 20:23 UTConesignal.comOfficial status page

Are you on the OneSignal team and see something inaccurate? Report it to us. We respond within one business day.

Is OneSignal down right now?

No. OneSignal has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Oct 12, 2026 21:40 UTC

Normal

OneSignal is operating normally

As of Oct 12, 2026 21:40 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

0

Last incident

Sep 18, 2026 02:59 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unavailable

Current measurements are not available for a health score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for OneSignal.

1

Incident days

29

No recorded incident

2h 10m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical
Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.
Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for OneSignal. Hover a day for detail.

Sep 13Sep 18Sep 23Sep 28Oct 3Oct 801234

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

1

Days with incidents

1 incident

Busiest day

2h 10m

Recorded duration

Report volume

0 reports in last 24H

09:30 PM01:00 AM04:30 AM08:00 AM11:30 AM03:00 PM06:30 PM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

OneSignal outage on September 18 — 2h 9m disruption

Sep 18, 12:49 AM → Sep 18, 02:59 AM · 2h 9m · high

OneSignal experienced a high-severity service disruption. This incident was detected via the vendor's status page and automated signals. The disruption lasted for 2 hours and 9 minutes, from 2026-09-18T00:49:24.682Z until it was resolved at 2026-09-18T02:59:18.298Z.

Duration
2h 9m
tracked by PulseWatch

Impact

During the 2-hour and 9-minute high-severity disruption, the OneSignal service experienced an outage. This incident was identified through automated monitoring and the vendor's own status page. No user-reported data was collected for this incident, and therefore no specific user-reported issue types or affected regions were recorded.

Incident timeline

  1. Sep 18, 12:49 AM

    PulseWatch detected the incident from automated vendor and probe signals (high severity)

  2. Sep 18, 12:49 AM

    Status updated: possible issue

  3. Sep 18, 02:59 AM

    Signals cleared — incident resolved

Official updates

  1. Sep 18, 12:49 AM

    OneSignal status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the sources listed above.

Reliability

Detected by PulseWatch

30-day uptime

99.70%

90-day uptime

99.90%

Calculated from OneSignal's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other communication services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedHigh

OneSignal: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch OneSignal or have an alert rule on it can be alerted, labelled vendor-reported.

9/18/2026, 12:49:24 AM · 2h 9m

12:49 AM02:59 AM
Detection9/18/2026, 12:49:24 AM · 24d ago

Detected — high severity

OneSignal: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch OneSignal or have an alert rule on it can be alerted, labelled vendor-reported.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment OneSignal enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Normal
Monitoring
Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

onesignal.com