Is Replit down right now?
Live status for replit.com isn't set up in this environment yet - check any URL manually instead.
Checking replit.com right now
A fresh check, started when you opened this page - each probe runs its own independent DNS, TCP, TLS and HTTP request. Anonymous runs sample the network; a signed-in account checks from more locations.
About Replit outages
Written by the HostTracker monitoring team · updated from live probe data.
Replit runs code inside on-demand workspaces and containers, and its own architecture splits into a few pieces that can each fail on their own: the browser-based editor and its live collaboration, the container infrastructure that actually boots and runs a workspace, the AI agent that writes and edits code on request, and Deployments, which hosts a project's published app separately from the development workspace itself. That last split matters most in practice - a workspace failing to boot for editing doesn't necessarily mean an already-deployed app built with Replit goes offline, since Deployments runs on its own hosting path once a project is published.
Common causes of Replit downtime
Workspace or container boot failures, where the isolated environment behind a project fails to provision, blocking editing before any code runs
Deployments and the editor's workspace hosting running on separate infrastructure, so a published app can stay online while the development workspace fails to boot, or the reverse
AI agent capacity constraints during high-demand periods, which slow or queue agent-assisted coding requests without affecting the plain editor
Websocket connectivity problems behind restrictive school or corporate networks, which block the live editor's real-time features while the same account works normally on an open connection
Not sure whether it's Replit or your own connection? Read the full breakdown in our website down checker guide for a general walkthrough of diagnosing any outage, from DNS failures to expired certificates.
Other services we track
HostTracker has monitored websites and online services since 2004 and is trusted by 500,000+ sites today, covering 14 check types from 300+ global locations. Want the same multi-location confirmation and instant alerts for your own site or any service you depend on? Getting started costs nothing - start a free monitor or compare plans and pricing.
Questions people ask during an outage
The live probe run on this page tests replit.com from a broad sample of HostTracker's 300+-location monitoring network - many independent networks at the same moment, rather than just your own connection. If every location fails to reach it, the outage is real and affects everyone; if only a few locations fail while most load normally, the problem is local to those regions or networks rather than Replit being fully down. A single refresh from your own browser can never make that distinction, because it only ever tests from one vantage point on one network.
Yes. HostTracker lets you add any URL - including third-party services you depend on, not just your own website - as a monitored target, and notifies you automatically the moment it becomes unreachable. Before sending an alert, HostTracker re-verifies a failure from multiple locations in its 300+-location network, so you're notified about real, confirmed outages rather than a single location's momentary blip. The free plan checks two monitors every 30 minutes indefinitely at no cost; paid plans check as often as once a minute, with alerts available through SMS, email, voice call, and several messenger apps.
Run the live check at the top of this page - it tests replit.com from HostTracker's 300+ monitoring locations at once and tells you within seconds whether Replit is reachable for everyone or only failing for you.
It likely is. Replit Deployments hosts a published app on infrastructure separate from the development workspace, so a problem booting the workspace you'd use to edit code doesn't automatically mean an already-deployed app stops serving traffic. These two systems can fail independently, which is worth knowing before assuming a wider outage just because the editor itself isn't loading.
Probably not a full outage. Replit's AI agent runs as its own component layered on top of the plain code editor, and capacity constraints during busy periods can slow or queue agent requests specifically while the underlying editor, file system, and container infrastructure keep working normally for manual editing. A working editor with an unresponsive agent points at agent-specific load rather than a platform-wide problem.
This is very often a network restriction rather than a Replit outage. The live editor relies on websocket connections for real-time features, and restrictive school or corporate networks frequently block or interfere with websocket traffic even while allowing normal web browsing, which breaks the collaborative editor experience specifically. Testing on an unrestricted connection is the fastest way to tell a local network policy from an actual service problem.
Monitor your website from 300+ locations
Start a free trial and get instant alerts when your site goes down - verified from multiple locations before you're notified.