Voice input degraded
Voice input (speech to text) is failing or slower than usual for some users. Replit reports that the service is in monitoring and works again for most users. Replit watches the service while the transcription provider finishes the fix.
State
Monitoring
Started
Ongoing for
1 h 19 min
Worst impact
Degraded
Timeline
2 updatesIdentified
1 h 4 min 81%
Monitoring
15 min 19%
Updates
Times in UTCAs posted by Replit
Voice input is working again for most users. We’re watching it while our provider finishes their fix. Next update by 10:00 AM PT.
Voice input (speech to text) is failing or slower than usual for some users because of an issue at our transcription provider. Typing still works normally. We’re monitoring their fix and will post an update by 9:30 AM PT.
Replit in the last 90 days
Full historyIncidents in 90 days
28
Days with an incident
39
Median duration
2 h 6 min
This incident
37% shorter than the median
Other Replit incidents
All incidentsReplit·Reserved VM publishes failing at Promote: "inspect shared VPC attachment" error
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.
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.
Replit·Some Replit workspaces are inaccessible
Some Replit workspaces are inaccessible. Replit reports that this incident is resolved. It lasted 16 minutes.
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.
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.
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.
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.
https://outages.live/feed.xml?providers=replit/feed subscribe https://outages.live/feed.xml?providers=replitFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane