Is Google Cloud Google Kubernetes Engine Down?
Google Cloud Google Kubernetes Engine Status is Minor Outage
The easiest way to monitor all your external providers
IsDown is a status page aggregator & outage monitoring tool for all your business-critical dependencies. Get a custom dashboard with all your external services. Instant notifications on outages. All in one place.
Alerts in
No credit card required · 1762 services available · Check out Live Demo
Latest Google Cloud Google Kubernetes Engine Outages
Check the stats and details of the latest Google Cloud Google Kubernetes Engine outages and issues
Resolved Minor Global: Calico enabled GKE clusters’ pods may get stuck terminating after upgrading to 1.22+
Summary: Global: Calico enabled GKE clusters’ pods may get stuck terminating after upgrading to 1.22+ Description: GKE clusters running versions 1.22 or later and that use Calico Network Policy might experience issues with terminating Pods under some conditions. Our engineering team continues to investigate the issue and are qualifying a potential mitigation for release to the Rapid channel 1.24. After all the qualifications are done, we will expedite the backport of the fix to 1.22 as soon as possible. We will provide an update by Friday, 2022-09-16 15:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: The Calico CNI plugin will show the following error terminating Pods: “Warning FailedKillPod 36m (x389 over 121m) kubelet error killing pod: failed to "KillPodSandbox" for "af9ab8f9-d6d6-4828-9b8c-a58441dd1f86" with KillPodSandboxError: "rpc error: code = Unknown desc = networkPlugin cni failed to teardown pod "myclient-pod-6474c769...
Resolved Minor Global: Calico enabled GKE clusters’ pods may get stuck Terminating or Pending after upgrading to 1.22+
Summary: Global: Calico enabled GKE clusters’ pods may get stuck terminating after upgrading to 1.22+ Description: GKE clusters running versions 1.22 or later and that use Calico Network Policy might experience issues with terminating Pods under some conditions. Our engineering team continues to investigate the issue and are qualifying a potential mitigation for release to the Rapid channel 1.24. After all the qualifications are done, we will expedite the backport of the fix to 1.22 as soon as possible. We will provide an update by Friday, 2022-09-16 15:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: The Calico CNI plugin will show the following error terminating Pods: “Warning FailedKillPod 36m (x389 over 121m) kubelet error killing pod: failed to "KillPodSandbox" for "af9ab8f9-d6d6-4828-9b8c-a58441dd1f86" with KillPodSandboxError: "rpc error: code = Unknown desc = networkPlugin cni failed to teardown pod "myclient-pod-6474c769...
Resolved Minor GKE cluster control planes unavailable in us-central1-a
Summary: GKE cluster control planes unavailable in us-central1-a Description: We've received a report of an issue with Google Kubernetes Engine as of Monday, 2022-08-01 18:26 US/Pacific. We will provide more information by Monday, 2022-08-01 20:00 US/Pacific. Location: us-central1-a Diagnosis: Multiple clusters in us-central1-a have an issue accessing Kubernetes control planes. Users may face issues while performing operations like administering cluster, modify workloads etc. Workaround: None at this time.
Resolved Minor us-central1-c: GKE experiencing issues with some cluster and nodepool operations.
Summary: us-central1-c: GKE experiencing issues with some cluster and nodepool operations. Description: We are experiencing an issue with Google Kubernetes Engine beginning at Wednesday, 2021-10-20 08:30 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2021-10-20 09:42 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: The following operations may fail with 500/503 errors: create-cluster, delete-cluster, create-nodepool, delete-nodepool, and node-pool resizes Workaround: The failed operations may succeed on retrying them
Resolved Minor us-central1-c: GKE experiencing issues with some cluster and nodepool operations. Mitigation underway.
Summary: us-central1-c: Create / Delete Cluster and NodePool operations failing Description: We are experiencing an issue with Google Kubernetes Engine beginning at Tuesday, 2021-10-19 11:40 US/Pacific. Our engineering team continues to investigate the issue. We will provide an update by Tuesday, 2021-10-19 14:35 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: create-cluster, delete-cluster, create-nodepool, and delete-nodepool, node-pool resizes operations are failing with 500 and 503 errors. Workaround: The failed operations may succeed on retrying them
Google Cloud Alternatives
The easiest way to monitor all your external providers
IsDown is a status page aggregator & outage monitoring tool for all your business-critical dependencies. Get a custom dashboard with all your external services. Instant notifications on outages. All in one place.
Alerts in
No credit card required · 1762 services available · Check out Live Demo
"If you are in SRE, IT, or Security and work in an environment with a lot of SaaS (which, let's face it, is all of them) - IsDown is your new best friend. Helpfully aggregates various Statuspages from services into a very clear dashboard. Worth every penny."
Mike, Head of Security
Monitor outages where you already do the work
How can we help?
It has never been easier to understand the outages in your external cloud services.
Birds-eye view over all your services statuses
Check the status page aggregated of all your services in one place. No more going to each of the status pages and managing them individually.
Outage monitoring in real time
We monitor 24 hours a day, 7 days a week and will notify you if there is an incident. No more wasting time trying to figure out why something isn't working.
Alerts in your favorite channels
Get instant notifications in your email, Slack, Teams, or Discord when we detect a service outage. Outage monitoring where you are already doing your work.
Avoid notifications clutter
Configure which notifications you want to receive from each service. Filter notifications by service components. You can opt to receive notifications only when a specific component is affected. You can also choose to receive notifications with a certain severity.
Easily integrate with your current tools and workflows
Using Zapier or Webhooks, you can easily integrate notifications into your processes. PagerDuty integration is also available.
Dedicated dashboard for each team's services
Create one dashboard for each of your teams. Monitor only the services that each teams uses. Dedicated dashboard with custom notification settings.
Prepare for scheduled maintenances
Never again be caught off guard by unexpected maintenance from your services. A feed of the next scheduled maintenances is available.
Weekly Digest of the services' outages
Every Monday, you'll receive a weekly summary of what happened the previous week as well as the maintenance schedule for the following week.
Each team with their own
dashboard and notifications
IT Support
You already monitor your internal systems. What about the external services? Monitor the services your business depends on. Don't waste time looking elsewhere when external outages are the cause of issues.
Customer Service
Detect external outages before your clients tell you. Anticipate possible issues and make the necessary arrangements. Having proactive communication builds trust over clients and prevents more work.
5 minutes to set up, hours saved not looking elsewhere
-
Step 1 Create an account
Start with a trial account that will allow you to try and monitor up to 40 services for 14 days.
-
Step 2 Select your services
There are 1762 services to choose from, and we're adding more every week.
-
Step 3 Set up notifications
You can get notifications by email, Slack, and Discord. You can also use Zapier or Webhooks to build your workflows.
-
Step 4 Done!
You'll start getting alerts when we detect outages in your external dependencies! No more wasting time looking in the wrong place!
Frequently Asked Questions
- Is Google Cloud Google Kubernetes Engine down today?
- Google Cloud seems to be having problems. You can check the incident details on the top of the page.
- I'm having issues with Google Cloud, but the status is OK. What's going on?
-
There are a few things you can try:
- Check the official status page for more information.
- Check the Twitter account for more information.
- How can I be notified when Google Cloud is having issues?
- You can subscribe for updates on the official status page or create an account in IsDown. We will send you a notification in real-time when Google Cloud has issues.
- Why use IsDown?
- IsDown is a status page aggregator, which means that we aggregate the status of multiple cloud services. Monitor all the services that impact your business. Get a dashboard with the health of all services and status updates. Set up notifications via email, Slack, or Discord when a service you monitor has issues or when maintenances are scheduled.
- What happens when I create an account?
- You'll have access to a 14-day trial in our Pro plan. You can cancel or delete your account anytime. After 14 days, you'll need to subscribe to continue to use the service and get notifications.
- How can I pay for a subscription?
- You can go to the Billing section in your account and choose one of the plans. We have monthly and yearly options. We accept all major credit cards, Apple Pay, and Google Play. We use Stripe for payments.
- Can I get a refund?
- We'll refund your subscription if you cancel it until ten days after the subscription has started. No questions asked.
- Can't find a service/integration?
- Just contact us, and we'll add it ASAP.
Latest Articles
Easily monitor all your services providers
Increase the productivity and efficiency of your team. Enable monitoring for your services, and start receiving real-time alerts when your external dependencies have outages.
Start today for FREE