Is Firebase down?

No, Firebase is working normally. UptimeRobot monitors google.com around the clock from multiple global locations, and our latest checks show no confirmed issues.

You can see the current status and recent incident history at the top of this page. If you're still having trouble reaching google.com, the issue may be local to your connection, DNS, VPN, browser, or device.

UptimeRobot shows Firebase as operational right now, which means google.com is responding normally from our global monitoring locations.

If you're still having trouble accessing it, the issue may be local to your connection. Try switching browsers, devices, or networks, and check your DNS or VPN settings.

Try opening google.com from another browser, device, or network (e.g., mobile hotspot). You can also disable your VPN, clear DNS cache, restart your router, or check whether your internet provider is having issues. If the site works elsewhere, the problem is likely local rather than a confirmed Firebase outage.

We monitor google.com from our own infrastructure. When a check fails, we repeat the test from two other randomly chosen global locations to eliminate false positives. If these checks fail too, we mark Firebase as down.

A Firebase outage means our checks detected that google.com was not responding correctly after multiple checks from different global locations. This doesn't always mean every user is affected. Some outages are regional, some affect only certain features, and some appear as slow loading instead of a full failure.

Not exactly. UptimeRobot monitors google.com from the outside, so we can detect when something is wrong and show high-level symptoms such as connection timeouts, HTTP errors, or failed responses from specific regions.

However, we don't have visibility into internal systems, so we can't identify the exact root cause (like a failed deployment, database issue, or infrastructure problem).

What we can show you:

• When the issue started and when it was resolved
• How long the outage lasted
• Which regions were affected
• The type of error observed (for example, timeouts or HTTP status codes like 500 or 404)

For detailed root cause information and official updates, we recommend checking Firebase's official status page.

Yes, UptimeRobot lets you set up your own monitors for google.com so you get alerted the moment something goes wrong, and before your users notice. Our free plan includes 50 monitors with 5-minute check intervals. You'll also get details that this public status page doesn't show, such as response headers, response body, region-level results, and a full activity log.

Create a free UptimeRobot account and set up a monitor for google.com. You'll receive alerts via email, SMS, Slack, webhooks, and other integrations as soon as we detect an issue, and again when it's resolved. Because we monitor independently from Firebase's own infrastructure, you may be notified even before their official status page acknowledges the issue.

Alternatively, you can check whether Firebase offers notifications on its official status page.

Over the last 5 years, the average resolved outage for Firebase lasted 9d 12h. That average is the mean difference between created_at and resolved_at across 6 resolved incidents we track for this provider.