outages.live
Live
ReplitIncident · 2026-11-02 22:05 UTC

Some Replit workspaces are inaccessible

ResolvedOfficial update
0

Some Replit workspaces are inaccessible. The incident affected conversations in these workspaces. Replit reports that the issue is resolved. The outage lasted 16 minutes.

State

Resolved

Started

2 h ago

2026-11-02 22:05 UTC

Lasted

16 min

until 2026-11-02 22:21 UTC

Worst impact

Major outage

Timeline

2 updates
22:0522:0922:1322:1722:21
Major outageUpdate postedTimes in UTC

Investigating

16 min 100%

Updates

Times in UTC

As posted by Replit

Resolved2026-11-02 22:21 UTC
Investigating2026-11-02 22:18 UTC

We are currently investigating issues with accessing conversations in some Replit workspaces,

Replit in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

34

Days with an incident

46

Median duration

1 h 56 min

This incident

86% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

13 days
median 1 h 56 min
90 days agoToday

Other Replit incidents

All incidents

Replit·Replit chats are inaccessible

Replit chats were inaccessible. Access to Replit chats is restored, and the incident is resolved. The outage lasted about 43 minutes.

Resolvedresolved 59 min ago

Replit·Agent and Workspace Issues

Replit reports that the Agent and Workspace issues affected Agent interactions. Replit stated that the issue is resolved. The outage lasted about 13 hours and 26 minutes.

Resolvedresolved 19 h ago

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.

Resolvedresolved 3 d ago

Replit·Investigating issues related to platform access

Access to Replit services has recovered.

Resolvedresolved 3 d ago

Replit·Users can't access privately deployed apps

Users are able to access their private apps again.

Resolvedresolved 10 d ago

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.

Prompt
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.

RSS
https://outages.cc/feed.xml?providers=replit
Slack
/feed subscribe https://outages.cc/feed.xml?providers=replit

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane