Todyl Outage History

Todyl experienced delays in case creation processing for 36 minutes. The incident affected the timely generation of new cases within the system. The issue was identified and fixed, with all delayed cases being fully processed and reviewed.

Todyl's SIEM portal experienced degraded search performance for 23.8 hours, causing a subset of users to encounter slow or delayed search results. Log ingestion and alerting functions remained fully operational throughout the incident. The engineering team identified the root cause, implemented a fix, and monitored the environment until search performance was fully restored.

Todyl experienced elevated device reconnection rates on a subset of SASE nodes, causing intermittent connection instability and degraded performance for users on the Secure Global Network. The issue was resolved after 2 hours with a fix implementation and monitoring period.

Todyl's Secure Global Network experienced SASE reconnections and connection delays for 31 minutes. The issue was identified and a fix was implemented, with monitoring confirming resolution. The incident affected network connectivity stability for users accessing the SASE service.

Todyl experienced elevated errors on their Secure Global Network (SGN) that impacted device connections and prevented new device registrations for 3.6 hours. The incident was caused by replication delays affecting policy change propagation, though SASE connectivity remained unaffected throughout the outage. A fix was deployed to address the replication issues, restoring normal portal functions and allowing new device registrations to resume.

Todyl experienced a major incident where SASE Static IP policies were not applying correctly to certain network traffic, affecting their Secure Global Network. The routing issue was investigated and resolved within 8 minutes.

Todyl experienced intermittent connectivity issues at their Washington D.C. (IAD) Point of Presence on the Secure Global Network, affecting a subset of users with degraded or interrupted connectivity, including disruptions to tunnel connections and static IP assignments. The engineering team identified the root cause and implemented a fix after 3.2 hours, with devices expected to reconnect automatically as the network returned to normal operation.