Intermittent System Availability

Final update

[monday.com](http://monday.com) · INCIDENT SUMMARY # **Degraded performance on November 4, 2026** **Customer impact:** 18:28 – 19:02 UTC \(34 minutes\) **Status:** Resolved ## **Summary** On November 4, 2026, between 18:28 and 19:02 UTC, customers in all regions experienced degraded performance while using [monday.com](http://monday.com). The exact impact window varied by region. The impact originated in one of our centralized edge networking components, which handles how requests reach our services. An unexpected change by one of our third-party technology providers affected this component. ## **Details** ### **1. Customer impact** The impact was global and affected multiple [monday.com](http://monday.com) services. Users may have experienced slow loading, intermittent errors, or actions that did not complete as expected. ### **2. Impact by region \(UTC\)** | Region | Impact window \(UTC\) | | --- | --- | | United States | 18:28 – 19:02 | | Europe | 18:28 – 18:57 | | Australia | 18:33 – 18:59 | | Israel | 18:35 – 18:57 | ### **3. Timeline \(UTC\)** | Time | Event | | --- | --- | | 18:28 | Degraded performance begins | | 18:30 | Detected by our monitoring; engineers engaged | | 18:

1. Postmortem · Nov 5, 08:04 UTC
   [monday.com](http://monday.com) · INCIDENT SUMMARY # **Degraded performance on November 4, 2026** **Customer impact:** 18:28 – 19:02 UTC \(34 minutes\) **Status:** Resolved ## **Summary** On November 4, 2026, between 18:28 and 19:02 UTC, customers in all regions experienced degraded performance while using [monday.com](http://monday.com). The exact impact window varied by region. The impact originated in one of our centralized edge networking components, which handles how requests reach our services. An unexpected change by one of our third-party technology providers affected this component. ## **Details** ### **1. Customer impact** The impact was global and affected multiple [monday.com](http://monday.com) services. Users may have experienced slow loading, intermittent errors, or actions that did not complete as expected. ### **2. Impact by region \(UTC\)** | Region | Impact window \(UTC\) | | --- | --- | | United States | 18:28 – 19:02 | | Europe | 18:28 – 18:57 | | Australia | 18:33 – 18:59 | | Israel | 18:35 – 18:57 | ### **3. Timeline \(UTC\)** | Time | Event | | --- | --- | | 18:28 | Degraded performance begins | | 18:30 | Detected by our monitoring; engineers engaged | | 18:50 | Root cause identified and fix rollout began | | 19:02 | Service fully restored in all regions | ### **4. Cause & resolution** An unexpected change by a third-party provider caused our centralized edge networking component to stop processing some requests normally. Our engineering team rolled ou
2. Resolved · Nov 4, 19:02 UTC
   This incident has been resolved. We experienced a service disruption caused by a third-party vendor that lasted approximately 30 minutes and has now been resolved. Our services are back to normal operation.
3. Investigating · Nov 4, 18:28 UTC
   We are currently investigating an issue where we are seeing intermittent failures with customer requests across the platform.