Causaly incident

Complete outage

Resolved after 20 hours 45 minutes, affecting Frontend Application and Auth0 and 1 more, on June 16, 2026.

resolved Jun 17, 2026, 01:29 PM UTC

Causaly service has been successfully restored. No further issues have been detected during our post-fix monitoring period. Summary of impact: • 15:50–16:45 UTC, 16 June — the platform was intermittently unavailable. Users were unable to log in, or were logged out and redirected to the login page. • 16:45–22:00 UTC — the platform was entirely unavailable and users were unable to log in. • 15:30–22:00 UTC — chats and searches made by users who reached the platform during this window were not stored (storage was affected slightly before the login problems became visible) We understand how disruptive this was, and we sincerely apologise. We're conducting a thorough review of both the incident and our response, to improve our resilience based on the lessons learned.

Started
Jun 16, 2026, 04:44 PM UTC
Resolved
Jun 17, 2026, 01:29 PM UTC
Duration
20h 45m
Detected by Pingoru
Jun 16, 2026, 04:44 PM UTC

Affected components

Frontend ApplicationAuth0Backend Services

Update timeline

  1. investigating Jun 16, 2026, 04:44 PM UTC

    Causaly is currently experiencing a complete outage. Our team is investigating the cause and working hard to restore normal performance levels. We apologize for any inconvenience.

  2. monitoring Jun 16, 2026, 10:01 PM UTC

    The recent outage has been resolved, and Causaly services have been fully restored. We are continuing to monitor performance and functionality closely. Thank you for your patience, and we apologize for the inconvenience caused. If you continue to experience any issues, please contact us at [email protected].

  3. resolved Jun 17, 2026, 01:29 PM UTC

    Causaly service has been successfully restored. No further issues have been detected during our post-fix monitoring period. Summary of impact: • 15:50–16:45 UTC, 16 June — the platform was intermittently unavailable. Users were unable to log in, or were logged out and redirected to the login page. • 16:45–22:00 UTC — the platform was entirely unavailable and users were unable to log in. • 15:30–22:00 UTC — chats and searches made by users who reached the platform during this window were not stored (storage was affected slightly before the login problems became visible) We understand how disruptive this was, and we sincerely apologise. We're conducting a thorough review of both the incident and our response, to improve our resilience based on the lessons learned.

Your product runs on more than Causaly

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →