Replit did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-11-01 15:42 UTC. This page shows the end time when Replit marks it resolved.

How do I get alerts for Replit?

Subscribe to the Replit live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Replit. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

ReplitIncident · 2026-11-01 15:42 UTC

Agent and Workspace Issues

Q: What happened?

Replit reported "Agent and Workspace Issues" on its status page at 2026-11-01 15:42 UTC. 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.

Partial outageOfficial update

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.

State

Monitoring

Started

3 h ago

2026-11-01 15:42 UTC

Ongoing for

3 h 7 min

Worst impact

Major outage

Timeline

2 updates

15:4216:2917:1618:0218:49

Major outagePartial outageUpdate postedTimes in UTC

Monitoring

3 h 7 min 100%

Updates

Times in UTC

As posted by Replit

Monitoring2026-11-01 17:27 UTC

For those seeing Agent failures can you please update the browser tab, we expect agent interactions to be working again.

Monitoring2026-11-01 17:18 UTC

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 history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

2 h 3 min

This incident

1.5× the median

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

13 days

median 2 h 3 min

90 days agoToday

Other Replit incidents

All incidents

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 1 d ago

Replit·Investigating issues related to platform access

Access to Replit services has recovered.

Resolvedresolved 2 d ago

Replit·Users can't access privately deployed apps

Users are able to access their private apps again.

Resolvedresolved 9 d ago

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.

Resolvedresolved 9 d ago

Replit·Users unable to top-up

Users are able to top up again.

Resolvedresolved 23 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