# Intermittent System Availability

- Provider: [monday.com](https://down.guide/monday)
- Level: confirmed
- Impact: Partial outage
- lasted 34m
- started 2026-11-04 18:28 UTC
- Platform, Platform, Platform +1
- au, eu, us
- id: DWN-dc77d94f6b
- Official page: https://stspg.io/0v4hrfn3yms8

## Root cause
> We experienced a service disruption caused by a third-party vendor that lasted approximately 30 minutes and has now been resolved.

Category: Upstream dependency. [Postmortem](https://stspg.io/0v4hrfn3yms8)

## Updates from monday.com
### 2026-11-04 18:28 UTC: investigating
We are currently investigating an issue where we are seeing intermittent failures with customer requests across the platform.

### 2026-11-04 19:02 UTC: resolved
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.

### 2026-11-05 08:04 UTC: postmortem
\[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 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.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).