SELECT Outage History

SELECT is up right now

SELECT had 6 outages in the last 2 years — averaging 0.2 incidents per month.

There were 6 SELECT outages since February 17, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.select.dev

Minor September 11, 2026

Some customers seeing delayed data syncs into SELECT

Detected by Pingoru
Sep 11, 2026, 05:02 PM UTC
Resolved
Sep 11, 2026, 05:02 PM UTC
Duration
—
Affected: Metadata Sync & Alerts
Timeline · 4 updates
  1. investigating Sep 11, 2026, 02:45 PM UTC

    Status: Investigating Some customers' data has not yet synced to SELECT for the overnight runs. We are investigating. Affected components Metadata Sync & Alerts (Partial outage)

  2. identified Sep 11, 2026, 03:23 PM UTC

    Status: Identified We are reworking our data pipeline due to a Snowflake behaviour change resulting in ineffective query execution and delayed data. Affected components Metadata Sync & Alerts (Partial outage)

  3. monitoring Sep 11, 2026, 04:35 PM UTC

    Status: Monitoring We have deployed a fix and we are running our pipelines. Affected components Metadata Sync & Alerts (Partial outage)

  4. resolved Sep 11, 2026, 05:02 PM UTC

    Status: Resolved Affected data has been refreshed. Affected components Metadata Sync & Alerts (Operational)

Read the full incident report →

Minor June 2, 2026

Snowflake metadata usage sync is delayed

Detected by Pingoru
Jun 02, 2026, 10:33 PM UTC
Resolved
Jun 02, 2026, 10:33 PM UTC
Duration
—
Affected: Metadata Sync & Alerts
Timeline · 6 updates
  1. investigating Jun 02, 2026, 02:41 PM UTC

    Status: Investigating Some customers may experience delayed data in SELECT today due to a Snowflake platform issue affecting access to certain Cortex usage views. We are actively working with Snowflake support to resolve this and expect data pipelines to resume normally once the issue is addressed. Affected components Metadata Sync & Alerts (Partial outage)

  2. monitoring Jun 02, 2026, 04:09 PM UTC

    Status: Monitoring Snowflake support has confirmed that this is an issue with a configuration change on the following views: • cortex_functions_query_usage_history • cortex_document_processing_usage_history • cortex_aisql_usage_history • cortex_search_daily_usage_history • cortex_search_serving_usage_history Snowflake support has escalated this to their engineering team internally to investigate a possible regression. We are waiting on Snowflake to deploy a fix or rollback. Affected components Metadata Sync & Alerts (Partial outage)

  3. monitoring Jun 02, 2026, 06:04 PM UTC

    Status: Monitoring Snowflake support has informed us of a rollback in progress to mitigate this issue on their side. We are continuing to monitor, and will initiate the sync as soon as we have clearance from Snowflake. In parallel we are developing a workaround to allow the rest of the app to sync. Note: this issue blocks metadata sync across the whole app. Affected components Metadata Sync & Alerts (Partial outage)

  4. monitoring Jun 02, 2026, 07:20 PM UTC

    Status: Monitoring We are deploying a workaround that will unblock the metadata sync for the rest of the app, minus Cortex spend. Once the deploy is complete, we will backfill affected customers. Once Snowflake confirms rollback from their side, we will backfill the AI spend as well. Affected components Metadata Sync & Alerts (Partial outage)

  5. monitoring Jun 02, 2026, 08:24 PM UTC

    Status: Monitoring We are currently re-syncing affected accounts after turning off metadata ingestion for the affected Cortex usage tables. Affected components Metadata Sync & Alerts (Partial outage)

  6. resolved Jun 02, 2026, 10:33 PM UTC

    Status: Resolved We have workaround the Snowflake cortex usage access issues by turning off sync for the affected accounts. Once Snowflake rolls out the fix for cortex usage access, we will backfill the affected accounts. Affected components Metadata Sync & Alerts (Operational)

Read the full incident report →

Minor May 1, 2026

SELECT customers are unable to access SELECT due to an intermittent Cloudflare error

Detected by Pingoru
May 01, 2026, 12:55 PM UTC
Resolved
May 01, 2026, 12:55 PM UTC
Duration
—
Affected: WebsiteDocsApp
Timeline · 2 updates
  1. investigating May 01, 2026, 12:45 PM UTC

    Status: Investigating The SELECT team has identified an issue with Cloudflare preventing customers from being able to access our website. Affected components Docs (Full outage) App (Full outage) Website (Full outage)

  2. resolved May 01, 2026, 12:55 PM UTC

    Status: Resolved DNS configuration has been repaired. Our sincere apologies for this unexpected downtime. Affected components App (Operational) Website (Operational) Docs (Operational)

Read the full incident report →

Minor April 13, 2026

Syncs failing due to Snowflake issue

Detected by Pingoru
Apr 13, 2026, 02:57 PM UTC
Resolved
Apr 13, 2026, 02:57 PM UTC
Duration
—
Affected: Metadata Sync & Alerts
Timeline · 2 updates
  1. investigating Apr 12, 2026, 05:35 AM UTC

    Status: Investigating Multiple Snowflake account usage views are unable to be queried right now due to an error "Schema 'SNOWHOUSE_LOCAL.DS_USAGE.BILLING' does not exist or not authorized.". This is an internal Snowflake issue, we are monitoring the situation. Syncs will be delayed until the underlying issue is resolved by Snowflake. Affected components Metadata Sync & Alerts (Degraded performance)

  2. resolved Apr 13, 2026, 02:57 PM UTC

    Status: Resolved Snowflake have resolved the underlying problem and syncs succeeded overnight. Affected components Metadata Sync & Alerts (Operational)

Read the full incident report →

Minor March 27, 2026

Filters are showing 'Not Set' in place of correct values

Detected by Pingoru
Mar 27, 2026, 09:48 PM UTC
Resolved
Mar 27, 2026, 09:48 PM UTC
Duration
—
Affected: App
Timeline · 3 updates
  1. investigating Mar 27, 2026, 09:20 PM UTC

    Status: Investigating Filters throughout the app are incorrectly rendering values as 'Not Set'. The team are actively working on resolving this issue, and the estimated time to fix is half an hour. Affected components App (Degraded performance)

  2. identified Mar 27, 2026, 09:44 PM UTC

    Status: Identified We have identified the issue causing the filters to show "Not Set". We are in the process of rolling out a fix, which should be deployed within 30 minutes. Affected components App (Degraded performance)

  3. resolved Mar 27, 2026, 09:48 PM UTC

    Status: Resolved Issue has been resolved. We apologies for the inconvenience caused. Affected components App (Operational)

Read the full incident report →

Minor February 18, 2026

Account level data for 16th February delayed

Detected by Pingoru
Feb 18, 2026, 09:01 AM UTC
Resolved
Feb 18, 2026, 09:01 AM UTC
Duration
—
Affected: App
Timeline · 3 updates
  1. investigating Feb 17, 2026, 02:52 PM UTC

    Status: Investigating We're aware that for many customers, spend data for the 16th Feb (yesterday) is incomplete while historic data remains accurate. We are investigating what has caused this. Affected components App (Degraded performance)

  2. identified Feb 17, 2026, 03:35 PM UTC

    Status: Identified We're aware of an issue affecting spend synced in the last 24 hours, where the most recent data is not showing in the app. Historic data is unaffected. We have identified the root cause, and are in the process of rolling out a fix to all affected accounts. Affected components App (Degraded performance)

  3. resolved Feb 18, 2026, 09:01 AM UTC

    Status: Resolved Account level data from the 16th was delayed for many accounts on the 17th. All accounts are now working normally and data for the 17th has synced to customers in line with normal expectations. Affected components App (Operational)

Read the full incident report →