Previous incidents

January 2025
Jan 08, 2025
1 incident

Azure billing connections delayed in platform

Degraded

Resolved Jan 08 at 02:30pm EST

We have identified and rectified the root cause of this issue. All Azure connections are up to date or currently ingesting data, and will be available in the CloudZero platform alongside their respective billing data as soon as our normal nightly billing ingest cycle completes.

1 previous update

December 2024
No incidents reported
November 2024
Nov 25, 2024
1 incident

Some billing connections delayed in CloudZero platform

Degraded

Resolved Nov 25 at 11:45am EST

We have identified and mitigated the root cause, and have triggered processes to ingest the latest billing data for all impacted billing connections. We expect all billing data to be caught up shortly.

1 previous update

Nov 12, 2024
1 incident

CloudWatch Kubernetes container metric ingestion delayed

Degraded

Resolved Nov 13 at 12:00am EST

We have identified and rectified the root cause of this issue. All CloudWatch container metrics are up to date for all impacted customers, and will be available in the CloudZero platform alongside their respective billing data as soon as our normal nightly billing ingest cycle completes.

1 previous update

Nov 08, 2024
1 incident

Delayed Datadog Billing Data

Degraded

Resolved Nov 09 at 01:00pm EST

Datadog has provided a workaround for this behavior for the time being. Please consult your FinOps Account Manager for steps to remediate as needed. We will continue to assist Datadog with troubleshooting in the meantime.

2 previous updates

Nov 06, 2024
1 incident

Analytics data issue

Resolved Nov 06 at 04:20pm EST

Our underlying Analytics provider has found a bug that can result in data being slightly delayed. It only impacts a specific backend analytics component, currently only included in the CloudZero standard dashboard "AWS Reservation Catalog" and a few custom dashboards delivered via CloudZero Customer Success (they will reach out if you are impacted).

We have opened a bug with the provider and are working on a workaround in parallel.

The workaround was deployed last night and we continue to ...