platform status · independent triage guide

Is Replit down — or is it just your app?

Check status.replit.com for official platform incidents — if the workspace or Deployments infrastructure is down, it affects everyone and the fix is on Replit's side. But a deployment that crash-loops after a dependency update, an Autoscale app that hit its resource limits, or a secret that never made it into production breaks your app alone, with Replit's status page showing green the whole time.

Replit doesn't expose a public status feed we can read from your browser check status.replit.com directly

Nightlamp is not affiliated with Replit and this is not the official status page. For platform incidents, the source of truth is status.replit.com. This page exists for the other half of the question: what to do when the platform is green and your app still isn't working.

what their status page covers

What status.replit.com does tell you

  • The Replit workspace and editor
  • Deployments infrastructure (Autoscale, Reserved VM, Static)
  • Replit AI/Agent availability
  • Platform-wide networking incidents
what it can't tell you

Replit can be green while your app is down

Your deployment is crash-looping

A dependency update, a syntax error pushed at midnight, or an unhandled exception on startup leaves your deployment restarting forever. Replit's infrastructure is healthy; your process never stays up.

You hit resource or scaling limits

An Autoscale deployment that exhausts its compute budget, or a Reserved VM out of memory, starts dropping requests. That's a limit on your deployment, not a platform incident.

A secret didn't make it to production

Secrets configured in the workspace are not automatically the secrets your deployment sees. A missing or stale API key in the deployment environment breaks exactly one app: yours.

Your database or custom domain is the problem

Connection-limit errors against your Postgres database, or a custom domain whose DNS record drifted, take your app offline while every Replit system reports operational.

five-minute triage

Platform problem or your problem? Run this checklist

  1. Check status.replit.com — workspace or Deployments incidents are platform-wide.
  2. Open your deployment's logs: is the process crash-looping or failing on startup?
  3. Check resource usage against your deployment's limits.
  4. Compare deployment secrets against what the app actually needs — workspace secrets don't auto-sync.
  5. Test the deployed URL's core flow in a private window, not just the root page.
  6. If you use a custom domain, verify DNS and the certificate; test the replit.app URL as a control.

If sign-in emails are part of the broken flow, our free magic-link tester checks the full email round-trip in one click.

Checklist points at your own app? Our guide to fixing a Replit app that stopped working walks through each failure symptom by symptom.

Stop checking status pages after the fact

Nightlamp watches your Replit app's actual flows — checkout, signup, login emails, scheduled jobs — and a real engineer sends a plain-English diagnosis when one breaks, whether or not the platform is having an incident.

Start 14-day trial · no card
faq

Frequently asked questions

Replit's status page is green but my app is down. Why?

status.replit.com reports Replit's infrastructure. Crash-looping deployments, exhausted resource limits, missing deployment secrets, database connection failures, and custom-domain DNS problems all break your app while the platform stays green.

Why doesn't this page show live Replit status?

Replit's status page blocks automated requests behind a security challenge, so there is no public JSON feed we can read honestly from your browser. Rather than show fake or stale data, we link you straight to status.replit.com.

How do I get alerted when my Replit app breaks but Replit is up?

Monitor your deployment's actual behavior — uptime of the deployed URL, the core user flow, scheduled jobs, login emails. Nightlamp probes those continuously and a real engineer sends a plain-English diagnosis when something breaks.

Newsletter

One real no-code incident + the fix, monthly

A post-mortem from a real no-code outage — what broke, how it was found, and the fix — once a month. Confirming also gets you the no-code incident runbook pack.

Double opt-in. One-click unsubscribe. No spam, ever.