monday.com outage, July 2026: Issues with degraded platform performance

monday.com reported and resolved an incident: Issues with degraded platform performance. It lasted 1.8 hours.

Resolved

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

What happened

Started
Resolved
Duration
1.8 hours
Impact
major
Affected
Platform, Dashboards, Automations, Other Functionalities
  1. Investigating
  2. Identifiednot posted
  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:** Today, following a gradual rollout of a new feature, our platform experienced widespread cross-system performance degradation. While most features continued to work, a heavy load on our database impacted overall service availability, causing automations to run slowly and the automations store and agents to occasionally fail to load. **Please note that at no point was any data lost or compromised.** **Timeline:** * **US Region:** 15:30 – 17:10 UTC \(1 hour and 40 minutes of degradation\) ‌ **What caused it:** A new Dynamic Client Registration \(DCR\) feature for OAuth \(supporting MCP applications\) caused an unexpected chain reaction. Even with the limited rollout of this feature, frequent automated DCR requests triggered a continuous, global cache invalidation storm across our core caching infrastructure. With this shared cache repeatedly cleared, all traffic was directed straight to the database, causing a severe CPU spike. ‌ **How we responded:** Our engineering team identified the source and immediately performed a significant system scale-up to handle the extreme load. We then disabled the DCR endpoint in production. This stopped the cache invalidation loop, restoring database stability and returning system performance to normal. **What we're doing to prevent recurrence:** Moving forward, we plan to use a setup that will take the load off core caching systems. Because this was a limited gradual rollout, turning it off has zero impact on your current wo

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 experiencing issues related to platform latency/slowness. Our dedicated team is working to resolve this as quickly as possible

  2. investigating

    We are continuing investigating the issues related to platform latency/slowness. This also might affect automations not triggering/loading. Thanks for your patience and understanding.

  3. investigating

    We are continuing investigating the issues related to platform not loading/working. This is also affecting automations, boards, board views, dashboards, AI features, my work, item creation, workspaces.

  4. monitoring

    A fix has been implemented and we are monitoring the results.

  5. resolved

    This incident has been resolved.

  6. postmortem

    **What Happened:** Today, following a gradual rollout of a new feature, our platform experienced widespread cross-system performance degradation. While most features continued to work, a heavy load on our database impacted overall service availability, causing automations to run slowly and the automations store and agents to occasionally fail to load. **Please note that at no point was any data lost or compromised.** **Timeline:** * **US Region:** 15:30 – 17:10 UTC \(1 hour and 40 minutes of degradation\) ‌ **What caused it:** A new Dynamic Client Registration \(DCR\) feature for OAuth \(supporting MCP applications\) caused an unexpected chain reaction. Even with the limited rollout of this feature, frequent automated DCR requests triggered a continuous, global cache invalidation storm across our core caching infrastructure. With this shared cache repeatedly cleared, all traffic was directed straight to the database, causing a severe CPU spike. ‌ **How we responded:** Our engineering team identified the source and immediately performed a significant system scale-up to handle the extreme load. We then disabled the DCR endpoint in production. This stopped the cache invalidation loop, restoring database stability and returning system performance to normal. **What we're doing to prevent recurrence:** Moving forward, we plan to use a setup that will take the load off core caching systems. Because this was a limited gradual rollout, turning it off has zero impact on your current wo

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

  • Retry anything that failed during the 1.8 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