Connector status mismatch and removal errors
The issue affecting existing connector connections has been resolved. Previously connected integrations should now appear again without reconnecting. If a connection still appears unavailable or you see a setup or removal error, please contact support with the affected connector and project so we can investigate.
The latest update from Replit.
State
Resolved
Started
40 d ago
2026-09-22 21:36 UTC
Lasted
2 h 6 min
until 2026-09-22 23:42 UTC
Worst impact
Degraded
Timeline
3 updatesInvestigating
2 h 6 min 100%
Updates
Times in UTCAs posted by Replit
The issue affecting existing connector connections has been resolved. Previously connected integrations should now appear again without reconnecting. If a connection still appears unavailable or you see a setup or removal error, please contact support with the affected connector and project so we can investigate.
We're aware of an issue where some connectors display as "healthy" in the a project while the underlying agent reports them as "not set up." Attempting to remove an affected connection currently returns a 401 error. We're investigating and will post updates here.
We're aware of an issue where some connectors display as "healthy" in the a project while the underlying agent reports them as "not set up." Attempting to remove an affected connection currently returns a 401 error. We're investigating and will post updates here.
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
About the median
Other Replit incidents
All incidentsReplit·Agent and Workspace Issues
Replit reports a major outage that affects Agent and Workspace interactions. Replit is now monitoring the fix. Replit states that agent interactions should work again and asks users to update the browser tab.
Replit·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.
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.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 "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.cc/feed.xml?providers=replit/feed subscribe https://outages.cc/feed.xml?providers=replitFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane