Partially Degraded Service
monday.com reports degraded service for Integrations and Automations. The provider is investigating the issue.
State
Components degraded
Started
Ongoing for
1 h 1 min
Worst impact
Degraded
Timeline
1 updateComponents degraded
1 h 1 min 100%
Updates
Times in UTCAs posted by monday.com
Affected components
4monday.com in the last 90 days
Full historyIncidents in 90 days
15
Days with an incident
11
Median duration
40 min
This incident
1.5× the median
Other monday.com incidents
All incidents
monday.com·Investigating issues with automations involving Outlook
monday.com automations that use Outlook do not work. The problem affects Automations and Integrations in the US, EU, and AUS regions. monday.com identified the cause and reported that it waited on a Microsoft outage. monday.com resolved the incident after about 12 hours and 43 minutes.
monday.com·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.
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.
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