Struck in red is what Monday.com removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
ChangedStatus#1
Before: resolved
After: postmortem
AddedUpdatepostmortem#2
Before: not present
After: 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. 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 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 out a fix and verified that all services returned to full performance.
5. Data & security
This was an operational issue, not a security incident. Customer data was not lost, exposed, or corrupted, and no action is required from customers.
Next steps
Our monitoring systems worked as expected and alerted our engineering team as soon as the issue began. The affected component has been fully remediated, and we are following up with the vendor to understand the change on their side and prevent a recurrence. We sincerely apologize for the disruption.
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.