# OneSignal: Issue has been identified

**Deleted by the vendor** (gone from the status page since 2026-10-19 00:03 UTC). The content below is the last version Rewindex archived.

- Impact (vendor’s label): none
- Status: resolved
- Started: 2026-07-20 17:56 UTC · Resolved: 2026-07-20 17:57 UTC · Duration: 1 min
- Updates: 3
- [Vendor status page: https://status.onesignal.com/incidents/01KY0AQZPATK88T1YG8V1VPRHC](https://status.onesignal.com/incidents/01KY0AQZPATK88T1YG8V1VPRHC)
- [Company: OneSignal](https://rewindex.com/company/onesignal.md)

## 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, sol)_
## Timeline of updates

- **identified** 2026-07-20 17:56 UTC: We have identified the root cause and are working towards a resolution.
- **monitoring** 2026-07-20 17:56 UTC: We have applied a mitigation that resolves the impact.
- **resolved** 2026-07-20 17:57 UTC: The issue has been resolved. All impacted systems are now operating normally.

## Rewindex changes for this incident

- 2026-10-19 00:03 UTC: [Incident deleted: Issue has been identified](https://rewindex.com/change/df5ba89ee28bf43.md)


---
Canonical: https://rewindex.com/company/onesignal/incidents/01KY0AQZPATK88T1YG8V1VPRHC · Markdown: https://rewindex.com/company/onesignal/incidents/01KY0AQZPATK88T1YG8V1VPRHC.md · JSON: https://rewindex.com/api/v1/companies/onesignal/incidents/01KY0AQZPATK88T1YG8V1VPRHC · Generated 2026-10-20T00:29:04.403Z