SELECT Outage History
SELECT is up right nowPingoru has recorded 9 incidents for SELECT: 9 in the last 12 months and 4 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 33 of 720 (5%) |
| May 2026 | 1 | 0 of 744 (0%) |
| June 2026 | 1 | 8 of 720 (1%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 1 | 2 of 720 (0%) |
| October 2026 | 3 | 29 of 744 (4%) |
| November 2026 | 0 | 0 of 140 (0%) |
Incidents, newest first
Major October 15, 2026 Some users unable to sign in to SELECT 13h 32m App
Started Oct 15, 2026, 11:38 PM UTC· resolved Oct 16, 2026, 01:10 PM UTC
- identified Oct 15, 2026, 11:38 PM UTC
Some users are unable to sign in to SELECT. After entering their credentials, they see an error page or are sent back to the login screen. Other users aren't affected, and SELECT's dashboards and data collection are working normally. We've identified the cause: a recent change to our website infrastructure rejects sign-in requests from accounts with unusually large session data. We've reported the issue to the team that manages it, and a fix is in progress. We'll post an update when the fix is deployed.
- monitoring Oct 16, 2026, 01:32 AM UTC
We have rolled out a fix to the login issues being experienced by some customers and are monitoring the errors.
- resolved Oct 16, 2026, 01:10 PM UTC
The fix has been confirmed. Affected users should now be able to sign in and use SELECT normally.
Major October 9, 2026 Delayed data refresh for some accounts 9h 39m Metadata Sync & Alerts
Started Oct 09, 2026, 04:00 PM UTC· resolved Oct 10, 2026, 01:39 AM UTC
- identified Oct 09, 2026, 04:00 PM UTC
We’re investigating a delay in today’s scheduled data refresh. About half of connected accounts did not receive their daily update and are showing data up to 24 hours old. No data has been lost. We’ve found the cause and are reprocessing the affected accounts now. Updates to follow.
- monitoring Oct 09, 2026, 04:20 PM UTC
Today’s scheduled data refresh was only partly completed. About half of connected accounts didn’t receive their daily update and are showing data up to 36 hours old. No data has been lost. The cause was a performance regression in our sync scheduling, introduced by a recent change. We’re rolling back that change and reprocessing the affected accounts now. Data will update automatically, and no action is needed on your side. We’ll post an update once all accounts are current.
- monitoring Oct 09, 2026, 05:17 PM UTC
We’ve found and fixed the issue that delayed today’s data refresh for some accounts. The affected accounts are now being reprocessed, and their data will update automatically over the next few hours. We’ll post a final update once all accounts are current.
- monitoring Oct 09, 2026, 06:36 PM UTC
We are still in the process of doing the backfill, and will drop an update when complete.
- monitoring Oct 09, 2026, 09:25 PM UTC
All runs are still progressing. majority of customers should have synced already, however about 7% of connections still remain in progress. We are continuing to monitor them and will post an update when complete.
- resolved Oct 10, 2026, 01:39 AM UTC
The account metadata sync has been completed. If your connection is still appears to be stale, please reach out to support. The next wave of account syncs will commence over the next 2 hours.
Major October 8, 2026 Data sync delays resolved 5h 48m Metadata Sync & Alerts
Started Oct 08, 2026, 10:07 AM UTC· resolved Oct 08, 2026, 03:56 PM UTC
- investigating Oct 08, 2026, 10:07 AM UTC
Some customers' nightly data refresh on October 8 was delayed or did not complete. Dashboards may show data from the previous day. Refreshes are processing again and we are re-running those that failed. We're investigating the cause and will post updates here.
- identified Oct 08, 2026, 10:42 AM UTC
Data refreshes that were delayed or didn't complete on October 8 are now being re-processed. Most affected accounts should see up-to-date dashboards within the next few hours. We're continuing to monitor, and will post another update once re-processing is complete.
- identified Oct 08, 2026, 01:38 PM UTC
Data refreshes that were delayed or didn't complete on October 8 are now largely complete. The remaining affected accounts should see up-to-date dashboards within the next two hours. We're continuing to monitor, and will post another update once re-processing is complete.
- resolved Oct 08, 2026, 03:56 PM UTC
Today's scheduled data syncs were delayed by several hours. Some syncs failed on their first attempt. All affected syncs have now been re-run successfully, and data is up to date. We're adding safeguards to catch and recover from this kind of delay faster. If your data still looks stale, please check your connection settings or contact support.
Major September 11, 2026 Some customers seeing delayed data syncs into SELECT 2h 16m Metadata Sync & Alerts
Started Sep 11, 2026, 02:45 PM UTC· resolved Sep 11, 2026, 05:02 PM UTC
- investigating Sep 11, 2026, 02:45 PM UTC
Some customers' data has not yet synced to SELECT for the overnight runs. We are investigating.
- identified Sep 11, 2026, 03:23 PM UTC
We are reworking our data pipeline due to a Snowflake behaviour change resulting in ineffective query execution and delayed data.
- monitoring Sep 11, 2026, 04:35 PM UTC
We have deployed a fix and we are running our pipelines.
- resolved Sep 11, 2026, 05:02 PM UTC
Affected data has been refreshed.
Major June 2, 2026 Snowflake metadata usage sync is delayed 7h 51m Metadata Sync & Alerts
Started Jun 02, 2026, 02:41 PM UTC· resolved Jun 02, 2026, 10:33 PM UTC
- investigating Jun 02, 2026, 02:41 PM UTC
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. The cortex sync currently blocks all metadata sync.
- monitoring Jun 02, 2026, 04:09 PM UTC
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. The cortex sync currently blocks all metadata sync.
- monitoring Jun 02, 2026, 06:04 PM UTC
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.
- monitoring Jun 02, 2026, 07:20 PM UTC
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.
- monitoring Jun 02, 2026, 08:24 PM UTC
We are currently re-syncing affected accounts after turning off metadata ingestion for the affected Cortex usage tables.
- resolved Jun 02, 2026, 10:33 PM UTC
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.
Critical May 1, 2026 SELECT customers are unable to access SELECT due to an intermittent Cloudflare error 10m Website, Docs, App
Started May 01, 2026, 12:45 PM UTC· resolved May 01, 2026, 12:55 PM UTC
- investigating May 01, 2026, 12:45 PM UTC
The SELECT team has identified an issue with Cloudflare preventing customers from being able to access our website.
- resolved May 01, 2026, 12:55 PM UTC
DNS configuration has been repaired. Our sincere apologies for this unexpected downtime.
Minor April 12, 2026 Syncs failing due to Snowflake issue 1d 9h Metadata Sync & Alerts
Started Apr 12, 2026, 05:35 AM UTC· resolved Apr 13, 2026, 02:57 PM UTC
- investigating Apr 12, 2026, 05:35 AM UTC
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.
- resolved Apr 13, 2026, 02:57 PM UTC
Snowflake have resolved the underlying problem and syncs succeeded overnight.
Minor March 27, 2026 Filters are showing 'Not Set' in place of correct values 27m App
Started Mar 27, 2026, 09:20 PM UTC· resolved Mar 27, 2026, 09:48 PM UTC
- investigating Mar 27, 2026, 09:20 PM UTC
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.
- identified Mar 27, 2026, 09:44 PM UTC
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.
- resolved Mar 27, 2026, 09:48 PM UTC
Issue has been resolved. We apologies for the inconvenience caused.
Minor February 17, 2026 Account level data for 16th February delayed 18h 8m App
Started Feb 17, 2026, 02:52 PM UTC· resolved Feb 18, 2026, 09:01 AM UTC
- investigating Feb 17, 2026, 02:52 PM UTC
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.
- identified Feb 17, 2026, 03:35 PM UTC
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.
- resolved Feb 18, 2026, 09:01 AM UTC
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.