Is Replit down right now?

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.

No - as of the most recent check, replit.com is responding normally to HostTracker's monitoring network, and has been up for 21d 7h. Over the last 24 hours it recorded 100.00% uptime across 0 incidents. If it is failing for you specifically, the cause is local - your network, DNS cache, or a regional route - and the live probe results above will show which locations, if any, are affected.

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.