Snowflake · Degraded
Observed by INTERNETMON
← All status pages
Vendor-reported status observed by INTERNETMON

Snowflake status

Snowflake · Atlassian Statuspage
Degraded
Atlassian Statuspage reports Partially Degraded Service.
Services by cloud and region
Checked Poll cadence every 60 seconds Feed state fresh
Official signal: this is the provider's own report, collected and retained inside INTERNETMON. Compare it with independent regional monitoring when troubleshooting.

Active incidents

INC20000150

Current status: We've taken additional steps with our warehouse team to reduce provisioning latencies for virtual warehouses, and we've observed some improvement in provisioning latencies as a result. Resource availability remains variable and correlated to overall demand, with some intermittent delays occurring during high-volume times. We're continuing to work closely with our warehouse team to maintain available capacity and keep provisioning times low. Our third-party cloud platform provider has indicated that the additional compute capacity remains on track, and we're continuing to coordinate with them to restore the needed capacity. We'll provide another update within 7 days. Customer experience: Customers hosted in the specified region may intermittently be unable to use Snowpark Container Services. Affected customers may experience failures, timeouts, or delays when running Snowpark Container Services workloads, such as starting or resuming Notebooks, or provisioning or resumi

Status identified Impact degraded Updated

Maintenance

No active or upcoming maintenance was included in this vendor report.

Component health

Reported
675
Retained
100
Affected retained
2
Projection scope: complete · 100 retained of 675 reported components across 53 source groups · bounded/truncated source projection.
Databases, Tables, and Views Group: AWS - US East (N. Virginia) Operational
Databases, Tables, and Views Group: Azure - East US 2 (Virginia) Operational
Databases, Tables, and Views Group: Azure - West Europe (Netherlands) Operational
Databases, Tables, and Views Group: AWS - Europe (Frankfurt) Operational
Databases, Tables, and Views Group: AWS - Asia Pacific (Sydney) Operational
Databases, Tables, and Views Group: AWS - US West (Oregon) Operational
Databases, Tables, and Views Group: AWS - Europe (Ireland) Operational
Databases, Tables, and Views Group: AWS - Asia Pacific (Singapore) Operational
Databases, Tables, and Views Group: Azure - Australia East (New South Wales) Operational
Databases, Tables, and Views Group: Azure - US Gov (Virginia) Operational
Databases, Tables, and Views Group: AWS - Canada (Central) Operational
Databases, Tables, and Views Group: Azure - Canada Central (Toronto) Operational
Databases, Tables, and Views Group: Azure - UAE North (Dubai) Operational
Databases, Tables, and Views Group: AWS - US East (Ohio) Operational
Databases, Tables, and Views Group: AWS - Asia Pacific (Tokyo) Operational
Databases, Tables, and Views Group: Azure - West US 2 (Washington) Operational
Databases, Tables, and Views Group: GCP - US Central 1 (Iowa) Operational
Databases, Tables, and Views Group: GCP - Europe West 4 (Eemshaven) Operational
Databases, Tables, and Views Group: AWS - Asia Pacific (Mumbai) Operational
Databases, Tables, and Views Group: Azure - Switzerland North (Zürich) Operational
Showing 20 of 100 retained components in the compact HTML summary. The JSON projection and interactive view contain the full bounded sample.

Recent observed status changes and checkpoints

These are sparse stored checkpoints—state changes plus hourly samples—not an uptime calculation or an exact incident duration.

Degraded
HTTP 200 · 193.73 ms feed latency
Degraded
HTTP 200 · 156.34 ms feed latency
Degraded
HTTP 200 · 188.33 ms feed latency
Degraded
HTTP 200 · 259.16 ms feed latency
Degraded
HTTP 200 · 100.07 ms feed latency
Degraded
HTTP 200 · 285.24 ms feed latency
Degraded
HTTP 200 · 150.03 ms feed latency
Degraded
HTTP 200 · 198.77 ms feed latency
Degraded
HTTP 200 · 82.0 ms feed latency
Degraded
HTTP 200 · 190.04 ms feed latency

Collection details

Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
275.23 ms