How do I check if Bubble is down right now?

Open status.bubble.io — Bubble's official status page. It reports the availability of Bubble's editor and of apps hosted on Bubble, with components including Bubble Core (editor and hosted apps), Bubble Dedicated, Native Mobile, the Security Dashboard, the support portal, and third-party dependencies like AWS, Cloudflare, and Intercom.

Why is my Bubble app down when status.bubble.io is green?

Then the problem is on your side. The usual causes: a custom-domain DNS or configuration issue, a change that behaves differently in live than in version-test, or workload-unit exhaustion — with overages disabled (or on the Free plan), Bubble takes the app offline when WU run out and emails you. None of these appear on Bubble's status page.

Which URL should I test — my domain or bubbleapps.io?

Both. The default live URL is yourapp.bubbleapps.io and development is yourapp.bubbleapps.io/version-test. With a custom domain configured, requests to bubbleapps.io redirect to your domain, which serves the live version (dev sits at yourdomain.com/version-test). If bubbleapps.io works but the custom domain doesn't, you have a DNS or domain configuration problem, not a Bubble outage.

Can my Bubble app go offline because of workload units?

Yes. The current workload model doesn't throttle, but if overages are disabled and your app exhausts its workload units, Bubble takes it offline and notifies you by email — and Free-plan apps can't enable overages at all. The app comes back when you enable overages, buy a workload tier, or the next billing period starts.

Bubble decision guide

Bubble app down? First find out whose outage it is.

Q: What does a green status page NOT tell me?

Whether your app works. A platform status page reports infrastructure, not your flows: it will stay green while your login emails bounce, your Stripe webhook posts to version-test, a privacy rule empties your search results, or a recurring workflow silently stops. Platform up and app working are different facts — you need your own checks for the second one.

Check status.bubble.io first — it's Bubble's official status page and covers the editor and apps hosted on Bubble, plus dependencies like AWS and Cloudflare. If the platform is green, the outage is yours: a custom domain misconfiguration, an undeployed change, or workload-unit overage taking the app offline. And remember a green status page says nothing about whether your login, checkout, or webhooks actually work.

Start 14-day trial Jump to the decision list

why it happens

"Down" is three different problems wearing one word

When someone says their Bubble app is down, it's one of three things: Bubble's infrastructure is having an incident (rare, visible on the status page), your app's plumbing failed (domain, deploy, workload units — invisible to Bubble's status page), or the app is "up" but a flow that earns money is broken (invisible to everyone's status page). The decision list below separates them in a few minutes of checks, in order of cheapest evidence first.

the decision list

Five checks, in order — whose outage is it?

Check status.bubble.io before touching anything

Symptom: Your app is unreachable or erroring for everyone at once.

Fix: status.bubble.io is the official page, covering the editor and apps hosted on Bubble: Bubble Core, Dedicated, Native Mobile, the Security Dashboard, the support portal, plus third-party dependencies (AWS, Cloudflare, Intercom). An active incident on Bubble Core means it's their outage — subscribe to updates and don't deploy mid-incident. Green? Keep reading: it's yours.

Test the bubbleapps.io URL and your custom domain separately

Symptom: Some people can reach the app, others can't.

Fix: The live default is yourapp.bubbleapps.io; with a custom domain configured, bubbleapps.io redirects to the domain, which serves live (dev is yourdomain.com/version-test). If bubbleapps.io answers but the domain doesn't, the problem is DNS or domain configuration — yours to fix, invisible to Bubble's status page.

Make sure you're judging live, not version-test

Symptom: "It works for me" — but you're in the editor, on /version-test, with separate data.

Fix: Development and Live are parallel environments with independent databases. A change that exists in dev but was never deployed makes live look broken; data created in testing won't be in live. Open the live URL in an incognito window before declaring anything fixed or broken.

Rule out workload-unit overage offline

Symptom: The app went dark suddenly; pages and workflows all stopped together.

Fix: With overages disabled — or on Free, which can't enable them — exhausting workload units takes the app offline, and Bubble emails you (with a warning at 75% first). Check the inbox of the account owner, then enable overages or buy a tier to restore service, and find the WU-hungry workflow before the next cycle.

If the platform is green and URLs answer: your flow is what's broken

Symptom: The homepage loads fine, but signups, checkout, or emails are failing.

Fix: This is the gap between "up" and "working". A green status page and a 200 homepage say nothing about login, payment webhooks, scheduled workflows, or email delivery. Walk the actual flow as a stranger (incognito, real account), watch the provider dashboards (Stripe, email), and read the server logs' Errors filter. Or have checks doing this around the clock — next section.

copyable runbook

Paste this into your incident notes

Bubble "app down" decision runbook

[ ] status.bubble.io: active incident on Bubble Core / Dedicated / dependencies?
    -> YES: platform outage. Subscribe to updates. Don't deploy mid-incident.
[ ] yourapp.bubbleapps.io answers? Your custom domain answers?
    -> bubbleapps.io OK + domain dead: DNS / domain config. Yours.
[ ] Incognito, LIVE url (no /version-test): does the symptom reproduce?
    -> Works in editor only: undeployed change or dev-only data.
[ ] Owner inbox: WU 75% warning or "taken offline" email?
    -> Overage offline: enable overages / buy tier; hunt the WU-hungry workflow.
[ ] Everything 200 but a flow broken: walk login -> core action -> payment as
    a stranger; check Stripe/email dashboards; read server logs Errors filter.

how to catch it automatically

What a green status page can't see — and checks can

The decision list above is exactly what Nightlamp automates, with the platform/app distinction built in. An http_status check on both the bubbleapps.io URL and your custom domain localizes "down" instantly — and an offline app from WU overage shows up here at the first failed probe, not when a customer emails. An ssl check watches the custom domain's certificate. A browser_journey walks login and checkout on the live URL, which is how you find out the app is broken while every status page on the internet is green. When a real Bubble incident is in progress, that context lands in the diagnosis — so you're not debugging your own app during someone else's outage.

http_status — bubbleapps.io and custom domain, separately

ssl — custom-domain certificate validity

browser_journey — login and checkout on live

http_keyword — live page serves expected content

visual_snapshot — the live homepage still looks like yours

heartbeat — recurring workflows still running

faq

Bubble app down FAQ

How do I check if Bubble is down?

status.bubble.io — the official page for the editor and apps hosted on Bubble, including third-party dependencies like AWS and Cloudflare.

Bubble is green but my app is down. Why?

It's on your side: custom-domain DNS, an undeployed or bad change in live, or workload units exhausted with overages disabled (which takes the app offline).

Which URL do I test?

Both: yourapp.bubbleapps.io and your custom domain. The domain serves live; /version-test is dev. If one answers and the other doesn't, you've localized the problem.

Can workload units take my app offline?

Yes — offline, not throttled, when WU run out with overages disabled (Free can't enable them). Bubble warns by email at 75%.

What does a green status page not tell me?

Whether your login, checkout, webhooks, emails, or scheduled workflows work. Platform-up and app-working are different facts.

Skip the "is it me or is it Bubble?" panic entirely

Nightlamp watches both URLs, the certificate, and the flows that earn money — and tells you whose outage it is in the first alert. No more refreshing the status page while customers wait.

Start 14-day trial · no card

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.