Causaly Outage History

Causaly is up right now

Causaly had 8 outages in the last 2 years totaling 26m of downtime — averaging 0.3 incidents per month.

There were 8 Causaly outages since September 25, 2025 totaling 26m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.causaly.com

Minor July 27, 2026

Multi-hop unavailable

Detected by Pingoru
Jul 27, 2026, 01:04 PM UTC
Resolved
Jul 27, 2026, 01:04 PM UTC
Duration
—
Affected: Frontend ApplicationBackend Services
Timeline · 3 updates
  1. identified Jul 27, 2026, 12:08 PM UTC

    Status: Identified Multi-hop is currently unavailable. We have identified the root cause and are actively working on a fix to restore the service as quickly as possible. We apologize for the inconvenience and appreciate your patience. Affected components Frontend Application (Partial outage) Backend Services (Partial outage)

  2. monitoring Jul 27, 2026, 12:21 PM UTC

    Status: Monitoring A fix has been applied and Multi-hop is now available again. We are closely monitoring the service to ensure stability. Thank you for your patience while we resolved the issue. Affected components Frontend Application (Operational) Backend Services (Operational)

  3. resolved Jul 27, 2026, 01:04 PM UTC

    Status: Resolved The issue affecting Multi-hop has been resolved and the service is operating normally. We appreciate your patience while we investigated and resolved the issue. If you continue to experience any problems, please contact our support team. Affected components Frontend Application (Operational) Backend Services (Operational)

Read the full incident report →

Minor June 26, 2026

Issues with login

Detected by Pingoru
Jun 26, 2026, 07:31 AM UTC
Resolved
Jun 26, 2026, 07:31 AM UTC
Duration
—
Affected: Frontend Application
Timeline · 2 updates
  1. investigating Jun 26, 2026, 07:11 AM UTC

    Status: Investigating Causaly users are currently experiencing issues with authentication (log in). Our team is investigating the cause and working hard to restore normal performance levels. We apologize for any inconvenience. Affected components Frontend Application (Partial outage)

  2. resolved Jun 26, 2026, 07:31 AM UTC

    Status: Resolved The recent outage, caused by degraded service from our third party Identity Platform, has been resolved and Causaly services are fully restored. We appreciate your patience and apologize for any inconvenience. If you continue to experience any issues, please contact us at [email protected]. Affected components Frontend Application (Operational)

Read the full incident report →

Minor June 17, 2026

Complete outage

Detected by Pingoru
Jun 17, 2026, 01:29 PM UTC
Resolved
Jun 17, 2026, 01:29 PM UTC
Duration
—
Affected: Frontend ApplicationAuth0Backend Services
Timeline · 3 updates
  1. investigating Jun 16, 2026, 04:44 PM UTC

    Status: Investigating 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. Affected components Frontend Application (Full outage) Auth0 (Full outage) Backend Services (Full outage)

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

    Status: Monitoring 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]. Affected components Frontend Application (Operational) Auth0 (Operational) Backend Services (Operational)

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

    Status: Resolved 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. Affected components Frontend Application (Operational) Auth0 (Operational) Backend Services (Operational)

Read the full incident report →

Minor March 25, 2026

Degraded performance in Agentic Research chats

Detected by Pingoru
Mar 25, 2026, 07:15 PM UTC
Resolved
Mar 25, 2026, 07:15 PM UTC
Duration
—
Affected: Backend Services
Timeline · 2 updates
  1. investigating Mar 25, 2026, 07:01 PM UTC

    Status: Investigating Causaly is currently experiencing some degraded performance. Our team is currently working hard to restore normal performance levels. We apologize for any inconvenience. Affected components Backend Services (Degraded performance)

  2. resolved Mar 25, 2026, 07:15 PM UTC

    Status: Resolved The issue affecting performance in Agentic Research chats has now been fully resolved. All systems are operating normally again. Agentic Research is back to expected performance levels. We sincerely apologize for any disruption this may have caused and appreciate your patience while we worked to resolve the issue. Affected components Backend Services (Operational)

Read the full incident report →

Minor January 28, 2026

Multi-modal source files are not available

Detected by Pingoru
Jan 28, 2026, 11:59 AM UTC
Resolved
Jan 28, 2026, 11:59 AM UTC
Duration
—
Affected: Frontend ApplicationBackend Services
Timeline · 2 updates
  1. investigating Jan 28, 2026, 11:49 AM UTC

    Status: Investigating Causaly is currently experiencing some issues. Multi-modal source files are currently unavailable, potentially affecting some Discover summaries. Our team is currently working hard to restore normal performance levels. We apologize for any inconvenience. Affected components Frontend Application (Degraded performance) Backend Services (Degraded performance)

  2. resolved Jan 28, 2026, 11:59 AM UTC

    Status: Resolved The recent issue has been resolved and Causaly services are fully restored. We appreciate your patience and apologize for any inconvenience. If you continue to experience any issues, please contact us at [email protected]. Affected components Frontend Application (Operational) Backend Services (Operational)

Read the full incident report →