Grid Status Outage History

Grid Status is up right now

Grid Status had 5 outages in the last 2 years totaling 467h 51m of downtime, averaging 0.2 incidents per month.

There were 5 Grid Status outages since January 5, 2025 totaling 467h 51m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.gridstatus.io

Major November 18, 2025

Grid Status App Currently Unavailable Due to Cloudflare Outage

Detected by Pingoru
Nov 18, 2025, 11:45 AM UTC
Resolved
Nov 18, 2025, 02:42 PM UTC
Duration
2h 57m
Affected: Website and APIs (Grid Status App)
Timeline · 2 updates
  1. investigating Nov 18, 2025, 11:45 AM UTC

    The Grid Status application is currently unavailable due to a Cloudflare outage (https://www.cloudflarestatus.com/incidents/8gmgl950y3h7). The API, Snowflake, data ingestion, and alerts are unaffected. We are actively monitoring the situation and will provide updates in real time.

  2. resolved Nov 18, 2025, 02:42 PM UTC

    The Grid Status app is now available as Cloudflare has recovered.

Read the full incident report →

Major March 26, 2025

Snowflake sync delayed

Detected by Pingoru
Mar 26, 2025, 01:40 AM UTC
Resolved
Mar 26, 2025, 07:34 PM UTC
Duration
17h 54m
Affected: Snowflake Data Warehouse (Snowflake Real-Time Data Sync)
Timeline · 2 updates
  1. investigating Mar 26, 2025, 01:40 AM UTC

    We are currently experiencing delays in data updates to Snowflake due to a partial outage at our Snowflake sync provider. Our team is actively in communication with the vendor to resolve this issue. We will provide further updates as more information becomes available.

  2. resolved Mar 26, 2025, 07:34 PM UTC

    Real-time data is syncing again. We will be monitoring closely to make sure it remains stable

Read the full incident report →

Minor February 28, 2025

Snowflake Real Time Data Not Syncing

Detected by Pingoru
Feb 28, 2025, 03:32 PM UTC
Resolved
Mar 18, 2025, 12:48 AM UTC
Duration
17d 9h
Affected: Snowflake Data Warehouse (Snowflake Real-Time Data Sync)
Timeline · 2 updates
  1. investigating Feb 28, 2025, 03:32 PM UTC

    Due to an issue with Snowflake's database connector, real-time data is not being ingested into Snowflake as of 9 PM UTC, February 26, 2025. All historical data remains available. We are actively working with Snowflake to resolve the issue. Real-time data is available through the API.

  2. resolved Mar 18, 2025, 12:48 AM UTC

    Data is currently syncing in near-real-time for 95% of datasets. If you are experiencing any issues, please reach out to us directly at [email protected]. A detailed post-mortem will be shared directly with impacted customers upon resolution and full analysis of the issues. Thank you for your patience as we resolved this matter.

Read the full incident report →

Minor February 25, 2025

Snowflake Real Time Data is Not Syncing

Detected by Pingoru
Feb 25, 2025, 07:39 PM UTC
Resolved
Feb 27, 2025, 01:23 AM UTC
Duration
1d 5h
Affected: Snowflake Data Warehouse (Snowflake Real-Time Data Sync)
Timeline · 2 updates
  1. investigating Feb 25, 2025, 07:39 PM UTC

    Due to an issue with Snowflake's database connector, real-time data is not being ingested into Snowflake as of 12:15 AM UTC February 25, 2025. All historical data remains available. We are actively working with Snowflake to resolve the issue.

  2. resolved Feb 27, 2025, 01:23 AM UTC

    Real-time data sync to Snowflake has resumed as of 21:10 UTC (16:10 EST). No data has been lost.

Read the full incident report →

Major January 5, 2025

Snowflake Sync New Data Unavailable

Detected by Pingoru
Jan 05, 2025, 03:08 PM UTC
Resolved
Jan 05, 2025, 03:08 PM UTC
Duration
–
Affected: Snowflake Data Warehouse (Snowflake Real-Time Data Sync)
Timeline · 1 update
  1. resolved Jan 05, 2025, 03:08 PM UTC

    Due to an issue affecting Snowflake's Postgres connector, new data was unavailable in Snowflake from Dec 31, 2024 at 8:32pm EST to Jan 4, 2025 at 7:27am EST. Data from before Dec 31, 2024 was available for the duration of the incident. No data was lost and new data has been syncing since the end of the incident. We have taken steps to prevent this issue from re-occurring.

Read the full incident report →