outages.live
Live

Replit

Replit is reporting partial outage

Checked 1 min ago Partial outage

Major service outage

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.

Partial outageupdated 3 h ago

History

90 days agoToday

Incidents in 90 days

34

Days with an incident

46

Median duration

2 h 3 min

Longest incident

13 days

Components

9
Integrations Operational
90 days agoNo incidentsToday
Published App Databases Operational
90 days agoNo incidentsToday
Mobile App Operational
90 days agoNo incidentsToday
Development Sandboxes Operational
90 days agoNo incidentsToday
Replit Agent Operational
90 days agoNo incidentsToday
Publishing Operational
90 days agoNo incidentsToday
Published Apps Operational
90 days agoNo incidentsToday
Replit Auth Operational
90 days agoNo incidentsToday
Development Databases Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 31, 2026

Duration49 min09:55 to 10:44Investigating an issue related to the agent's ability to process imagesPartial outage

We have resolved some of the earlier issues where connections to replit was disrupted.

Oct 30, 2026

Duration34 min22:14 to 22:47Investigating issues related to platform accessMajor outage

Access to Replit services has recovered.

Oct 23, 2026

Duration41 min21:04 to 21:45Users can't access privately deployed appsPartial outage

Users are able to access their private apps again.

Duration10 h 44 min16:35 to 03:19Hubspot Connectors is not workingDegraded

HubSpot connectors that use Replit’s default configuration are not working. We’ve identified the root cause and are currently working on a fix.

Oct 9, 2026

Duration3 h 46 min20:17 to 00:02Users unable to top-upDegraded

Users are able to top up again.

Oct 6, 2026

Duration1 h 4 min21:26 to 22:30Connection errors affecting some customersDegraded

We've rolled back successfully and all monitors related to this connection issue have resolved.

Duration32 h 39 min17:44 to 02:22Connectors platform latencyDegraded

We have identified and resolved the connectors platform latency issue.

Oct 1, 2026

Duration1 h 47 min13:25 to 15:11Issue loading integrations pagePartial outage

The issue affecting loading of the integrations page has been resolved. Integrations should be functional again. If you are still seeing issues loading or using integrations, please contact support and we will help investigate.

Sep 24, 2026

Duration13 days16:05 to 14:52GitHub connector may not be working for usersPartial outage

We've identified an issue with GitHub connectors starting Tuesday 1PM PT that prevented users from being able to connect their project source code to GitHub. This issue is recovering and we'll keep you updated here.

Sep 22, 2026

Duration2 h 6 min21:36 to 23:42Connector status mismatch and removal errorsDegraded

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.

Sep 17, 2026

Duration52 min20:40 to 21:31Resolved: Degraded Agent Performance Due to Upstream Model Provider ErrorsPartial outage

We have resolved the incident related to degraded agent performance due to increase in errors from our upstream model providers.

Sep 10, 2026

Duration28 min20:30 to 20:58Resolved: Agent experiencing increased errorsMajor outage

We have deployed a fix for increased error in agents. We apologize for any inconvenience.

Sep 4, 2026

Duration51 min00:53 to 01:44Service Functionality ResumedDegraded

We have resolved the issue.

Sep 1, 2026

Duration5 h 50 min15:50 to 21:40Upstream IssuesPartial outage

All systems are healthy. The upstream cloud provider issue has been resolved and we're setting the status back to OK after monitoring.

Duration3 days14:56 to 17:19Some users are unable to publish apps with an external DATABASE_URL errorPartial outage

We've deployed a fix for the issue causing some projects to fail publishing with a DATABASE_URL error, and publishing should work normally now. If you're seeing missing data in your development database, columns that appear to be gone, or a migration with an unusually high number of drop statements, please contact support (replit.com/help) so we can look into it with you directly. Thanks for your patience while we worked through this.

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane