monday.com outage, October 2025: Investigating connectivity issues across accounts and devices due to an AWS outage

monday.com reported and resolved an incident: Investigating connectivity issues across accounts and devices due to an AWS outage. It lasted 14.1 hours.

Resolved

From monday.com's official status page, in their words.

What happened

Started
Resolved
Duration
14.1 hours
Impact
critical
Affected
Platform, Platform
  1. Investigating
  2. Identified
  3. Monitoring
  4. Resolved

Why it happened

monday.com has not given a cause in its updates. We never guess one.

How it was resolved

**What Happened:** On October 20th, starting around 03:00 AM EST, our US server customers experienced approximately 250 minutes of disruption, including about 165 minutes of full system downtime followed by 522 minutes of degraded performance that affected automations and integrations. The issue was caused by an outage of our third-party provider, AWS, which primarily impacted the US region, but also created downstream effects globally. As a result, some customers in our EU and AU regions experienced related degraded performance issues with API, automations, and integrations, lasting up to 150 minutes. ‌ **What caused it:** This incident was caused by a major outage at our third-party provider, AWS \(Amazon Web Services\), in one of their U.S. data center regions. This outage led to widespread disruptions across many platforms, including [monday.com](http://monday.com). This issue began with errors and delays within AWS’s core systems, which affected how our servers handled data and automations. As AWS implemented mitigation efforts to restore functionality, our team actively worked to maintain stability and recovery as services gradually returned to normal. ‌ **How we responded:** Our engineering and developers teams acted immediately to stabilize the platform once the issue was detected. To protect performance and further disruption, we temporarily paused automations and API activity connected to the affected region while we worked on restoring service. We kept customers in

monday.com's closing update

This incident on the monday.com status page

Timeline

Oldest first, from the first notice to the resolution. From monday.com's official status page, in their words.

  1. investigating

    We are currently investigating reports of connectivity issues across the platform, which are caused by an AWS outage per https://health.aws.amazon.com/health/status. Our team is working to resolve this promptly.

  2. investigating

    We are continuing to investigate this issue.

  3. investigating

    Our API is also experiencing connectivity issues in our EU and AU servers. We're working to investigate the issue.

  4. identified

    Our team has identified that the root cause of the issue is with our third party, and they are working to resume regular service usage. Additionally, API is partially working in the EU and AU servers. We will continue to provide updates on their progress

  5. identified

    Our automations and integrations are also experiencing issues in the EU and AU servers. We are working to fix the issue.

  6. identified

    We are continuing to work on a fix for this issue.

  7. identified

    Automations and integrations working again in the EU server, but may experience delays

  8. identified

    Automations and integrations working again in the AU server, but may experience delays

  9. identified

    The platform is starting to recover, we will update again soon.

  10. monitoring

    The EU and AU servers are fully functional, and the platform is partly functional in the US server. We're working to fully resolve the issue as soon as possible

  11. monitoring

    We're still working to fully resolve the issue as soon as possible!

  12. monitoring

    Automations and integrations are experiencing degraded performance on the US server. We will continue to provide updates until the issue is fully resolved!

  13. monitoring

    Automations are experiencing degraded performance on the US server. We're working to fully resolve the issue as soon as possible!

  14. monitoring

    We are still monitoring the incident.

  15. monitoring

    We are currently experiencing issues connecting customers with our Customer Support Team. We are continuing to monitor for any platform-related issues.

  16. monitoring

    Automations are experiencing degraded performance on the US server. We will continue to provide updates until the issue is fully resolved!

  17. monitoring

    Automations are experiencing degraded performance on the US server. We are still experiencing issues connecting customers with our Customer Support Team. We will continue to provide updates until the issue is fully resolved!

  18. monitoring

    We are monitoring results to restore full system stability on the platform, including automations on the US server and issues connecting customers with our Customer Support Team. We will continue to provide updates until the issue is fully resolved!

  19. monitoring

    A fix has been implemented, all system is working and being monitored beside automations in US which are still being affected.

  20. monitoring

    All system is working and being monitored beside automations and API in US which are still being affected.

  21. monitoring

    All platform components availability and latency have returned to normal. We are no longer observing issues coming from AWS infrastructure. Our teams will continue to monitor platform availability; Automations is back to work but we do expect delays in automation completion.

  22. monitoring

    We are continuing to monitor for any further issues.

  23. resolved

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

  24. postmortem

    **What Happened:** On October 20th, starting around 03:00 AM EST, our US server customers experienced approximately 250 minutes of disruption, including about 165 minutes of full system downtime followed by 522 minutes of degraded performance that affected automations and integrations. The issue was caused by an outage of our third-party provider, AWS, which primarily impacted the US region, but also created downstream effects globally. As a result, some customers in our EU and AU regions experienced related degraded performance issues with API, automations, and integrations, lasting up to 150 minutes. ‌ **What caused it:** This incident was caused by a major outage at our third-party provider, AWS \(Amazon Web Services\), in one of their U.S. data center regions. This outage led to widespread disruptions across many platforms, including [monday.com](http://monday.com). This issue began with errors and delays within AWS’s core systems, which affected how our servers handled data and automations. As AWS implemented mitigation efforts to restore functionality, our team actively worked to maintain stability and recovery as services gradually returned to normal. ‌ **How we responded:** Our engineering and developers teams acted immediately to stabilize the platform once the issue was detected. To protect performance and further disruption, we temporarily paused automations and API activity connected to the affected region while we worked on restoring service. We kept customers in

What this means for a business (and what to check now)

  • Retry anything that failed during the 14.1 hours.
  • Enter any payments, bookings or jobs you took another way.
  • If a deadline fell inside the window, keep this page as your record of the outage.

The full guide: what to do when a service you rely on is down

Other monday.com incidents

Hear about the next monday.com incident as it starts

Free email alerts when the official status changes, with what to do while it is down.

Watch monday.com