| Provider | Date | Status | Impact | Title | Components | Dur | TT2 | TTM | TTR | # Upd | Words | PM |
|---|
Trend and distribution views for the current scope — set the provider above with the scope chips.
Each line is one provider × impact. "Weekly" is each week's average incident duration; "4-wk running avg" smooths those weekly averages into a running monthly trend.
| Provider | Date | Karma | Comments | Title | Author | Link |
|---|
User-reported problem counts. Spikes correlate with outage days on the status page.
| Provider | Time | Author | Comment |
|---|
Provider postmortems — Anthropic engineering-blog write-ups and OpenAI status-page incident write-ups. Filtered by the scope chip group above. "Incidents covered" counts status-page incidents linked to each postmortem: direct matches share the root cause; likely-related are dated within the same window with overlapping components.
| Provider | Published | Title | Scope | Incidents covered | Source |
|---|
| Provider | Date | Category | Title | Models | Source |
|---|
Each step shows a funding round closed; line tracks cumulative dollars committed (USD billions). Strategic rounds from Amazon and Google included.
"Disclosed" columns come from each lab's system/model cards (Anthropic + OpenAI). "Estimate (FLOPs)" comes from Epoch AI's database; bounds shown where available. Neither lab publishes training compute, parameter counts, or hardware for recent models, so those cells are intentionally blank — OpenAI discloses even less than Anthropic. Epoch's estimates exist mainly for older, well-studied models (e.g. GPT-4, GPT-3).
| Provider | Model | Released | Cutoff | Hardware mentions (card) | Epoch est. FLOPs | Est. cost (2023 USD) | Est. method | Card |
|---|
| Date | Partner | Type | Headline | Capacity | $ committed | Source |
|---|
| Date | Round | Amount ($B) | Post-money valuation ($B) | Lead investors | Source |
|---|
AWS = curated list of major outages affecting us-east-1 / us-east-2 / us-west-2 / global. GCP = full status.cloud.google.com/incidents.json archive. Time-window overlap with a frontier-lab incident is correlation, not causation.
| Date | Provider | Severity | Regions | Services | Summary | Source |
|---|
Frontier labs and the infrastructure they depend on — clouds, chip and memory vendors, optics, fiber, power, cooling, colocation, and investors. Edges are hand-curated from research drops (provider_relationships), not scraped. A solid edge is a documented relationship; a dashed edge is inferred from secondary reporting. Edge thickness tracks risk weight — how concentrated the dependency is. This view ships infrastructure dependencies only; model and data-center nodes are on the roadmap. Drag nodes to reshape the graph; click any node or edge for detail.
Loading incident data…