Agent and Workspace Issues
Replit reports a partial outage. Agent and Workspace functions do not fully work. Replit put a fix in place and monitors the result. Replit states that agent interactions should work again after a browser tab update. The issue started 273 minutes ago.
State
Monitoring
Started
10 h ago
2026-11-01 15:42 UTC
Ongoing for
10 h 13 min
Worst impact
Partial outage
Timeline
1 updateMonitoring
10 h 13 min 100%
Updates
Times in UTCAs posted by Replit
For those seeing Agent failures can you please update the browser tab, we expect agent interactions to be working again.
Replit in the last 90 days
Full historyIncidents in 90 days
34
Days with an incident
46
Median duration
2 h 3 min
This incident
5.0× the median
Other Replit incidents
All incidentsReplit·Investigating an issue related to the agent's ability to process images
We have resolved some of the earlier issues where connections to replit was disrupted.
Replit·Investigating issues related to platform access
Access to Replit services has recovered.
Replit·Users can't access privately deployed apps
Users are able to access their private apps again.
Replit·Hubspot Connectors is not working
HubSpot connectors that use Replit’s default configuration are not working. We’ve identified the root cause and are currently working on a fix.
Replit·Users unable to top-up
Users are able to top up again.
Follow Replit
Your coding agent knows when Replit is down, and tells you when a failure is theirs, not yours. You can also get Replit 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 "replit" and tell me if Replit 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=replit/feed subscribe https://outages.live/feed.xml?providers=replitFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane