Google Cloud – UPDATE: Data Ingestion feeds errors while using SecOps

Summary: Data Ingestion feeds errors while using SecOps

Incident began at 2025-01-09 22:20 (all times are US/Pacific).

Our engineering team continues to investigate the issue.

Description: Customers ingesting data via feeds will experience errors and delays while using SecOps beginning at Thursday, 2025-01-09 16:20 US/Pacific.

We apologize to all who are affected by the disruption.

We will provide an update by Friday, 2025-01-10 00:30 US/Pacific with current details.

Workaround: None at this time.

Diagnosis: Customers impacted by this issue may observe DNS errors and delay in ingestion of their data.

Affected locations: Tokyo (asia-northeast1), Mumbai (asia-south1), Singapore (asia-southeast1), Sydney (australia-southeast1), Multi-region: europe, Turin (europe-west12), London (europe-west2), Frankfurt (europe-west3), Zurich (europe-west6), Paris (europe-west9), Doha (me-central1), Dammam (me-central2), Tel Aviv (me-west1), Toronto (northamerica-northeast2), São Paulo (southamerica-east1), Multi-region: us


Affected products: Chronicle Security

Jira Work Management – Component field value not available

Jan 10, 04:02 UTC
Resolved – Between 11:30:00 UTC on 9/Jan/25 to 2:30:00 UTC on 10/Jan/25, we experienced a problem displaying the component values in Jira, Jira Work Management and Jira Service Management for some customers. The issue has been resolved and the service is operating normally.

Jan 9, 23:19 UTC
Update – We are continuing to investigate why components are not appearing for some users and will provide updates as we learn more.

Jan 9, 21:53 UTC
Investigating – We have identified an incident that caused the components to disappear from the field and affected our Jira, Jira work management, and Jira Service Desk Cloud customers. As of now, we do not have a root cause for the incident. We are investigating and will post updates within the next hour.

Jira – Component field value not available

Jan 10, 04:00 UTC
Resolved – Between 11:30:00 UTC on 9/Jan/25 to 2:30:00 UTC on 10/Jan/25, we experienced a problem displaying the component values in Jira, Jira Work Management and Jira Service Management for some customers. The issue has been resolved and the service is operating normally.

Jan 9, 23:20 UTC
Update – We are continuing to investigate why components are not appearing for some users and will provide updates as we learn more.

Jan 9, 21:55 UTC
Investigating – We have identified an incident that caused the components to disappear from the field and affected our Jira, Jira work management and Jira Service Desk Cloud customers. As of now, we do not have a root cause for the incident. We are investigating and will post updates within the next hour.

Cloudflare – KUL (Kuala Lumpur) on 2025-01-10

Jan 3, 08:34 UTC
Scheduled – We will be performing scheduled maintenance in KUL (Kuala Lumpur) datacenter on 2025-01-10 between 04:00 and 09:00 UTC.

Traffic might be re-routed from this location, hence there is a possibility of a slight increase in latency during this maintenance window for end-users in the affected region. For PNI / CNI customers connecting with us in this location, please make sure you are expecting this traffic to fail over elsewhere during this maintenance window as network interfaces in this datacentre may become temporarily unavailable.

You can now subscribe to these notifications via Cloudflare dashboard and receive these updates directly via email, PagerDuty and webhooks (based on your plan): https://developers.cloudflare.com/notifications/notification-available/#cloudflare-status.

THIS IS A SCHEDULED EVENT Jan 10, 04:0009:00 UTC