Investigating issues with Vibe app
This incident has been resolved.
The latest update from monday.com.
State
Resolved
Started
53 d ago
2026-09-09 18:21 UTC
Lasted
18 min
until 2026-09-09 18:39 UTC
Worst impact
Notice
Timeline
4 updatesInvestigating
12 min 64%
Identified
4 min 22%
Monitoring
3 min 14%
Updates
Times in UTCAs posted by monday.com
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are currently experiencing issues related to vibe applications. Our dedicated team is working to resolve this as quickly as possible
monday.com in the last 90 days
Full historyIncidents in 90 days
8
Days with an incident
6
Median duration
30 min
This incident
40% shorter than the median
Other monday.com incidents
All incidentsmonday.com·Delayed automations in EU
This incident has been resolved.
monday.com·Investigating issues with slow loading of the monday platform
This incident has been resolved.
monday.com·Identified issues with AI operations in the monday platform (Service Degradation for some models)
This incident has been resolved.
monday.com·Issues with automations and integrations
The issue with our automations, workflows, and integrations has been successfully resolved. Please refresh your browser to resume regular service usage. Thank you for your patience
monday.com·Partial UI functionality degradation
The issue affecting UI platform functionalities, including the Search functionality, has been successfully resolved. Please refresh your browser to resume regular service usage. Thank you for your patience
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.cc/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.cc/feed.xml?providers=monday/feed subscribe https://outages.cc/feed.xml?providers=mondayFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane