Firebase status: is it down right now?
Our own check of firebase.google.com from Europe and the US, every 3 minutes, with recent history.
firebase.google.com responded. The page answered normally in 449 ms.
firebase.google.com responded.
The page answered normally in 449 ms.
Checked (1 minute ago) from Europe and the US, automatic every 3 minutes.
Run a website? Hear about it before your visitors do.
Firebase is up right now. Visual Sentinel watches your own site the same way and alerts you when a check fails or the page looks broken. Add your address and we'll check it now. No account needed.
This checks the response from firebase.google.com. It does not test playback, login or every Firebase feature.
Firebase status history
Our own checks from Europe and the US. Green means every check passed, amber means some checks failed, red means most checks in that period failed.
Outages our checks detected
None since Oct 13. A problem has to fail two checks in a row before we record it.
Watch your own site
This page is for their outage. Your own site can fail the same way. See its first check free, then try a paid plan for 7 days (card required).
Monitor my siteabout this service
About Firebase
Firebase is Google's app-development platform covering Authentication, Firestore (NoSQL document DB), Realtime Database (older NoSQL DB), Cloud Functions for Firebase, Firebase Hosting, Storage, Remote Config, Analytics, Crashlytics, and Cloud Messaging (FCM) for push notifications. Firebase sits inside Google Cloud but has its own dedicated status page. Outages typically affect Authentication (sign-in fails, blocking every app that uses Firebase Auth), Firestore reads/writes, FCM push delivery, or Hosting. Mobile apps built on Firebase are hit hardest because almost every feature path touches Firebase in some way.
The official Firebase status page is available as a reference. Official pages are useful, but they can lag behind real outages by minutes or hours.
outage patterns
How Firebase outages affect production workloads
Developer-platform outages have outsized impact because they cascade. When Firebase is degraded, every customer's build pipeline, deploy hook, or webhook delivery can stall, and the failure mode often looks like a customer problem before engineers realize the dependency is the cause. CI runs hang, status checks never report, and queued jobs pile up silently.
The live check above provides independent public-endpoint evidence from EU and US, including status and response timing. That helps separate a broad reachability problem from a local client issue, but it does not execute your private API call, build, webhook, or deploy. Test the exact dependency path before attributing the incident to Firebase.
Common signs Firebase is having issues
- API rate limits returning earlier than the documented thresholds
- Webhook deliveries showing 5xx errors or unusual latency tail
- Deploy or build hooks accepted by Firebase but never firing downstream
- OAuth or token endpoints failing intermittently for the same client credentials
What to do when Firebase is degraded
When Firebase is having trouble, the fastest mitigation is usually feature-flagging the dependency off if your application can degrade gracefully. Check the multi-region results on this page first; if both regions report healthy but your application still sees failures, the issue is likely your network path or DNS, not Firebase itself.
monitor 24/7
Monitor Firebase automatically.
Get independent uptime alerts when the public Firebase endpoint fails a confirmed check. Solo and Starter check every 5 minutes; Business and Agency check every 60 seconds.
5-minute checks from Solo
Business and Agency support 60-second uptime checks.
Multi-region
EU & US checks. Catch regional outages.
Alerts where you work
Email and push on every plan, plus team and incident channels by plan.
free first check · 7-day trial, card required · from $15/month
why independent monitoring
Provider status references
and endpoint checks answer different questions.
Independent endpoint evidence
The regional check can show that a public endpoint is failing before or after a provider posts broader incident context. It does not validate every product subsystem.
Scheduled alerts
Monitor Firebase on your plan interval and route confirmed endpoint failures through the notification channels available to your workspace.
Multi-region verification
EU and US results can reveal a regional difference in public-endpoint reachability. Confirm the exact workflow and provider region you use.
Historical data
Track Firebase uptime over time. See trends, identify recurring issues, and make informed decisions about your dependency.
Frequently asked questions
Is Firebase down right now?
See the latest check of firebase.google.com and its timestamp at the top of this page. If Firebase is down, you can also check the official status page for extra context.
How do I check if Firebase is having issues?
This page checks the public Firebase endpoint from EU and US. You can also monitor that endpoint on a schedule and receive confirmed-failure alerts through the channels available on your plan. Test the exact provider feature you use for a complete diagnosis.
How can I get alerted when Firebase goes down?
Add firebase.google.com to Visual Sentinel and its first check is free. To keep monitoring, start a 7-day trial (card required) or subscribe now: Solo and Starter check every 5 minutes, Business and Agency every 60 seconds, with email, push and chat alerts.
Where can I find Firebase outage context?
The official Firebase status page is available as a reference. Official pages are useful, but they can lag behind real outages by minutes or hours. Visual Sentinel checks the public Firebase endpoint independently from EU and US. Paid Business and Agency plans support 60-second uptime checks.
Why do my Firebase Auth sign-ins fail even though Firestore works?
Firebase Auth and Firestore are independent services. Auth handles identity, Firestore handles document storage. An Auth-only outage blocks new sign-ins and token refreshes, but Firestore reads and writes with cached auth tokens continue until tokens expire.
Does a Firebase Cloud Messaging outage lose push notifications?
FCM queues push messages for a short retry window if the receiving device is unreachable. During full FCM outages, queued messages may be dropped depending on their time-to-live setting. Critical notifications should set a longer TTL to survive brief outages.
Often checked together with Firebase
Development tools depend on each other. A failing build or editor plugin is not always the tool you opened.