Is Replit down?
No, Replit is not down.
Replit’s status page reports no incidents, replit.com and replit.com responded from 6 regions, and nobody reported problems in the last hour.
- Official statusNo incidentsstatus.replit.com
- Reachable6 of 6 regionsReplit GraphQL API 6/6 · replit.com 6/6
- Reports in the last hour0Normal
Replit’s status page
From status.replit.com. Read at
- IntegrationsOperational
- Published App DatabasesOperational
- Mobile AppOperational
- Development SandboxesOperational
- Replit AgentOperational
- PublishingOperational
- Published AppsOperational
- Replit AuthOperational
Show all 9 components
- Development DatabasesOperational
Not working for me
Pick what’s broken. Reports from everyone show up on the chart below within 5 minutes.
Last 24 hours
No problems in the last 24 hours, median response 161 ms, and 0 reports.
- Operational
- Degraded
- Partial outage
- Major outage
- No data
- Reachability check (replit.com)
By region
| Region | Replit GraphQL API replit.com | replit.com replit.com |
|---|---|---|
| N. Virginia us-east-1 | 400 · 49 ms | 200 · 120 ms |
| Oregon us-west-2 | 400 · 148 ms | 200 · 176 ms |
| Frankfurt eu-central-1 | 400 · 127 ms | 200 · 115 ms |
| Singapore ap-southeast-1 | 400 · 273 ms | 200 · 69 ms |
| Tokyo ap-northeast-1 | 400 · 197 ms | 200 · 132 ms |
| São Paulo sa-east-1 | 400 · 152 ms | 200 · 180 ms |
Two regions check Replit every minute, and any failure is rechecked from all of them. Each row shows the latest result. How we check
Last 90 days
We have checked Replit ourselves since Oct 28, 2026. Earlier days come from its status page.
53 days with problems in the last 90 days.
Recent incidents
Incidents: 7 in the last 30 days and 35 in the last 90, lasting a median of 2 h 3 min.
- Users can't access privately deployed appsPartial outage41 min
- Hubspot Connectors is not workingDegraded10 h 43 min
- Billing issueMajor outage5 h 13 min
- Users unable to top-upDegraded3 h 45 min
- Connection errors affecting some customersDegraded1 h 3 min
- Connectors platform latencyDegraded1 day
- Issue loading integrations pagePartial outage1 h 46 min
- Connector status mismatch and removal errorsDegraded2 h 5 min
- GitHub connector may not be working for usersPartial outage19 days
- Resolved: Degraded Agent Performance Due to Upstream Model Provider ErrorsPartial outage51 min
If Replit isn’t working for you
Replit is a browser-based development platform with an AI Agent that builds, runs and publishes apps.
Common Replit errors
| Error | What it means | Usually | What to do |
|---|---|---|---|
Agent encountered an error while running, we are investigating the issue. | Replit Agent stopped mid-task because of an error on Replit's side. | An outage | Wait and retry, and check status.replit.com; users report it can repeat during incidents. Source |
Application failed to respond | Your published app is not listening on the port Replit expects. | Your side | Bind your server to the PORT environment variable and listen on 0.0.0.0. Source |
502 Bad Gateway | Your published app's process crashed or returned output the server could not use. | Your side | Check deployment logs for crash errors just before the 502s appear. Source |
403 Forbidden | Your published app rejected the request, for example because of oversized cookie headers, missing authentication or an access restriction. | Your side | Clear cookies for the domain and check your app's access settings. Source |
Is it just you?
- Check whether the app works in Preview: if Preview fails, the problem is the app, and publishing will not fix it.
- If Preview works but the published app fails, add your production Secrets in the Publishing pane; editor Secrets do not carry over.
- Open the Logs tab in the Publishing pane for crash or startup errors.
- If the Replit editor or Agent will not load at all, check status.replit.com and the reports on this page.
Alternatives to Replit
Questions
Replit's help center lists the usual causes: the server not listening on the expected port, a crash behind a 502, missing production Secrets, or access restrictions behind a 403. Check the Publishing logs first.
If the Replit editor and Agent work but your published app does not, the issue is usually your app or its configuration. If the editor or Agent fails for many users, it is a Replit incident.
Sources: docs.replit.com, docs.replit.com, replit.discourse.group
Get alerted when Replit breaks your app.
If your product or your team depends on Replit, its outage is your outage, and your users will blame you, not Replit. Point a Site Qwality monitor at the Replit endpoint you actually rely on, put your own site next to it, and we alert you on Slack, email, SMS or any webhook the moment either one stops answering.