Service status & outage reports

Is Firebase down?

Check Firebase availability, incident history, downtime reports, and website performance.

https://firebase.google.com/ ↗
Provider reports service problems

The official provider feed identifies an active incident or affected component.

0 recorded outage reports · rolling 24 hours

Text version ↗

My watchlist

Estimated down reports for Firebase

Last 24 hours

There is not enough activity for a usable 24-hour estimate. Status and website measurements remain available below.

Last collection attempt: 2026-10-20 07:56:27 UTC · Insufficient activity.

No user-submitted outage reports in the last 24 hours.

Firebase outage history

2025–2026

Daily history over the past 12 months. Select a day for its evidence.

NovDecJanFebMarAprMayJunJulAugSepOct
GoodDown / service issuesNot enough data

Select a square for daily details. Scroll sideways to explore earlier months.

How to read this calendar

Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.

Firebase website uptime and response time

Website responded successfully HTTP 200. Last checked 2026-10-21 23:04:58 UTC.

Checked address: https://firebase.google.com/

DNS lookup: 4 ms · TCP connection: 5 ms · TLS handshake: 6 ms. Certificate expires 2026-12-21; trusted connection: yes.

100%
Successful website checks (24h)
123 successful / 123 measurable checks

308 ms
Median response time

623 ms
95th percentile response time

Successful website response times, 0 to 6140 milliseconds6140 ms0 ms2026-10-21T12:38:37.000Z: 493 ms2026-10-21T12:43:45.000Z: 373 ms2026-10-21T12:48:55.000Z: 324 ms2026-10-21T12:54:05.000Z: 813 ms2026-10-21T12:59:11.000Z: 298 ms2026-10-21T13:04:19.000Z: 350 ms2026-10-21T13:09:29.000Z: 436 ms2026-10-21T13:14:39.000Z: 230 ms2026-10-21T13:19:49.000Z: 268 ms2026-10-21T13:24:57.000Z: 376 ms2026-10-21T13:30:04.000Z: 195 ms2026-10-21T13:35:09.000Z: 663 ms2026-10-21T13:40:17.000Z: 377 ms2026-10-21T13:45:25.000Z: 341 ms2026-10-21T13:50:33.000Z: 263 ms2026-10-21T13:55:43.000Z: 249 ms2026-10-21T14:00:51.000Z: 406 ms2026-10-21T14:06:00.000Z: 399 ms2026-10-21T14:11:09.000Z: 255 ms2026-10-21T14:16:17.000Z: 341 ms2026-10-21T14:21:25.000Z: 280 ms2026-10-21T14:26:35.000Z: 233 ms2026-10-21T14:31:45.000Z: 235 ms2026-10-21T14:36:55.000Z: 459 ms2026-10-21T14:42:01.000Z: 207 ms2026-10-21T14:47:07.000Z: 206 ms2026-10-21T14:52:13.000Z: 214 ms2026-10-21T14:57:17.000Z: 237 ms2026-10-21T15:02:23.000Z: 450 ms2026-10-21T15:07:29.000Z: 420 ms2026-10-21T15:12:35.000Z: 372 ms2026-10-21T15:17:43.000Z: 303 ms2026-10-21T15:22:49.000Z: 229 ms2026-10-21T15:27:57.000Z: 235 ms2026-10-21T15:33:05.000Z: 243 ms2026-10-21T15:38:09.000Z: 300 ms2026-10-21T15:43:17.000Z: 404 ms2026-10-21T15:48:25.000Z: 206 ms2026-10-21T15:53:35.000Z: 340 ms2026-10-21T15:58:43.000Z: 327 ms2026-10-21T16:03:51.000Z: 234 ms2026-10-21T16:09:01.000Z: 341 ms2026-10-21T16:14:11.000Z: 185 ms2026-10-21T16:19:21.000Z: 302 ms2026-10-21T16:24:29.000Z: 415 ms2026-10-21T16:29:37.000Z: 344 ms2026-10-21T16:34:41.000Z: 228 ms2026-10-21T16:39:47.000Z: 281 ms2026-10-21T16:44:51.000Z: 254 ms2026-10-21T16:49:59.000Z: 271 ms2026-10-21T16:55:07.000Z: 453 ms2026-10-21T17:00:17.000Z: 6140 ms2026-10-21T17:05:27.000Z: 284 ms2026-10-21T17:10:36.000Z: 244 ms2026-10-21T17:15:45.000Z: 254 ms2026-10-21T17:20:55.000Z: 193 ms2026-10-21T17:26:05.000Z: 234 ms2026-10-21T17:31:11.000Z: 308 ms2026-10-21T17:36:21.000Z: 1722 ms2026-10-21T17:41:30.000Z: 623 ms2026-10-21T17:46:35.000Z: 347 ms2026-10-21T17:51:39.000Z: 509 ms2026-10-21T17:56:45.000Z: 262 ms2026-10-21T18:01:53.000Z: 423 ms2026-10-21T18:07:01.000Z: 454 ms2026-10-21T18:12:11.000Z: 226 ms2026-10-21T18:17:19.000Z: 507 ms2026-10-21T18:22:28.000Z: 325 ms2026-10-21T18:27:35.000Z: 296 ms2026-10-21T18:32:43.000Z: 205 ms2026-10-21T18:37:53.000Z: 321 ms2026-10-21T18:43:03.000Z: 264 ms2026-10-21T18:48:13.000Z: 277 ms2026-10-21T18:53:21.000Z: 240 ms2026-10-21T18:58:30.000Z: 392 ms2026-10-21T19:03:39.000Z: 509 ms2026-10-21T19:08:45.000Z: 584 ms2026-10-21T19:13:55.000Z: 291 ms2026-10-21T19:19:05.000Z: 2188 ms2026-10-21T19:24:15.000Z: 380 ms2026-10-21T19:29:23.000Z: 268 ms2026-10-21T19:34:31.000Z: 471 ms2026-10-21T19:39:41.000Z: 340 ms2026-10-21T19:44:49.000Z: 521 ms2026-10-21T19:49:58.000Z: 629 ms2026-10-21T19:55:07.000Z: 417 ms2026-10-21T20:00:17.000Z: 407 ms2026-10-21T20:05:25.000Z: 406 ms2026-10-21T20:10:33.000Z: 405 ms2026-10-21T20:15:43.000Z: 200 ms2026-10-21T20:20:51.000Z: 199 ms2026-10-21T20:26:00.000Z: 355 ms2026-10-21T20:31:09.000Z: 245 ms2026-10-21T20:36:18.000Z: 302 ms2026-10-21T20:41:27.000Z: 461 ms2026-10-21T20:46:35.000Z: 230 ms2026-10-21T20:51:45.000Z: 541 ms2026-10-21T20:56:53.000Z: 259 ms2026-10-21T21:02:01.000Z: 310 ms2026-10-21T21:07:09.000Z: 272 ms2026-10-21T21:12:17.000Z: 293 ms2026-10-21T21:17:25.000Z: 487 ms2026-10-21T21:22:33.000Z: 449 ms2026-10-21T21:27:43.000Z: 262 ms2026-10-21T21:32:53.000Z: 310 ms2026-10-21T21:37:59.000Z: 252 ms2026-10-21T21:43:03.000Z: 263 ms2026-10-21T21:48:09.000Z: 417 ms2026-10-21T21:53:13.000Z: 281 ms2026-10-21T21:58:19.000Z: 228 ms2026-10-21T22:03:23.000Z: 255 ms2026-10-21T22:08:29.000Z: 293 ms2026-10-21T22:13:33.000Z: 317 ms2026-10-21T22:18:39.000Z: 573 ms2026-10-21T22:23:43.000Z: 263 ms2026-10-21T22:28:53.000Z: 374 ms2026-10-21T22:33:59.000Z: 210 ms2026-10-21T22:39:09.000Z: 253 ms2026-10-21T22:44:19.000Z: 272 ms2026-10-21T22:49:29.000Z: 600 ms2026-10-21T22:54:39.000Z: 222 ms2026-10-21T22:59:49.000Z: 515 ms2026-10-21T23:04:58.000Z: 332 ms

0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.

Evidence behind the status

Provider reports service problems. The official provider feed identifies an active incident or affected component.

Website checks and estimated activity have independent update times. Refer to each section for its latest observation.

These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.

Official component status

Firebase official status · fetched 2026-10-21 23:00:10 UTC

13 mapped components · 1 reporting problems
ComponentProvider status
Realtime Databasedegraded performance
Test Laboperational
Hostingoperational
App Hostingoperational
Crashlyticsoperational
Performance Monitoringoperational
Cloud Messagingoperational
App Distributionoperational
A/B Testing (Beta)operational
AI Logicoperational
Studio (Preview)operational
Remote Configoperational
SQL Connectoperational

Official incident timeline

Partial performance degradation for RTDB users in us-central1 · investigating · 2026-10-21T14:39:25+00:00

Product match: components.

Read the provider’s incident report

  1. ·

    Users may be experiencing intermittent 500's and elevated latencies.

Firebase Hosting projects presenting intermittent "Bandwidth Quota Exceeded" errors or failing deployments with quota errors. · resolved · 2026-10-09T21:44:22+00:00

Product match: components.

Read the provider’s incident report

  1. ·

    The issue has been resolved.

  2. ·

    A rollback has completed that should mitigate the bandwidth quota errors. Deployments that are failing due to quota may still be impacted as the rollback for that service continues. Ensuring the API is enabled is still a mitigation for more immediate resolution.

  3. ·

    We are investigating an issue with Firebase Hosting where projects—including those on the Blaze plan—may intermittently serve HTTP 509 "Bandwidth Quota Exceeded" errors or fail deployments with HTTP 429 quota errors. Workaround / Immediate Mitigation: Affected customers can mitigate the issue immediately by ensuring that the Firebase Hosting API is enabled for their project in Google Cloud Console: https://console.cloud.google.com/apis/library/firebasehosting.googleapis.com?project=_ Our enginee

Firebase Test Lab is experiencing availability issues with ARM emulator devices. · resolved · 2026-09-23T00:04:58+00:00

Product match: components.

Read the provider’s incident report

  1. ·

    ARM emulator availability issues have been mitigated and full traffic capacity has been restored.

  2. ·

    Firebase Test Lab is experiencing availability issues with ARM emulator devices.

Firebase App Hosting experiencing issues actuating Cloud Run · resolved · 2026-09-22T05:17:13+00:00

Product match: components.

Read the provider’s incident report

  1. ·

    Firebase App Hosting's actuations of Cloud Run have been restored and builds should be working as expected now.

  2. ·

    Firebase App Hosting is having issues actuating Run. Services that are already running should be unaffected, but new builds or rollouts may be having issues.

Firebase Hosting dataplane connectivity is in some regions. · resolved · 2026-09-22T16:26:59+00:00

Product match: components.

Read the provider’s incident report

  1. ·

    The connectivity issues seem to be resolved and we are seeing requests complete from those regions once again. We will continue to monitor but believe the situation has recovered.

  2. ·

    Firebase Hosting has received report of sites being unavailable in some regions.

Firebase Test Lab is experiencing availability issues with ARM emulator devices. · resolved · 2026-09-21T23:49:04+00:00

Product match: components.

Read the provider’s incident report

  1. ·

    We are rolling out a new server update to mitigate the issue.

  2. ·

    We are experiencing high test latencies for ARM tests due to reduced capacity and high demand.

Crashlytics and Performance Monitoring consoles experiencing low availability. · resolved · 2026-09-16T20:36:42+00:00

Product match: components.

Read the provider’s incident report

  1. ·

    Disruption is resolved at 13:30 PDT

  2. ·

    Starting at 2PM ET, Crashlytics and Performance Monitoring console started experiencing low availability. We are working to remediate ASAP.

Firebase Test Lab is experiencing execution delay on ARM based virtual devices. We are currently investigating the cause. · resolved · 2026-09-11T00:16:34+00:00

Product match: components.

Read the provider’s incident report

  1. ·

    Firebase Test Lab is experiencing execution delay on ARM based virtual devices. We are currently investigating the cause.

Recovery tracker

The provider still reports an active problem.

6 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.

Slowdown detection

No sustained slowdown has been established against the earlier baseline.

Recent median: 332 ms · Earlier median: 308 ms. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.

Emerging down-report signals

  • is firebase down

Query “firebase” · observed 2026-10-21 22:55:40 UTC · 0 newly observed problem phrases.

Query “is firebase” · observed 2026-10-21 22:55:40 UTC · 0 newly observed problem phrases.

Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.

Is it down in your region?

Run one public website check from a community probe. Results describe that probe, not every user in a country.

Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.

Infrastructure incident context

Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of Firebase.

GitHub official status · 2026-10-21 23:04:12 UTC

No active incidents recorded.

About Firebase status on Iszdown

Check Firebase availability, incident history, downtime reports, and website performance.

This page combines the available Firebase report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.

13 product-matched official components are listed above. Latest public website measurement: 2026-10-21T23:04:58.000Z.

Visit the official Firebase website · Official provider status · How it works

What to check when Firebase is not working

These are troubleshooting suggestions, not a list of currently reported problems.

Firebase will not open

Compare your usual browser or app with a private browser window, then try another network if available. Save unsent work first. A difference between networks can help separate a local connection problem from a wider disruption.

Firebase is slow or only one feature fails

Record the affected action, exact error, and time. Compare the website response measurements with any official component incidents; loading a homepage does not test every feature.

Website troubleshooting guide · Sign-in problems · API errors and timeouts

Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.

Recent Firebase outage history

Latest available product-matched official incidents in the calendar’s archive. Times below use UTC. Duration is the provider’s recorded incident window, not a measurement of impact on every user.

Frequently asked questions about Firebase

Is Firebase down right now?

Provider reports service problems. The official provider feed identifies an active incident or affected component. This page was assembled at 2026-10-21T23:05:41.000Z.

How many Firebase outage reports are there today?

The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-20T23:00:00.000Z to 2026-10-21T23:00:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.

Why does Firebase show operational when it is not working for me?

An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Firebase feature.

When was Firebase status last updated?

The latest status observation was 2026-10-21T23:00:10.000Z. Only matched product components and incidents are shown. The assessment is recent.

Has Firebase had outages before?

The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.

How do I follow Firebase or report a problem?

Use “Watch this service” to save Firebase in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.

Related services to Firebase

Check a related product separately; its status can differ from Firebase.

Firebase