对于大多数 Google Cloud 突发事件，受影响的客户会直接在 Google Cloud 控制台中通过 Personalized Service Health 接收突发事件通知。如果这些突发事件符合提醒条件，还会触发您已配置的所有 Service Health 提醒。
全球 Service Health 团队使用许多不同类型的信号来监控产品状态，如果发生广泛性问题，该团队将更新 Google Cloud Service Health。如果需要，他们将在突发事件解决后发布详细的突发事件分析报告。如需了解支持团队和产品工程团队如何协同解决突发事件，请参阅突发事件生命周期。
符合以下任一条件的突发事件会显示在 Google CloudService Health 中：
重大公开突发事件
在无法使用 Personalized Service Health 信息中心时发生的突发事件
重大突发事件
Google Cloud 将突发事件定义为重大突发事件的前提是该突发事件对全球产生影响，或对多个区域的大量客户项目产生影响。
Google Cloud Service Health 会提供影响 Google Cloud 产品和服务的所有重大突发事件的当前和历史状态信息。如果您遇到的问题未在Google Cloud Service Health 中列出，则可能是只有您的项目或实例遇到了这个问题，或者这个问题影响的客户数量很有限。范围较小的突发事件可能会在支持门户中列出。如果您遇到了 Google Cloud Service Health 未列出的问题，可以与 Service Health 团队联系。
currently_affected_locations：包含有关突发事件积极影响的位置的最新信息。与 updates.affected_locations 不同，此列表在突发事件解决后（即 end 设置为非空值时）会变为空。
previously_affected_locations：包含之前在突发事件中受到影响但目前未受影响的位置的列表。随着突发事件的进展，某些位置可能会解决服务中断问题。这些位置仍会显示在 previously_affected_locations field 中。突发事件解决后（即 end 设置为非空值时），此字段将包含在此突发事件期间受影响的所有位置的列表。
查找有关以往产品中断和服务中断的信息
Google Cloud Service Health 会将 Google Cloud 产品中断和服务中断情况记录下来，并保留最长五年。信息中心会按语言区域显示产品的当前状态。如需查看过去一年中与产品中断和服务中断相关的信息，请点击arrow_forward查看突发事件历史记录。如需查看某个产品在过去五年内的服务中断历史记录，请针对该产品点击history查看详情。
查看区域化状态信息
Google Cloud Service Health 会显示所有 Google Cloud产品的状态，并按区域和全球语言区域进行整理。如需查看多区域位置的状态，请选择特定于区域的标签页。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-19。"],[],[],null,["# Use Google Cloud Service Health as a fallback\n\nThis document explains how to use Google Cloud Service Health in the rare event\nPersonalized Service Health itself is unavailable or affected by a disruption, or\nthe impacted product has not yet onboarded to Personalized Service Health.\n\nGoogle Cloud Service Health provides you with information on ongoing\nwidespread incidents that [meet certain criteria](#when-do-incidents-appear).\nPersonalized Service Health will always have the most information available to\nGoogle Cloud customers.\n\nPrior to March 24, 2022, Google Cloud Service Health was called\nGoogle Cloud Status Dashboard.\n\nAccess Google Cloud Service Health\n----------------------------------\n\nYou can access Google Cloud Service Health through the following:\n\n- A public status dashboard: [Google Cloud Service Health](https://status.cloud.google.com/)\n- A public [RSS feed](https://status.cloud.google.com/en/feed.atom)\n- The Google Cloud console:\n\n 1. In the Google Cloud console, go to the **Support** \\\u003e\n **Cases** page.\n\n\n [Go to Cases](https://console.cloud.google.com/support/cases)\n\n \u003cbr /\u003e\n\n 2. Using the resource selector on the console toolbar, select the resource\n for which you'd like to list known issues.\n\n 3. Click the **Known issues** tab.\n\n Known issues also include minor and limited-scope incidents. You can\n [link a support case to a known issue](/support/docs/customer-care-procedures#link-cases)\n so that you get regular updates and can communicate with support staff.\n Support cases are appropriate for issues that don't qualify as\n incidents or where direct interaction is needed. If you have Premium,\n Enhanced, or Standard Support, you can report an incident by\n [creating a support case](/support/docs/customer-care-procedures#create_a_support_case).\n\nIf you are unable to access Google Cloud Service Health through the\nprevious resources, you can use the\n[Google Cloud Platform Support Questions form](https://support.google.com/cloud/contact/prod_issue).\n\nSupported Google Cloud Service Health incidents\n-----------------------------------------------\n\nFor most Google Cloud incidents, impacted customers receive incident\ncommunications directly through Personalized Service Health in the Google Cloud console.\nIf they meet the alert conditions, these incidents also trigger any\n[Service Health alerts](/service-health/docs/configure-alerts-cloud-logging)\nthat you have configured.\n\nThe global Service Health team monitors the status of products\nusing many different types of signals and updates Google Cloud Service\nHealth in the event of a widespread issue. If needed, they will post a detailed\nincident analysis report after an incident has been resolved. To learn about how\nthe Support and product engineering teams work together to resolve an incident,\nsee the [incident lifecycle](/service-health/docs/incident-lifecycle).\n\nIncidents that meet any of the following criteria appear in Google Cloud\nService Health:\n\n- Major, public incidents\n- Incidents that occur when the Personalized Service Health dashboard is unavailable\n\n### Major incident\n\nGoogle Cloud defines an incident as a Major incident if it has global\nimpact or affecting a significant percentage of customer projects across\nmultiple regions.\n\nIn the rare instance a major incident occurs, we act with urgency to resolve any\nissues.\n\nDuring a major incident, the status of the issue is communicated through the\n[dashboard](https://status.cloud.google.com/).\nA major incident is marked as cancel\n**Service outage** on the dashboard. After the issue is resolved, we publish a\npublic incident report that includes the details of the factors that contributed\nto the incident and the steps we plan to take to prevent such incidents from\nreoccurring.\n\nIn the case of smaller-scoped incidents, a nonpublic report might be made\navailable to customers.\n\n### Issues not listed in Google Cloud Service Health\n\nGoogle Cloud Service Health provides current and historical status\ninformation for any major incident that affects Google Cloud products and\nservices. If you are experiencing an issue that is not listed by\nGoogle Cloud Service Health, the issue might be isolated to your projects\nor instances, or it might impact a limited number of customers. Incidents that\nhave less scope can appear on the\n[Support Portal](https://support.cloud.google.com/portal/). You\ncan contact Service Health about any issues you are experiencing that\nare not listed by Google Cloud Service Health.\n\nIf you are already using\n[Personalized Service Health](https://console.cloud.google.com/servicehealth/incidents),\ncheck if the issue is listed there to determine if your project or instance is\naffected.\n\nIf you are using the Google Cloud console, in the top toolbar, select\nhelp\n\\\u003e **Send feedback**.\n\nConsume Google Cloud Service Health data programmatically\n---------------------------------------------------------\n\nYou can build integrations to consume the data displayed by Google Cloud\nService Health in the following ways:\n\n- Through an RSS feed.\n- Through a JSON history file. You can download the\n [schema for the JSON file](https://status.cloud.google.com/incidents.schema.json)\n from the public status dashboard.\n\n Use the fields marked **Stable** instead of the fields marked **Unstable** .\n In general, ID fields are considered **Stable** whereas fields such as display\n names are considered **Unstable** and might change without warning. Use\n **Stable** fields when integrating with an external system or building\n automation.\n\n If you're trying to programmatically identify incidents impacting\n a particular set of products, use the product IDs (`affected_products\u003eid`),\n not their display names. See the\n [product catalog](https://status.cloud.google.com/products.json) for the\n mapping between product IDs and product names.\n\n A product ID provides a stable field to key off while allowing the display\n name of a product to change. You should reference the product ID when\n programmatically identifying incidents impacting a set of products.\n\nThe RSS feed and JSON history file provide incident status information such as\nthe following:\n\n- Products and locations that the incident impacts\n- Incident start time and end time\n- Overall severity\n- Incident updates that describe how the incident changes over time, including its status and the then impacted locations\n\n### Integrations based on prior Google Cloud Service Health implementations\n\nIn both the RSS feed and the JSON file, the regional status information is an\naddition to the information that was already being published prior to the\nintroduction of regionalized status reporting and change in the name of\nGoogle Cloud Service Health. Therefore, we expect your existing\nintegrations to continue working. However, if you want to consume the regional\nstatus information through your integrations, then you need to modify them.\n\nHere's a detailed description of how regional information appears in both\nthe RSS feed and JSON file:\n\n- **RSS feed**\n\n The regional status information is a new addition to the feed information that\n was provided prior to the introduction of regionalized status. Any locations\n that are reported as affected are appended to the RSS message.\n- **JSON file**\n\n Prior to the regional status update, Google Cloud published a stream of\n incidents where each incident contained a list of affected products and a list\n of status updates for each, if any. These status updates contained an\n unstructured string field that did or did not contain the location\n information.\n\n Now, Google Cloud publishes a stream of incidents just as it did before.\n However, for every incident, each status update contains the following new\n fields:\n - `updates.affected_locations`: contains a structured list of affected locations at the time the update was posted. Every update record and the `most_recent_update` record contain this field.\n - `currently_affected_locations`: contains the most recent information on the locations that are actively impacted by the incident. Unlike `updates.affected_locations`, this list becomes empty after the incident is resolved (that is, when `end` is set to a non-empty value).\n - `previously_affected_locations`: contains a list of locations that were previously impacted during an incident, but aren't currently. As the incident progresses, some locations might have an outage resolution. These locations will still exist in the `previously_affected_locations field`. Once the incident is resolved (that is, when `end` is set to a non-empty value), this field contains a list of all locations that were impacted during this incident.\n\nFind information about past product disruptions and outages\n-----------------------------------------------------------\n\nGoogle Cloud Service Health keeps\na record of disruptions and outages for Google Cloud products for up to\nfive years. The\n[dashboard]() shows the current status of\nproducts by locale. To view information about product disruptions and outages in\nthe last year, click\narrow_forward\n**View incident history** . To view a product's outage history for the last five\nyears, click\nhistory\n**See more** for that product.\n\nView regionalized status information\n------------------------------------\n\nGoogle Cloud Service Health displays the status of all Google Cloud\nproducts organized by region and global locale. To view the status for a\nmulti-region, select the region-specific tab."]]
