Skip to content

Commit

Permalink
Update data on 2025-02-23T03:32:29+00:00
Browse files Browse the repository at this point in the history
  • Loading branch information
Automated committed Feb 23, 2025
1 parent 4f87e66 commit 4c5695d
Showing 1 changed file with 0 additions and 294 deletions.
294 changes: 0 additions & 294 deletions gcp_outages.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -39561,299 +39561,5 @@
"id": "us-west4"
}
]
},
{
"id": "PeLsdQ7XaTwTDQbMoRRh",
"number": "872468119704692812",
"begin": "2024-02-22T12:31:34+00:00",
"created": "2024-02-22T12:56:48+00:00",
"end": "2024-02-24T03:15:16+00:00",
"modified": "2024-02-24T03:15:17+00:00",
"external_desc": "Cloud Asset Data Ingestion Issue",
"updates": [
{
"created": "2024-02-24T03:15:10+00:00",
"modified": "2024-02-24T03:15:18+00:00",
"when": "2024-02-24T03:15:10+00:00",
"text": "The issue with Chronicle Security has been resolved for all affected projects as of Friday, 2024-02-23 19:15 US/Pacific.\nWe thank you for your patience while we worked on resolving the issue.",
"status": "AVAILABLE",
"affected_locations": [
{
"title": "Tokyo (asia-northeast1)",
"id": "asia-northeast1"
},
{
"title": "Mumbai (asia-south1)",
"id": "asia-south1"
},
{
"title": "Singapore (asia-southeast1)",
"id": "asia-southeast1"
},
{
"title": "Sydney (australia-southeast1)",
"id": "australia-southeast1"
},
{
"title": "London (europe-west2)",
"id": "europe-west2"
},
{
"title": "Frankfurt (europe-west3)",
"id": "europe-west3"
},
{
"title": "Zurich (europe-west6)",
"id": "europe-west6"
},
{
"title": "Dammam (me-central2)",
"id": "me-central2"
},
{
"title": "Tel Aviv (me-west1)",
"id": "me-west1"
}
]
},
{
"created": "2024-02-22T17:57:49+00:00",
"modified": "2024-02-22T17:58:32+00:00",
"when": "2024-02-22T17:57:49+00:00",
"text": "Summary: Cloud Asset Data Ingestion Issue\nDescription: We have identified the cause of the Cloud Asset Metadata logs issue which started on Wednesday, 2024-02-14 02:50 US/Pacific.\nMitigation work is currently underway by our engineering team.\nThe mitigation expected time of completion has been revised to Friday, 2024-02-23 20:00 US/Pacific.\nWe will provide more information by Friday, 2024-02-23 21:00 US/Pacific.\nDiagnosis: Customers are unable to receive new Cloud Asset Metadata logs.\nWorkaround: None at this time.",
"status": "SERVICE_INFORMATION",
"affected_locations": [
{
"title": "Tokyo (asia-northeast1)",
"id": "asia-northeast1"
},
{
"title": "Mumbai (asia-south1)",
"id": "asia-south1"
},
{
"title": "Singapore (asia-southeast1)",
"id": "asia-southeast1"
},
{
"title": "Sydney (australia-southeast1)",
"id": "australia-southeast1"
},
{
"title": "London (europe-west2)",
"id": "europe-west2"
},
{
"title": "Frankfurt (europe-west3)",
"id": "europe-west3"
},
{
"title": "Zurich (europe-west6)",
"id": "europe-west6"
},
{
"title": "Dammam (me-central2)",
"id": "me-central2"
},
{
"title": "Tel Aviv (me-west1)",
"id": "me-west1"
}
]
},
{
"created": "2024-02-22T13:36:21+00:00",
"modified": "2024-02-22T13:36:28+00:00",
"when": "2024-02-22T13:36:21+00:00",
"text": "Summary: Cloud Asset Data Ingestion Issue\nDescription: We have identified the cause of the Cloud Asset Metadata logs issue which started on Wednesday, 2024-02-14 02:50 US/Pacific. Mitigation work is currently underway by our engineering team.\nThe mitigation is expected to be completed by Thursday, 2024-02-22 21:00 US/Pacific.\nWe will provide more information by Thursday, 2024-02-22 21:30 US/Pacific.\nDiagnosis: Customers are unable to receive new Cloud Asset Metadata logs.\nWorkaround: None at this time.",
"status": "SERVICE_INFORMATION",
"affected_locations": [
{
"title": "Tokyo (asia-northeast1)",
"id": "asia-northeast1"
},
{
"title": "Mumbai (asia-south1)",
"id": "asia-south1"
},
{
"title": "Singapore (asia-southeast1)",
"id": "asia-southeast1"
},
{
"title": "Sydney (australia-southeast1)",
"id": "australia-southeast1"
},
{
"title": "London (europe-west2)",
"id": "europe-west2"
},
{
"title": "Frankfurt (europe-west3)",
"id": "europe-west3"
},
{
"title": "Zurich (europe-west6)",
"id": "europe-west6"
},
{
"title": "Dammam (me-central2)",
"id": "me-central2"
},
{
"title": "Tel Aviv (me-west1)",
"id": "me-west1"
}
]
},
{
"created": "2024-02-22T13:00:59+00:00",
"modified": "2024-02-22T13:01:09+00:00",
"when": "2024-02-22T13:00:59+00:00",
"text": "Summary: Cloud Asset Metadata logs Issue\nDescription: Our engineering team has identified the cause of this issue and mitigation work is currently underway.\nThe mitigation is expected to be completed by Thursday, 2024-02-22 21:00 US/Pacific.\nWe will provide more information by Thursday, 2024-02-22 21:30 US/Pacific.\nDiagnosis: Impacted customers are not receiving Cloud Asset Metadata logs\nWorkaround: None at this time.",
"status": "SERVICE_INFORMATION",
"affected_locations": []
},
{
"created": "2024-02-22T12:56:44+00:00",
"modified": "2024-02-22T12:56:51+00:00",
"when": "2024-02-22T12:56:44+00:00",
"text": "Summary: Cloud Asset Metadata logs Issue\nDescription: Our engineering team has identified the cause of this issue and mitigation work is currently underway.\nThe mitigation is expected to be completed by Thursday, 2024-02-22 21:00 US/Pacific.\nELSE, We do not have an ETA for mitigation at this point.\nWe will provide more information by Thursday, 2024-02-22 21:30 US/Pacific.\nDiagnosis: Impacted customers are not receiving Cloud Asset Metadata logs\nWorkaround: None at this time.",
"status": "SERVICE_INFORMATION",
"affected_locations": [
{
"title": "Tokyo (asia-northeast1)",
"id": "asia-northeast1"
},
{
"title": "Mumbai (asia-south1)",
"id": "asia-south1"
},
{
"title": "Singapore (asia-southeast1)",
"id": "asia-southeast1"
},
{
"title": "Sydney (australia-southeast1)",
"id": "australia-southeast1"
},
{
"title": "London (europe-west2)",
"id": "europe-west2"
},
{
"title": "Frankfurt (europe-west3)",
"id": "europe-west3"
},
{
"title": "Zurich (europe-west6)",
"id": "europe-west6"
},
{
"title": "Dammam (me-central2)",
"id": "me-central2"
},
{
"title": "Tel Aviv (me-west1)",
"id": "me-west1"
}
]
}
],
"most_recent_update": {
"created": "2024-02-24T03:15:10+00:00",
"modified": "2024-02-24T03:15:18+00:00",
"when": "2024-02-24T03:15:10+00:00",
"text": "The issue with Chronicle Security has been resolved for all affected projects as of Friday, 2024-02-23 19:15 US/Pacific.\nWe thank you for your patience while we worked on resolving the issue.",
"status": "AVAILABLE",
"affected_locations": [
{
"title": "Tokyo (asia-northeast1)",
"id": "asia-northeast1"
},
{
"title": "Mumbai (asia-south1)",
"id": "asia-south1"
},
{
"title": "Singapore (asia-southeast1)",
"id": "asia-southeast1"
},
{
"title": "Sydney (australia-southeast1)",
"id": "australia-southeast1"
},
{
"title": "London (europe-west2)",
"id": "europe-west2"
},
{
"title": "Frankfurt (europe-west3)",
"id": "europe-west3"
},
{
"title": "Zurich (europe-west6)",
"id": "europe-west6"
},
{
"title": "Dammam (me-central2)",
"id": "me-central2"
},
{
"title": "Tel Aviv (me-west1)",
"id": "me-west1"
}
]
},
"status_impact": "SERVICE_INFORMATION",
"severity": "low",
"service_key": "FHwvkSZ6RzzDYAvDZXMM",
"service_name": "Chronicle Security",
"affected_products": [
{
"title": "Chronicle Security",
"id": "FHwvkSZ6RzzDYAvDZXMM"
}
],
"uri": "incidents/PeLsdQ7XaTwTDQbMoRRh",
"currently_affected_locations": [],
"previously_affected_locations": [
{
"title": "Tokyo (asia-northeast1)",
"id": "asia-northeast1"
},
{
"title": "Mumbai (asia-south1)",
"id": "asia-south1"
},
{
"title": "Singapore (asia-southeast1)",
"id": "asia-southeast1"
},
{
"title": "Sydney (australia-southeast1)",
"id": "australia-southeast1"
},
{
"title": "London (europe-west2)",
"id": "europe-west2"
},
{
"title": "Frankfurt (europe-west3)",
"id": "europe-west3"
},
{
"title": "Zurich (europe-west6)",
"id": "europe-west6"
},
{
"title": "Dammam (me-central2)",
"id": "me-central2"
},
{
"title": "Tel Aviv (me-west1)",
"id": "me-west1"
}
]
}
]

0 comments on commit 4c5695d

Please sign in to comment.