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-09 00:57 UTC and ended at 2026-11-09 17:57 UTC. It lasted 17 h 1 min.

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 ·

Chat is failing on mobile

Q: What happened?

Replit reported "Chat is failing on mobile" on its status page at 2026-11-09 00:57 UTC. Replit Chat did not work on mobile devices. Replit reports that the fix is in place and Chat is working on mobile now. The incident is resolved. The incident lasted about 17 hours.

ResolvedOfficial update

Replit Chat did not work on mobile devices. Replit reports that the fix is in place and Chat is working on mobile now. The incident is resolved. The incident lasted about 17 hours.

State

Resolved

Started

Lasted

17 h 1 min

Worst impact

Partial outage

Timeline

4 updates

00:5705:1209:2713:4217:57

Partial outageUpdate postedTimes in UTC

Investigating

21 min 2%

Monitoring

16 h 39 min 98%

Updates

Times in UTC

As posted by Replit

Resolved

Chat is working on mobile now.

Monitoring

The fix is in place and mobile chat is now functional. We are monitoring.

Monitoring

We are currently investigating this issue

Investigating

We are currently investigating this issue

Replit in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

2 h 34 min

This incident

6.6× the median

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

13 days

median 2 h 34 min

90 days agoToday

Other Replit incidents

All incidents

Replit·Some Replit workspaces are inaccessible

Some Replit workspaces are inaccessible. Replit reports that this incident is resolved. It lasted 16 minutes.

Resolved

Replit·Replit chats are inaccessible

Replit chats were inaccessible. The incident affected Replit chats. Replit reports that the issue is resolved. The outage lasted 43 minutes.

Resolved

Replit·Agent and Workspace Issues

The Replit Agent and Workspace do not fully work. This partial outage affects Agent interactions and Workspace. Replit reports that the issue is resolved and it lasted about 13 hours and 26 minutes.

Resolved

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.

Resolved

Replit·Investigating issues related to platform access

Access to Replit services has recovered.

Resolved

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

RSS

https://outages.live/feed.xml?providers=replit

Slack

/feed subscribe https://outages.live/feed.xml?providers=replit

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane