Partially Degraded Service
The Search component on monday.com does not work correctly. monday.com reports that the incident is resolved. The incident lasted 3 minutes.
State
Resolved
Started
Lasted
3 min
Worst impact
Degraded
Timeline
2 updatesComponents degraded
3 min 100%
Updates
Times in UTCAs posted by monday.com
Affected components
1monday.com in the last 90 days
Full historyIncidents in 90 days
13
Days with an incident
9
Median duration
32 min
This incident
91% shorter than the median
Other monday.com incidents
All incidents
monday.com·Degraded Performance - Inbox Loading Delays
The inbox tool on monday.com had slow loading. The Communication component and the US Communication region had degraded performance. monday.com reports that the incident is resolved. It lasted about 16 hours and 47 minutes.
monday.com·Investigating issues with My Work and Dashboards not loading
monday.com reported that My Work and Dashboards did not load for some users. The affected components were Platform, Dashboards, US - Dashboards, EU - Platform, and AUS - Platform. monday.com resolved the incident, which lasted 99 minutes.
monday.com·Minor Service Outage
monday.com reports a minor service outage that affects Datadog US1 APM. The issue is resolved. The outage lasted 12 minutes.
monday.com·Service disruption on US server
monday.com reports a service disruption on the US server. The problem affected the Platform, Dashboards, and Automations components in the US region. The outage is resolved and lasted about 134 minutes. Monday.com states that the platform is back to regular service and asks users to refresh the browser.
monday.com·Intermittent System Availability
monday.com reports intermittent failures with customer requests on the Platform. The affected regions are the US, the EU, Australia, and Israel. monday.com reports that the incident is resolved. The incident lasted 22 minutes.
Follow monday.com
Your coding agent knows when monday.com is down, and tells you when a failure is theirs, not yours. You can also get monday.com incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "monday" and tell me if monday.com has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=monday/feed subscribe https://outages.live/feed.xml?providers=mondayFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane