Skip to main content
Bubble logo

Is Bubble Down?

No — Bubble is up

Reachable from all 6 checked regions

Average response time: 983ms

Last checked · checks run every 6 hours

Official status page: https://status.bubble.io

Bubble uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
445ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 15 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

15-day clean streak
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: no data
Aug 16: no data
Aug 17: no data
Aug 18: no data
Aug 19: no data
Aug 20: no data
Aug 21: no data
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: 100.00% uptime, 24 checks
Aug 27: 100.00% uptime, 32 checks
Aug 28: 100.00% uptime, 32 checks
Aug 29: 100.00% uptime, 32 checks
Aug 30: 100.00% uptime, 32 checks
Aug 31: 100.00% uptime, 32 checks
Sep 1: 100.00% uptime, 32 checks
Sep 2: 100.00% uptime, 30 checks
Sep 3: 100.00% uptime, 21 checks
Sep 4: 100.00% uptime, 23 checks
Sep 5: 100.00% uptime, 32 checks
Sep 6: 100.00% uptime, 32 checks
Sep 7: 100.00% uptime, 21 checks
Sep 8: 100.00% uptime, 39 checks
Sep 9: 100.00% uptime, 36 checks
Sep 10: no data
Aug 12 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
3093ms
DNS 0ms TCP 2ms TLS 8ms TTFB 2916ms
arn
673ms
DNS 0ms TCP 3ms TLS 7ms TTFB 639ms
bom
360ms
DNS 0ms TCP 2ms TLS 12ms TTFB 354ms
cdg
509ms
DNS 0ms TCP 2ms TLS 16ms TTFB 477ms
dfw
781ms
DNS 0ms TCP 4ms TLS 10ms TTFB 777ms
ewr
484ms
DNS 0ms TCP 2ms TLS 10ms TTFB 478ms

What Bubble does

Bubble is a no-code platform for building web applications visually. Users design pages, define workflows and model data in a browser-based editor, and Bubble hosts the application that results. Small teams and non-developers run production software on it, so an incident takes down somebody's live product rather than only a development tool.

What an outage looks like

Two different failures wear the same name. Apps hosted on Bubble stop serving, so visitors meet errors or blank pages on a live site. Separately, the editor fails to load or refuses to save workflow changes while published apps keep running normally. Native mobile apps built on Bubble are a third component again.

What to do about it

Check Bubble's status page and identify the component, since Bubble Core, Bubble Dedicated and Bubble Native Mobile fail independently. The page also tracks AWS and Cloudflare, which Bubble runs on, so an upstream incident shows there first. If only the editor is affected, published apps are usually still serving and your visitors need nothing from you.

Is it down for everyone, or just you?

If this page says Bubble is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Webflow
Webflow
Retool
Retool
AWS
AWS
Cloudflare
Cloudflare

Bubble outage FAQ

Is my live app down, or just the editor?
They are separate components and fail separately. The editor is where you build; Bubble Core serves the apps your visitors reach. An editor outage is invisible to your users, and the reverse holds too. Load your published app in a private window to tell which one you are actually experiencing.
Does the status page always report editor problems?
Not reliably. Users have reported editor sessions failing for hours while the status page showed no incident, a recurring complaint in Bubble's own forum. Independent measurement of the editor host is one way to tell whether the fault is yours or Bubble's before spending an afternoon debugging your own workflows.
Does an AWS or Cloudflare outage take Bubble down?
It can, and Bubble's status page tracks both for that reason, listing AWS across eight components and Cloudflare across four. Bubble runs on that infrastructure, so a regional AWS problem can surface as slow or failing Bubble apps. The upstream row usually turns before Bubble's own components do.
Will I lose editor work during an outage?
Changes saved before the incident are stored. Work in progress that never reached a save may not be. Bubble's editor saves continuously rather than on a button, so the exposure is normally small, but avoid making large structural changes while the editor is unstable.

How we measure this

  • We request Bubble's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 6 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Bubble publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Bubble goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required