Critical incident
Todyl: Case creation
Apr 28, 2026, 13:29 UTC
started
15:16 UTC
resolved
1 h 46 min
duration
Affected: SIEM Processing & Alerting
Current status of Todyl: Operational — live Todyl status
Timeline
- Apr 28, 2026, 13:29 UTCinvestigatingWe identified and resolved an issue that caused delays in case creation and scheduled reporting. No alerts were lost, and MXDR is actively reviewing and addressing all open cases. We are maintaining heightened monitoring until all delayed cases have been fully processed, reviewed, and addressed, and all scheduled reports have been delivered.
- Apr 28, 2026, 13:33 UTCinvestigatingWe are continuing to investigate this issue.
- Apr 28, 2026, 13:46 UTCinvestigatingWe are continuing to investigate this issue.
- Apr 28, 2026, 15:16 UTCresolvedDelays in case Creation and reporting issue is resolved. System and MXDR team is fully up to speed in reviewing the delayed cases. We are continuing to monitor but we consider the issue resolved.
Updates as published by Todyl (original).
Other services with incidents at the same time
- University of Warwick 14:29 UTC · Exam timetable errors
- ngrok 14:29 UTC · Users who install ngrok via the Microsoft Store encounter a fatal panic immediately on starting an endpoint.
- Duo 14:22 UTC · Elevated Authentication Latency in DUO6
- Simply 13:24 UTC · INCIDENT
- Infura 12:59 UTC · Developer dashboard outage
- Devin 12:55 UTC · Sessions queuing
- Devin 12:44 UTC · Devins slow to start
More Todyl incidents
- October 5, 2026 SASE Connectivity impacting subset of Windows Server 2016/2019