Skip to content

E-commerce & SaaS platform incident events (Shopify, HubSpot, BigCommerce)

Commercial use OKFreshLicense: CC-BY-4.0
Query in workbench

Follow this dataset

Get a notice in your feed when a new snapshot is published. Optionally, we also POST it to your webhook.

Must be a public https address. We never follow redirects.

The full snapshot isn't published yet — check back after the next refresh.Download sample CSVDownload sample JSONSample rows only (up to 20) — not the complete dataset.

Event-level incident history of Shopify, HubSpot, and BigCommerce from their public Statuspage v2 APIs, collected 2026-10-01 (150 rows): UTC created/resolved timestamps, duration_minutes (NULL when unresolved), impact on the critical/major/minor/none taxonomy with weights 4/3/2/1, affected components as a pipe-joined union of the components named in the incident's updates, update_count, per-row incident_url (shortlink), and disruption_score = impact_weight × log10(1 + duration_minutes), round 3. 94 rows are 2026 YTD; Shopify's exposed window runs 2019-10-17 → 2025-06-24 (50 archived incidents, none since June 2025). A shop joins on incident_date to flag checkout/outage-driven demand dips (e.g. 2025-06-24 'Shop Pay unavailable'); subscription businesses read platform-disruption windows as churn/dunning features; sales teams read HubSpot incident days as CRM-degraded days. Coverage gaps (verified 2026-10-01): Stripe has no public incident API; Adyen's Statuspage JSON API is disabled. Update bodies are excluded — factual metadata only. Provenance: agent-curated (intel-1 run 2026-10-01), keyless paginated Statuspage API collection.

Rows
150
Columns
18
Source cadence
Monthly
Last refreshed
Oct 1, 2026
Theme
technology

Use your own AI key

Once today's free allowance is used up, AI features can run on your own provider account.

Kept in this browser tab only (cleared when you close it) and sent with each AI request. Our servers use it for that request and never store or log it.