Google Cloud not working? Live outage status & reports

No reports in the last 24 hours.

Google Cloud current status

No recent reports

0 reports in the last 24 hours.

This does not confirm that Google Cloud is working.

Official website check: cloud.google.com is reachable (HTTP 200) · 513 ms · measured (18 minutes ago) This does not confirm the app or sign-in.

Status calculated automatically from user reports (unofficial) — How it works? · Checked at

Having problems?

contact Support: Google Cloud Support

Official status Google Cloud Service Health Google Cloud services by product and region, including the Google Cloud Console and the Google Cloud Android and iOS apps. Google Security Products and Looker (original) have their own status pages.

📈 24h trend

0 reports

Hours in UTC

01-45-910+

🗺️ Where Google Cloud is having problems

live

0 reports (24h)

No reports1–19 reports20–49 reports50+ reports

No active reports right now.

Google Cloud is down or won't load

Official toolCheck whether Google Cloud is down

Scope: Google Cloud services, worldwide

Open Google Cloud's official status dashboard. It shows whether your product has an incident in your region.

  1. Open Google Cloud Service Health.
  2. Find your product in the list. The list includes Google Cloud Console, Google Cloud Android App and Google Cloud iOS App.
  3. Use the region tabs to check the status where your resources run. The tabs are Americas, Europe, Asia Pacific, Middle East, Africa and Multi-regions.
  4. Read all times on the dashboard as US/Pacific time.

Your product shows an update under Non-regional

When: The update is in the Non-regional column

What it means: The issue affects that specific service, which is deployed globally. It is not a platform-wide disruption affecting all regions.

You use Google Security Products or Looker (original)

When: Your product is a Google Security Product or Looker (original)

  1. For Google Security Products, check status.cloud.google.com/security.
  2. For Looker (original), check status.cloud.google.com/looker.

You want to see incidents for your own projects

When: You need details for your Google Cloud projects

  1. Use Personalized Service Health (cloud.google.com/service-health/docs/overview). It shows incidents affecting your Google Cloud projects, including custom alerts, API data and logs.

If that does not work: Open Personalized Service Health from Google Cloud Support.

Did this fix it?

Scope: Google Cloud console in a web browser

Reload the page first. If the console still fails, check for an incident, then check your browser and network.

  1. Wait 15–30 seconds, then refresh the page. A brief network glitch or backend timeout can cause a temporary failure.
  2. If the page is still unavailable, use the gcloud CLI to inspect and manage your resources. The case “Keep working while the console is unavailable” below gives example commands.
  3. Check whether the affected service has an active incident on Google Cloud Service Health.
  4. If no incident is active, test in a private browsing window and check your permissions and policies. The cases below explain both checks.
  5. If the problem persists, create a support case and include the exact Tracking Number or Request ID shown in the error.

The page keeps spinning or stays blank

When: A page or card keeps spinning without showing data, or the window stays blank

What it means: This is typically caused by one of four things: a browser extension, corrupt cached site data, several signed-in accounts or blocked network requests.

  1. Open a private browsing window, such as an Incognito window in Google Chrome.
  2. Sign in to the Google Cloud console and go to the affected page.
  3. If the page loads there, one of your browser extensions is blocking the console. Turn your extensions off one by one in your usual profile to find it. Alternatively, set the extension to allow the domains listed in Allow access to Google Cloud console domains.
  4. Before you clear site data, make sure you know your Google Account password and have your 2-Step Verification method at hand: clearing cookies signs you out of the console and other Google sites in this browser. Then clear your browser cache and site data. Stale JavaScript bundles or corrupt cookies can stop the console from loading resources.
  5. Check that your browser is up to date and allows cookies for accounts.google.com and console.cloud.google.com.
  6. If the issue persists, test in another supported browser.

If that does not work: Open your browser's developer tools and note any script or network errors. If the errors persist, create a support case that includes them.

You are on a corporate network

When: You connect through a company web proxy, firewall or cloud access security broker

What it means: These network appliances can intercept or block the HTTPS traffic the Google Cloud console needs. Do these checks with your network administrator.

  1. Make sure your firewall and proxy allow traffic to all domains listed in Allow access to Google Cloud console domains.
  2. If the proxy performs SSL/TLS inspection, two things must hold. Its intermediate certificates must be trusted by your operating system and browser. WebSocket connections and streaming HTTP responses must not be cut off early.
  3. Try the console from an unrestricted network, such as a mobile hotspot or home network. This shows whether the failure is specific to your corporate network.

Keep working while the console is unavailable

When: You need to manage your resources now

  1. Use the gcloud CLI command that matches the console view you need. For example, gcloud compute instances list shows Compute Engine VM instances, and gcloud storage buckets list shows Cloud Storage buckets.
  2. To install and use the gcloud CLI, see Google Cloud CLI documentation.

If that does not work: If the console still fails after these checks, create a support case from Support > Cases. Include all of the following: the Tracking Number or Request ID; the full page URL and the project ID; the exact date, time and time zone (ISO 8601 or UTC); your browser name and version and your operating system; whether the issue happens in private browsing; and whether the equivalent gcloud CLI commands work.

Did this fix it?

Access, signup and support

Scope: Google Cloud console, signed in with a Google Account

Check which Google Account is active. Signing in to several accounts in one browser window can cause sign-in loops and permission errors on shared links. It can also open the console under the wrong account.

  1. In the Google Cloud console, click your avatar in the upper-right corner. Check that the active account is the email address that holds your IAM permissions.
  2. Watch for bookmarks and shared links. If one opens under a different signed-in account from the one with your IAM permissions, access to the console fails.
  3. Use separate browser profiles, such as Google Chrome profiles, for your work and personal accounts. Do not sign in to several accounts in the same profile window.

The right account is active but pages still fail

When: Console pages fail or stop responding, but gcloud CLI commands work for the same user and project

What it means: The console loads project metadata, enabled API status and aggregated views, so it can need more access than a single command. Check the following with your administrator.

  1. Ask whether your account needs the resourcemanager.projects.get permission (included in the Browser role, roles/browser) or the serviceusage.services.list permission. Narrow roles can work for one CLI command but lack the permissions to show project pages.
  2. Check whether Context-Aware Access bindings based on your device or IP address are blocking the console.
  3. Check whether VPC Service Controls perimeters are blocking the extra API calls that console views make.
  4. If your workloads use Assured Workloads data residency controls, use the regional console address, such as console.eu.cloud.google.com or console.us.cloud.google.com.

If that does not work: If pages still fail or show errors, create a support case from Support > Cases.

Did this fix it?

Scope: New Google Cloud account signup

Check your payment details, any unpaid balances and your browser, then try signing up again.

  1. Check that the billing address, name and contact details you entered match exactly what your card issuer or bank has on file.
  2. Use a valid payment method, such as a standard credit or debit card. Prepaid cards, virtual cards and certain unverified business cards may not be accepted.
  3. Make sure your card supports international transactions and automatic recurring payments.
  4. Clear any unpaid balance on an existing Google Cloud account or other Google Account. You must do this before you create a new billing account.
  5. Turn off any VPN, proxy or anonymizer service.
  6. Try signing up in an Incognito or private browsing window. Alternatively, temporarily turn off browser extensions such as ad-blockers.
  7. Try signing up again.

If that does not work: If you still can't complete signup, contact Cloud Customer Care through the Account suspension inquiry form.

Did this fix it?

Scope: Google Cloud organizations and projects

Create a support case in the Google Cloud console. Live chat is your quickest way to reach a support representative.

  1. Make sure you have the Tech Support Editor role (roles/cloudsupport.techSupportEditor) on the project, folder or organization. If you don't, ask your administrator to grant it.
  2. Go to Support > Cases in the Google Cloud console.
  3. Review the known issues (Known issues tab) and make sure a case has not already been filed.
  4. Use the resource selector on the console toolbar to choose your organization or project. Cases can only be created for organizations or projects.
  5. Click Get help.
  6. In the Select your product list, select your product.
  7. In the Describe your issue field, describe your issue.
  8. In the Observed error message field, enter any error message details.
  9. Select a priority and click Next. P1 means critical impact: the service is unusable in production.
  10. Look through the suggested resources. If you still need help, click Next.
  11. In the Select a category list, select the sub-category that best describes your issue.
  12. Choose Live chat or Email. Live chat is available only in English. With email, you can choose another supported language.
  13. Answer the remaining questions in as much detail as you can. With email, you can also attach screenshots and log files.
  14. Click Start chat if you chose live chat, or Submit if you chose email.

You have a billing or payment question

When: Your question is about Cloud Billing, including if you have no paid support package

What it means: All users can contact Customer Care about Cloud Billing. The free Basic Support package, provided to all Google Cloud customers, includes billing and payments support.

  1. Go to Support > Overview in the Google Cloud console.
  2. Use the resource selector on the console toolbar to choose your project.
  3. In the navigation menu, select Billing support for a live chat, or Phone support to get a phone number to call in supported languages.
  4. Or use the Billing Support Requests form. A support representative replies by email.

Gemini Cloud Assist is set up for your project

When: Your administrator has set up Gemini Cloud Assist for your folder or project

  1. Go to Support > Cases.
  2. Use the resource selector on the console toolbar to choose your folder or project.
  3. Click Create case with Gemini.
  4. In the Cloud Assist panel, describe your issue or ask your question in the Enter a prompt field.
  5. With a support package, you can ask for a support case at any point. With Premium Support, you can also click Contact support team.

Your case was closed but the problem is back

When: The case was closed in the last 15 days

What it means: You can reopen a case only within 15 days of its closure. After 15 days, create a new support case instead.

  1. Go to Support > Cases.
  2. Use the resource selector on the console toolbar to choose the organization or project of the case.
  3. Click the name of the case.
  4. Click Reopen case.
  5. Enter a reason for reopening the case.
  6. Click Reopen to confirm.
  7. If the case needs urgent attention, set its priority to P1.

You need to escalate a case

When: You have Enhanced or Premium support and the support process is not working as you expected

What it means: Escalation is meant for flagging process breaks. For a high-impact issue, escalating doesn't generally make the case faster; setting the right priority is the better option.

  1. In the Google Cloud console, open your support case and click Escalate. Quote the case number and give your reason.
  2. Or open the case in the Google Cloud Support Portal and click Escalate case. This button appears 30 minutes after the case is created.
Did this fix it?

About

Google Cloud is Google's set of cloud services, such as Google Compute Engine, Google BigQuery and Google Cloud Storage. You manage them in the Google Cloud console or with the gcloud CLI.

Still not working? Report it

If none of the help above fixed it, tell others: your report helps them see that Google Cloud is having a problem.

User comments

No comments yet. Be the first!

Share your experience with Google Cloud

Leave a comment on Google Cloud

0/1000

Comments are published right away if they pass an automatic filter (insults, links and spam are hidden). Report illegal content.

Where this status comes from

  • The verdict comes from user reports, counted above a small threshold. The check of the official website (cloud.google.com) is shown for information and does not change the verdict. An incident announced on the official status page can mark an outage as confirmed.
  • Google Cloud's own status page →

Contact options

Google Cloud Customer Care

Billing and signup help

Still having trouble with Google Cloud? Add your report: it helps others see whether it is down.