Is Bubble down — or is it just your app?
Check the live indicator below (pulled from status.bubble.io). If Bubble reports an outage, every Bubble app is affected and there is nothing to fix on your side — wait it out. But most “my Bubble app is down” moments happen while Bubble is green: a broken workflow, an expired API Connector token, or a failed Stripe webhook takes down only your app. Here is how to tell the difference in five minutes.
Checking Bubble's official status… live from status.bubble.io
Nightlamp is not affiliated with Bubble and this is not the official status page. For platform incidents, the source of truth is status.bubble.io. 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 status.bubble.io does tell you
- Availability of Bubble's shared hosting cluster and editor
- Dedicated-instance infrastructure incidents
- Scheduled platform maintenance windows
- Platform-wide degradations (slow page loads, workflow queue delays)
Bubble can be green while your app is down
Your Stripe webhook is failing while Bubble is green
A live Stripe endpoint still pointing at a version-test URL, an /initialize URL left in place, or a mismatched signing secret breaks checkout for your app only. Bubble's status page will never mention it — Stripe delivered the event, your workflow rejected it.
A scheduled backend workflow quietly stopped
Recurring workflows can stop after a plan change, a capacity hit, or an error in the workflow itself. Nothing turns red anywhere: your daily digest, cleanup job, or subscription renewal simply stops happening until a customer notices.
An API Connector token expired
Calls to OpenAI, Airtable, or any external API start returning 401 the moment a key is rotated or a trial ends. Bubble is fully operational — the page that depends on that call is not.
Your custom domain or SSL certificate broke
DNS records and domain renewals are yours, not Bubble's. Your app can be perfectly healthy on bubbleapps.io while yourdomain.com serves a certificate warning or nothing at all.
Platform problem or your problem? Run this checklist
- Check status.bubble.io — if there's an active incident, stop here and wait.
- Open your app in a private/incognito window: does the page itself load?
- Test the broken flow specifically (checkout, signup, form submit) — not just the homepage.
- Check Bubble's server logs and the scheduler for paused or erroring workflows.
- Check the dashboards of the services your flows call: Stripe webhooks, SendGrid/Postmark sends, external APIs.
- Trigger a login email and confirm it arrives — auth-email failures look exactly like “the app is down” to users.
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 step-by-step guide to fixing a Bubble app that's down walks through each failure symptom by symptom.
Stop checking status pages after the fact
Nightlamp watches your Bubble 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 cardFrequently asked questions
Bubble's status page is green but my app is down. Why?
Because status.bubble.io reports Bubble's infrastructure, not your app's logic and integrations. Broken workflows, expired API tokens, failed Stripe webhooks, stopped scheduled workflows, and custom-domain or SSL problems all take your app down while the platform stays green.
Does Bubble's status page cover my custom domain?
No. Your DNS records, domain registration, and SSL renewals are outside Bubble's status reporting. If yourdomain.com fails while yourapp.bubbleapps.io works, the problem is in your domain setup, not Bubble.
How do I get alerted when my Bubble app breaks but Bubble is up?
You need monitoring that watches your specific flows — checkout, signup, login emails, scheduled jobs — rather than the platform. Nightlamp probes those paths continuously and a real engineer sends a plain-English diagnosis when one of them 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.