Skip to main content
Bubble

Log ingestion degraded

Degraded Lasted 0m · started · Bubble's page

Level
confirmed
Worst impact
Degraded
Down Index
8of 100

What to do

  • Check whether your product depends on Bubble. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

    Anything that failed between 2026-07-23 01:35 UTC and 2026-07-23 01:24 UTC may need a replay.
  • Subscribe to Bubble's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=bubble works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Bubble 2

  1. identified

    Log ingestion is degraded, due to an outage in our log provider. We are working with them to get this fixed as soon as possible. [https://status.observeinc.com/](https://status.observeinc.com/ "https://status.observeinc.com/")

    provider

  2. resolved

    Log ingestion is stable.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-bccedfd817

Is Bubble still down?

No, this incident was resolved 2026-07-23 01:24 UTC. For Bubble's live state, see https://down.guide/bubble.

How long did it last?

0m, from 2026-07-23 01:35 UTC to 2026-07-23 01:24 UTC, by the times Bubble posted.

What caused it?

Bubble hasn't published a root cause. If it does, it shows here.

Where does this come from?

Bubble's official status page, https://status.bubble.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.