ChangesOneSignalIssue has been identified
OneSignal: Incident deleted: Issue has been identified
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 diff below (Sol; type: incident edit). Check the diff before relying on it.
Incident page: the full timeline of updates
What changed
Struck in red is what OneSignal removed; blue is what they added. Muted text is unchanged context.
Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).
History of this incident
TodayMonday, October 19Mon, Oct 19
1 rewrite
- Deleted by OneSignalDeleted by the vendor
Issue has been identifiedthis changeOneSignal 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.