Live Domain Check

Is Firebase Down? Check firebase.google.com Status and Outages

Run a live reachability check for firebase.google.com. Compare the regional responses with the problem you see in Firebase.

Find Firebase help and reporting links, specific checks, and step-by-step guidance below the live result.

Ready

Running automatic check…

Checking reachability from multiple regions.

Checked-

Verdict-

Response Time-

Final URL-

Regional checks8 regions

Rate:

No ratings yet.

Is Firebase working for you?

Share a quick update and see what other visitors are experiencing.

Loading community reports…

Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy

Understanding Firebase connection and service problems

Firebase availability depends on the product and project: Authentication, Hosting, Firestore and other services do not share every failure.

The checker above requests firebase.google.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Firebase action that failed. A homepage response alone cannot verify an account, app workflow or transaction.

For a deployment or console problem, compare the affected cloud entrypoint before changing your application: Google Cloud status check, Google Cloud Console status check. Compare results separately; these links do not establish a shared outage.

Looking for another service? Browse developer service checks.

Firebase official website and help

Firebase help and reporting

Choose the Firebase product and project; Google Workspace status is not its product dashboard.

Open firebase.google.com

Open the website in your browser and compare it with the result above.

Where to report problems with Firebase

Open Firebase help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.

Details to include in your report

Project ID, product, region, SDK version, error code and request time; do not publish keys or user records.

Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Firebase.

What to check when Firebase is not working

These are troubleshooting comparisons, not claims that Firebase is currently experiencing a particular incident.

Start with the action that failed

Identify the project, Firebase product and region where relevant; compare the corresponding status component.

Narrow down the affected service

Use a minimal read or sign-in test appropriate to that product and inspect its actual error rather than testing only firebase.google.com.

Read the actual checker response

A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.

How to check if Firebase is down

Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
Run the firebase.google.com check. Look at the regional results and when they were checked. Checking again may return a cached result.
Check for a service notice. Open Firebase help and use its guidance or announcements for the exact feature. Do not treat a general homepage as an outage bulletin.
Try another browser or network. Use the specific checks above to narrow down the problem. If it continues, send the error and time through the official help link.

If Firebase Is Not Working Only For You, Start Here

Use these local troubleshooting steps after the down-check workflow when Firebase seems broken only for you. This section focuses on app, browser, account, and network fixes.

1. Compare browser sessions

Open firebase.google.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.

2. Preserve a working account session

Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Firebase issue.

3. Try another network

If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.

4. Capture support-ready evidence

Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Firebase support.

Frequently asked questions about Firebase problems

Is Firebase down, or is the problem limited to one feature?

Run the firebase.google.com check and compare its original timestamps and responses with your actual error. Firebase availability depends on the product and project: Authentication, Hosting, Firestore and other services do not share every failure.

Where can I report a problem with Firebase?

Use the community buttons on this page to share whether the service works for you. For help from Firebase, use the official help/reporting resource linked above. Choose the Firebase product and project; Google Workspace status is not its product dashboard.

What should I check first when Firebase is not working?

Identify the project, Firebase product and region where relevant; compare the corresponding status component. Use a minimal read or sign-in test appropriate to that product and inspect its actual error rather than testing only firebase.google.com.

What information helps Firebase support investigate?