Investigating connectivity issues across accounts and devices

Update timeline

1. investigating Jun 12, 2025, 12:31 PM UTC

   We are currently investigating reports of connectivity issues across the platform. Our team is working to resolve this promptly.

2. identified Jun 12, 2025, 01:20 PM UTC

   Our team has identified the root cause of the issue and is working to resume regular service usage. We will continue to provide updates on their progress

3. identified Jun 12, 2025, 01:28 PM UTC

   The platform should be working mostly as expected. Our team is still working on issues with automations and notifications

4. identified Jun 12, 2025, 01:47 PM UTC

   Automations, API, and notifications are still not working as expected. We're working to resolve the issues and will continue to provide updates on our progress

5. identified Jun 12, 2025, 02:07 PM UTC

   API should be working as expected now. We are continuing to work on a fix for the issues with automations, integrations, and notifications

6. identified Jun 12, 2025, 02:38 PM UTC

   Automations and integrations are up but may be delayed. We're still working to solve the issue with notifications. We appreciate your patience

7. identified Jun 12, 2025, 02:52 PM UTC

   Notifications should be working as expected now. Automations and integrations may still be delayed. We are continuing to work to fully resolve the issue

8. monitoring Jun 12, 2025, 02:55 PM UTC

   A fix has been implemented, and we are monitoring results to restore full system stability

9. resolved Jun 12, 2025, 03:09 PM UTC

   The platform is now back to regular service. Please refresh your browser to access the platform. Thank you for your patience

10. postmortem Jun 17, 2025, 06:00 PM UTC

    **What Happened:** On June 12th \(8:26 EST AM\), we experienced a service disruption in our EU region that resulted in 68 minutes of degraded performance and 20 minutes of full downtime for several features, including API access, automations, notifications, and communications. ‌ **What caused it:** A backend infrastructure issue caused unexpected pressure on our caching systems, leading to widespread delays and partial outages across key services. ‌ **How we responded:** Our engineering teams quickly identified the root cause, rolled back the triggering changes, and scaled our systems to restore stability. Full functionality was gradually restored within a few hours. ‌ **What we're doing to prevent recurrence:** We’re implementing additional safeguards to detect anomalies earlier, improving system scalability, and strengthening internal processes to prevent similar incidents in the future ‌ **No data loss occurred** during this incident. ‌ We sincerely apologize for any disruption this caused to your workflow. Thank you for your understanding as we work to continuously improve our platform's reliability. Your team at [monday.com](http://monday.com)