Vendor Dependency Graph and Internet Supply Chain Map

FeaturesAugust 2, 20264 min read

The internet supply chain map draws vendor dependency edges from real incidents, replays how outages cascade through hub upstreams, and gives signed-in users a watchlist-backed dependency graph on the dashboard.

The Internet Supply Chain

The internet has a supply chain.

A curated map of hub dependencies and cascade replays built from real vendor incidents, not a live ops feed.

Historical graph

Cascade replayAWS outage window

Signed-in users also get a watchlist-backed dependency map on the dashboard, scoped to the vendors they actually run.

Explore the supply chain map Your stack graph

Highlights

Explore curated hub dependencies and replay historical cascade windows from AWS, Azure, Cloudflare, and other upstreams.
See how downstream vendors mention upstream outages in incident history, with edges qualified for recurrence and causation language.
Open your personal stack graph on the dashboard to map concentration risk across the vendors you actually watch.

We launched the internet supply chain map to answer a question most teams never draw explicitly: when a hub upstream stumbles, which vendors in your stack are actually connected to it? The public map at Supply chain map is built from hundreds of thousands of real vendor incidents. Deterministic extraction finds dependency mentions between vendors, then filters noise so the graph shows qualified edges rather than one-off name drops.

The page is a curated historical view, not a live operations feed. You can explore hub nodes such as AWS, Azure, GCP, Cloudflare, GitHub, and Okta, then scrub through cascade replay windows to watch how downstream incident mentions light up after major upstream events. Guided replay hints walk through well-known outage patterns without implying every edge is causation.

Signed-in users get a complementary slice on Dashboard the same day: stack concentration and an interactive dependency graph scoped to the vendors on your watchlist. The same qualification bar applies, so your personal map reflects upstreams that recur in incident history for vendors you care about, not the entire public graph.

We added the map to Solutions navigation, the site footer, and signup attribution so teams evaluating Huntertech during an outage can see why dependency context matters. The public teaser shows that the graph exists; deeper resilience scoring, cascade alerts, and exports remain on the product roadmap behind authenticated tiers.

If your team runs on vendors that share hidden upstreams, start with the public map, then sign in to see how your watchlist concentrates around those hubs. Pair it with timeline, incidents, and scorecards when you are triaging whether a downstream outage is isolated or part of a broader cascade.