Rewindex

CompaniesOneSignalIncidents

OneSignal: Issue has been identified

Deleted by OneSignal. This incident disappeared from OneSignal’s status page on . Below is the last version Rewindex archived.
No impact listedStatus: resolvedStarted Resolved (1 min)3 updatesstatus.onesignal.com (opens in new tab)
Summary

OneSignal removed the resolved “Issue has been identified” incident record, which listed impact as “none,” started at 2026-07-20 17:56 UTC and resolved at 2026-07-20 17:57 UTC. Updates stated that a mitigation resolved the impact and all impacted systems returned to normal; affected systems and the root cause were not specified.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Timeline of updates

  1. identified

    We have identified the root cause and are working towards a resolution.

  2. monitoring

    We have applied a mitigation that resolves the impact.

  3. resolved

    The issue has been resolved. All impacted systems are now operating normally.

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Rewindex captured a newer version after the last checkpoint; the next run (00:41 UTC) commits it.

Impact, status and times are the vendor’s own, as last archived. View on status.onesignal.com (opens in new tab).

OneSignal profileRecent OneSignal incidentsMarkdownJSON