Some users are unable to publish apps with an external DATABASE_URL error
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.
The latest update from Replit.
State
Resolved
Started
61 d ago
2026-09-01 14:56 UTC
Lasted
3 days
until 2026-09-04 17:19 UTC
Worst impact
Partial outage
Timeline
5 updatesInvestigating
3 h 29 min 5%
Identified
23 h 34 min 32%
Monitoring
47 h 19 min 64%
Updates
Times in UTCAs posted by Replit
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.
Production data is confirmed to be safe after a configuration error during deploys that impacted users on September 1st, 2026. The issue has been resolved going forward and we are working on a fix to restore impacted projects. If your project was impacted by this error please reach out to support.
We have deployed a forward fix. Please contact support if you cannot deploy.
We have identified a fix for failing app publishing and are rolling it out.
Some users are unable to publish their apps and may see errors related to databases. Our engineers are investigating, and we’ll share an update as more information becomes available.
Replit in the last 90 days
Full historyIncidents in 90 days
34
Days with an incident
46
Median duration
2 h 3 min
This incident
36× the median
Other Replit incidents
All incidentsReplit·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.
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.
Replit·Investigating issues related to platform access
Access to Replit services has recovered.
Replit·Users can't access privately deployed apps
Users are able to access their private apps again.
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.
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.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.
https://outages.cc/feed.xml?providers=replit/feed subscribe https://outages.cc/feed.xml?providers=replitFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane