outages.live
Live
ReplitIncident ·

Reserved VM publishes failing at Promote: "inspect shared VPC attachment" error

ResolvedOfficial update
0

Replit reports that reserved VM publishing failed at Promote with an "inspect shared VPC attachment" error. Replit identified the cause and resolved the issue. The outage lasted about 69 minutes.

State

Resolved

Started

Lasted

1 h 9 min

Worst impact

Degraded

Timeline

2 updates
06:1706:3506:5207:0907:26
DegradedUpdate postedTimes in UTC

Identified

1 h 9 min 100%

Updates

Times in UTC

As posted by Replit

Resolved

The issue is resolved. Thanks for your patience.

Identified

There is an outage for reserved VM publishing. We have identified the root cause and is addressing it.

Replit in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

31

Days with an incident

42

Median duration

2 h 6 min

This incident

45% shorter than the median

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

13 days
median 2 h 6 min
90 days agoToday

Other Replit incidents

All incidents

Replit·Chat is failing on mobile

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.

Resolved

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

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