Is Google Cloud Secret Manager down?
Current Google Cloud Secret Manager status is UP

We checked the official Google Cloud Secret Manager Status Page 47 sec. ago. Learn more
Having a problem? Help Allie Gator keep this page accurate!

Report an Issue

Stay informed of future downtime with dashboards and notifications

Recent Google Cloud Secret Manager Outages and Issues

Follow the recent outages and downtime for Google Cloud Secret Manager in the table below.

Start Time

Type

Length

Message

Details

November 09, 2023 01:30 UTC

WARN

less than a minute

Google Kubernetes Engine customers with Workload Identity enabled may see high application logging rate

See more
Start Time

November 09, 2023 01:30 UTC

Type WARN
Affected Components

Europe (regions) - Cloud Run

Asia Pacific (regions) - Cloud Run

Europe (regions) - Google App Engine

Asia Pacific (regions) - Google App Engine

Europe (regions) - Google Cloud Functions

Asia Pacific (regions) - Google Cloud Functions

Europe (regions) - Secret Manager

Asia Pacific (regions) - Secret Manager

europe-west1 - Cloud Run

europe-west1 - Google App Engine

europe-west1 - Google Cloud Functions

australia-southeast1 - Cloud Run

australia-southeast1 - Google App Engine

australia-southeast1 - Google Cloud Functions

australia-southeast1 - Secret Manager

europe-west1 - Secret Manager

Message

Google Kubernetes Engine customers with Workload Identity enabled may see high application logging rate

Details

Summary: Google Kubernetes Engine customers with Workload Identity enabled may see high application logging rate
Description: There is no impact to cluster functionality or performance. The only impact is extra logs in Cloud Logging.
gke-metadata-server is a GKE-managed system workload that is part of the GKE Workload Identity feature. Versions 0.4.272 to 0.4.280 of gke-metadata-server contain an incorrect configuration that results in a high rate of debug logs that contain the string "Unable to sync sandbox". These logs are then ingested into Cloud Logging, consuming Cloud Logging ingestion quota, and causing excess billable usage when exceeding the free monthly allotment.
A rollout containing a fix to no longer ingest the excess logs to Cloud Logging is about 25% complete.
We will provide an update by Friday, 2023-11-10 14:00 US/Pacific.
Diagnosis: Customers can determine whether their cluster is impacted by inspecting the gke-metadata-server daemonset with kubectl get daemonset -n kube-system -l k8s-app=gke-metadata-server -o yaml and looking at the components.gke.io/component-version annotation in .spec.template.metadata.annotations. If the value is a version between 0.4.272 and 0.4.280 (inclusive), then the cluster is currently affected.
Workaround:
- Customers using GKE Rapid Channel can upgrade their cluster control plane to 1.28.2-gke.1157000 and above, or 1.27.7-gke.1038000 and above.
- Customers on GKE Regular Channel, GKE Stable Channel, or who are not using release channels do not have a workaround at this time.

November 09, 2023 01:30 UTC

WARN

ongoing

Google Kubernetes Engine customers with Workload Identity enabled may see high application logging rate

See more
Start Time

November 09, 2023 01:30 UTC

Type WARN
Affected Components

Europe (regions) - Cloud Run

Asia Pacific (regions) - Cloud Run

Europe (regions) - Google App Engine

Asia Pacific (regions) - Google App Engine

Europe (regions) - Google Cloud Functions

Asia Pacific (regions) - Google Cloud Functions

Europe (regions) - Secret Manager

Asia Pacific (regions) - Secret Manager

europe-west1 - Cloud Run

europe-west1 - Google App Engine

europe-west1 - Google Cloud Functions

australia-southeast1 - Cloud Run

australia-southeast1 - Google App Engine

australia-southeast1 - Google Cloud Functions

australia-southeast1 - Secret Manager

europe-west1 - Secret Manager

Message

Google Kubernetes Engine customers with Workload Identity enabled may see high application logging rate

Details

Summary: Google Kubernetes Engine customers with Workload Identity enabled may see high application logging rate
Description: There is no impact to cluster functionality or performance. The only impact is extra logs in Cloud Logging.
gke-metadata-server is a GKE-managed system workload that is part of the GKE Workload Identity feature. Versions 0.4.272 to 0.4.280 of gke-metadata-server contain an incorrect configuration that results in a high rate of debug logs that contain the string "Unable to sync sandbox". These logs are then ingested into Cloud Logging, consuming Cloud Logging ingestion quota, and causing excess billable usage when exceeding the free monthly allotment.
A rollout containing a fix to no longer ingest the excess logs to Cloud Logging is about 25% complete.
We will provide an update by Friday, 2023-11-10 14:00 US/Pacific.
Diagnosis: Customers can determine whether their cluster is impacted by inspecting the gke-metadata-server daemonset with kubectl get daemonset -n kube-system -l k8s-app=gke-metadata-server -o yaml and looking at the components.gke.io/component-version annotation in .spec.template.metadata.annotations. If the value is a version between 0.4.272 and 0.4.280 (inclusive), then the cluster is currently affected.
Workaround:
- Customers using GKE Rapid Channel can upgrade their cluster control plane to 1.28.2-gke.1157000 and above, or 1.27.7-gke.1038000 and above.
- Customers on GKE Regular Channel, GKE Stable Channel, or who are not using release channels do not have a workaround at this time.

November 08, 2023 23:55 UTC

WARN

less than a minute

Customer experiencing a requests to Secret Manager timeout for App Engine and Cloud Run. and Google Kubernetes Engine customers with Workload Identity enabled may see high application logging rate

See more
Start Time

November 08, 2023 23:55 UTC

Type WARN
Affected Components

Europe (regions) - Cloud Run

Asia Pacific (regions) - Cloud Run

Europe (regions) - Google App Engine

Asia Pacific (regions) - Google App Engine

Europe (regions) - Google Cloud Functions

Asia Pacific (regions) - Google Cloud Functions

Europe (regions) - Secret Manager

Asia Pacific (regions) - Secret Manager

europe-west1 - Cloud Run

europe-west1 - Google App Engine

europe-west1 - Google Cloud Functions

australia-southeast1 - Cloud Run

australia-southeast1 - Google App Engine

australia-southeast1 - Secret Manager

australia-southeast1 - Google Cloud Functions

europe-west1 - Secret Manager

Message

Customer experiencing a requests to Secret Manager timeout for App Engine and Cloud Run. and Google Kubernetes Engine customers with Workload Identity enabled may see high application logging rate

Details

Summary: Customer experiencing a requests to Secret Manager timeout for App Engine and Cloud Run.
Description: Mitigation work is currently underway by our engineering team.
We do not have an ETA for mitigation at this point.
We will provide more information by Wednesday, 2023-11-08 16:40 US/Pacific.
Diagnosis: Requests to Secret Manager might time out for App Engine and Cloud Run customers.
Workaround: Some customers reported that removing the secret manager calls and "hard coded" the secrets is a workaround.
Summary: Google Kubernetes Engine customers with Workload Identity enabled may see high application logging rate
Description: There is no impact to cluster functionality or performance. The only impact is extra logs in Cloud Logging.
gke-metadata-server is a GKE-managed system workload that is part of the GKE Workload Identity feature. Versions 0.4.272 to 0.4.280 of gke-metadata-server contain an incorrect configuration that results in a high rate of debug logs that contain the string "Unable to sync sandbox". These logs are then ingested into Cloud Logging, consuming Cloud Logging ingestion quota, and causing excess billable usage when exceeding the free monthly allotment.
A rollout containing a fix to no longer ingest the excess logs to Cloud Logging is about 25% complete.
We will provide an update by Friday, 2023-11-10 14:00 US/Pacific.
Diagnosis: Customers can determine whether their cluster is impacted by inspecting the gke-metadata-server daemonset with kubectl get daemonset -n kube-system -l k8s-app=gke-metadata-server -o yaml and looking at the components.gke.io/component-version annotation in .spec.template.metadata.annotations. If the value is a version between 0.4.272 and 0.4.280 (inclusive), then the cluster is currently affected.
Workaround:
- Customers using GKE Rapid Channel can upgrade their cluster control plane to 1.28.2-gke.1157000 and above, or 1.27.7-gke.1038000 and above.
- Customers on GKE Regular Channel, GKE Stable Channel, or who are not using release channels do not have a workaround at this time.

November 08, 2023 23:55 UTC

WARN

about 2 hours

Customer experiencing a requests to Secret Manager timeout for App Engine and Cloud Run. and Google Kubernetes Engine customers with Workload Identity enabled may see high application logging rate

See more
Start Time

November 08, 2023 23:55 UTC

Type WARN
Affected Components

Europe (regions) - Cloud Run

Asia Pacific (regions) - Cloud Run

Europe (regions) - Google App Engine

Asia Pacific (regions) - Google App Engine

Europe (regions) - Google Cloud Functions

Asia Pacific (regions) - Google Cloud Functions

Europe (regions) - Secret Manager

Asia Pacific (regions) - Secret Manager

europe-west1 - Cloud Run

europe-west1 - Google App Engine

europe-west1 - Google Cloud Functions

australia-southeast1 - Cloud Run

australia-southeast1 - Google App Engine

australia-southeast1 - Secret Manager

australia-southeast1 - Google Cloud Functions

europe-west1 - Secret Manager

Message

Customer experiencing a requests to Secret Manager timeout for App Engine and Cloud Run. and Google Kubernetes Engine customers with Workload Identity enabled may see high application logging rate

Details

Summary: Customer experiencing a requests to Secret Manager timeout for App Engine and Cloud Run.
Description: Mitigation work is currently underway by our engineering team.
We do not have an ETA for mitigation at this point.
We will provide more information by Wednesday, 2023-11-08 16:40 US/Pacific.
Diagnosis: Requests to Secret Manager might time out for App Engine and Cloud Run customers.
Workaround: Some customers reported that removing the secret manager calls and "hard coded" the secrets is a workaround.
Summary: Google Kubernetes Engine customers with Workload Identity enabled may see high application logging rate
Description: There is no impact to cluster functionality or performance. The only impact is extra logs in Cloud Logging.
gke-metadata-server is a GKE-managed system workload that is part of the GKE Workload Identity feature. Versions 0.4.272 to 0.4.280 of gke-metadata-server contain an incorrect configuration that results in a high rate of debug logs that contain the string "Unable to sync sandbox". These logs are then ingested into Cloud Logging, consuming Cloud Logging ingestion quota, and causing excess billable usage when exceeding the free monthly allotment.
A rollout containing a fix to no longer ingest the excess logs to Cloud Logging is about 25% complete.
We will provide an update by Friday, 2023-11-10 14:00 US/Pacific.
Diagnosis: Customers can determine whether their cluster is impacted by inspecting the gke-metadata-server daemonset with kubectl get daemonset -n kube-system -l k8s-app=gke-metadata-server -o yaml and looking at the components.gke.io/component-version annotation in .spec.template.metadata.annotations. If the value is a version between 0.4.272 and 0.4.280 (inclusive), then the cluster is currently affected.
Workaround:
- Customers using GKE Rapid Channel can upgrade their cluster control plane to 1.28.2-gke.1157000 and above, or 1.27.7-gke.1038000 and above.
- Customers on GKE Regular Channel, GKE Stable Channel, or who are not using release channels do not have a workaround at this time.

April 28, 2023 01:55 UTC

WARN

less than a minute

Multiple Google Cloud services in the europe-west9-a zone are impacted

See more
Start Time

April 28, 2023 01:55 UTC

Type WARN
Affected Components

Europe (regions) - Cloud NAT

Europe (regions) - Cloud Key Management Service

Europe (regions) - Cloud Load Balancing

Europe (regions) - Cloud Run

Europe (regions) - Data Catalog

Europe (regions) - Eventarc

Europe (regions) - Google Cloud Identity-Aware Proxy

Europe (regions) - Secret Manager

Europe (regions) - Service Directory

Multi-regions - Speech-to-Text

Europe (regions) - Virtual Private Cloud (VPC)

europe-west9 - Access Context Manager

europe-west9 - Artifact Registry

europe-west9 - BigQuery Data Transfer Service

europe-west9 - Cloud External Key Manager

europe-west9 - Cloud Load Balancing

europe-west9 - Cloud Workflows

europe-west9 - Eventarc

europe-west9 - Google Cloud Identity-Aware Proxy

europe-west9 - Service Directory

europe-west9 - Virtual Private Cloud (VPC)

europe - Speech-to-Text

Europe (regions) - Cloud HSM

Europe (regions) - Cloud External Key Manager

Europe (regions) - Artifact Registry

europe-west9 - Data Catalog

Europe (regions) - BigQuery Data Transfer Service

europe-west9 - Cloud Run

Europe (regions) - Cloud Workflows

europe-west9 - Cloud NAT

Europe (regions) - Access Context Manager

europe-west9 - Cloud Key Management Service

europe-west9 - Apigee

Europe (regions) - Apigee

europe-west9 - Secret Manager

Europe (regions) - Google Cloud Storage

europe-west9 - Google Cloud Storage

Message

Multiple Google Cloud services in the europe-west9-a zone are impacted

Details

Summary: Multiple Google Cloud services in the europe-west9-a zone are impacted
Description: Water intrusion in a data center in europe-west9 caused a multi-cluster failure that led to a shutdown of multiple zones. Impact is now limited to services in europe-west9-a. There is no ETA for full recovery of operations in europe-west9-a at this time. We expect to see extended outages for some services. Customers are advised to failover to other zones/regions if they are impacted.
We will provide an update by Friday, 2023-04-28 07:00 US/Pacific, or upon any significant development.
Diagnosis: Customers may be unable to access existing Cloud resources in the europe-west9-a zone.
Workaround: Customers can failover to other zones in europe-west9 or to other regions.

2024-02-20 10:39:18 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-02-20 10:39:18 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-02-20 10:39:18 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-02-20 10:39:18 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

2024-02-20 10:39:18 UTC UTC

STATUS

? minutes

Sign in to view more status history.

See more

Sign Up for More Google Cloud Secret Manager History

StatusGator has over 7 years of Google Cloud Secret Manager status history.

No outages or status changes in the last 24 hours

Google Cloud Secret Manager status, last 24 hours:

11:00 AM
5:00 PM
11:00 PM
5:00 AM
11:00 AM
11:00 AM
11:00 PM
11:00 AM
  • Up: 24 hours

  • Warn: 0 minutes

  • Down: 0 minutes

Google Cloud Secret Manager Outage and Status History

We've been monitoring Google Cloud Secret Manager outages since August 22, 2016.
Here's the history of service outages we've observed from the Google Cloud Secret Manager Status Page:

February 2024

January 2024

December 2023

  • Up

  • Warn

  • Down

Instant enriched data from
3,570 status pages

About Our Google Cloud Secret Manager Status Page Integration

Google Cloud Secret Manager is a Cloud Infrastructure solution that StatusGator has been monitoring since August 2016. Over the past over 7 years, we have collected data on on more than 2,175 outages that affected Google Cloud Secret Manager users. When Google Cloud Secret Manager publishes downtime on their status page, they do so across 6,009 components and 62 groups using 3 different statuses: up, warn, and down which we use to provide granular uptime metrics and notifications.

More than 2,000 StatusGator users monitor Google Cloud Secret Manager to get notified when it's down or has an outage. This makes it one of the most popular cloud infrastructure services monitored on our platform. We've sent more than 396,400 notifications to our users about Google Cloud Secret Manager incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.

If Google Cloud Secret Manager is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.

Warn notifications are used when Google Cloud Secret Manager is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.

Google Cloud Secret Manager does not post separate notifications for planned maintenance work so we are unable to send notifications when maintenance windows begin. If you need Google Cloud Secret Manager maintenance notifications, please email us.

Google Cloud Secret Manager does not publish a feed of proactive maintenance events on their status page at this time. If they do, be sure to let us know and we'll aggregate Google Cloud Secret Manager maintenance events into your unified calendar.

When Google Cloud Secret Manager posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.

When Google Cloud Secret Manager has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.

Because Google Cloud Secret Manager has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.

Frequently Asked Questions

Can’t find your question? Email us to arrange a time to discuss. We’d love to chat!

Google Cloud Secret Manager Down?

Are you experiencing issues with Google Cloud Secret Manager? Sign up to receive notifications when Google Cloud Secret Manager publishes outages.

Google Cloud Secret Manager Down or not working? Never be taken by surprise again.

StatusGator tells you when your cloud services have problems or their statuses change. We monitor the official status pages of more than 3,570 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more.

Looking for recent downtime and outages of Google Cloud Secret Manager?

Sign up for StatusGator and see all historical information about Google Cloud Secret Manager outages and performance issues. Get free, instant notifications when Google Cloud Secret Manager goes down.