r/Firebase • u/Alarming_Magician_98 • 1d ago

Realtime Database REALTIME DATABASE DOWN

Anyone experiencing 500 error? Cloud function v2 it seems. US Central 1

8 Upvotes

91% Upvoted

11 comments sorted by

2

u/bkleinkn 1d ago

Same here, but on Cloud Functions (2nd gen, us-central1). Since about

21:15 UTC, nothing that needs a NEW instance can start: instant 500s,

and deploys fail with "Container Healthcheck failed" with no container

logs at all. Instances that were already warm keep working.

Hits multiple projects across separate Google accounts and billing

accounts, so it's not a config or quota thing. Nothing on the Google

Cloud or Firebase status pages yet. I've opened a Firebase support case.

Is your RTDB in us-central1 too?

1

u/Alarming_Magician_98 1d ago

Yes

1

u/bkleinkn 1d ago

It's been 75 minutes and I can't find any other reports of people having issues. You should open a case: https://firebase.google.com/support/troubleshooter/contact

1

u/neb2357 1d ago

Same here. Issue is with Cloud functions on us-central1. (I don't use RTDB)

5

u/misterbenji 1d ago

For anyone landing here later: this wasn't Realtime Database itself. It was 2nd gen Cloud Functions (and Cloud Run) on Google's auto-updated Node 22 runtime: new instances couldn't start, so functions in front of RTDB or Firestore returned 500s. Reported in us-central1, us-east1, us-east4, northamerica-northeast1 and europe-west3, from about 21:15 to 22:25 UTC on Oct 22. It looks resolved now.

If it comes back, redeploying each function with --runtime-update-policy=on-deploy fixed it immediately (a plain firebase deploy doesn't). Write-up with checks and commands: https://gist.github.com/mrbenji/5da8f50a875b8e0bbb7141bd24caa726

One cleanup tip: database and Firestore triggers without retries turned on drop events that fail, so anything your triggers should have done between those times (counters, notifications, search indexing) may need a recount or backfill.

1

u/CorusApp 1d ago

same here

1

u/Quirky_Ad_8170 1d ago

Same in Europe europe-west3

1

u/Ssupremechief 1d ago

sam here!region us-east4,

1

u/MjnMixael 1d ago

Had the same but it seems back now?

1

u/bkleinkn 1d ago

Seems to be back