Skip to main content
Bubble logo

Is Bubble Down?

No — Bubble is up

Reachable from all 8 checked regions

Average response time: 481ms

Last checked · checks run every 6 hours

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

Components the vendor reports as affected: Bubble Editor Degraded Performance

A component listed here does not necessarily mean a full outage — large providers routinely report maintenance on individual locations. It only affects the verdict above when the vendor marks it major or critical and our own checks also saw Bubble fail from enough regions to rule out probe noise.

Bubble uptime

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

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

30-day history

26-day clean streak
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: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 32 checks
Sep 13: 100.00% uptime, 24 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 31 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 31 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: no data
Aug 23 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.

iad
263ms
DNS 81ms TCP 2ms TLS 9ms TTFB 254ms
jnb
463ms
DNS 48ms TCP 0ms TLS 6ms TTFB 457ms
lax
368ms
DNS 107ms TCP 1ms TLS 13ms TTFB 364ms
lhr
1190ms
DNS 14ms TCP 2ms TLS 15ms TTFB 1186ms
nrt
492ms
DNS 104ms TCP 1ms TLS 13ms TTFB 488ms
ord
246ms
DNS 89ms TCP 1ms TLS 6ms TTFB 243ms
sin
426ms
DNS 113ms TCP 1ms TLS 10ms TTFB 420ms
sjc
406ms
DNS 90ms TCP 3ms TLS 10ms TTFB 402ms

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

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 8 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