asn.dev

Observed topology

AS5091 STRIPE - Stripe, Inc.

Unclassified ARIN Enterprise

Upstreams 26 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 25
Adjacent (IPv6) 3
Upstream graph Who carries AS5091, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS5091 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 26

Networks observed carrying traffic for AS5091: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4552
AS9244Diyixian.com (TW) LimitedHostingIPv450
AS9583Sify LimitedUnclassifiedIPv450
AS200780Eurofiber France SASUnclassifiedIPv450
AS8220COLT Technology Services Group LimitedHostingIPv449
AS2856British Telecommunications LimitedResidentialIPv448
AS6939Hurricane Electric LLCTransitIPv4 IPv643
AS33651Comcast Cable Communications, LLCUnclassifiedIPv439
AS3257GTT Communications Inc.TransitIPv436
AS3356Level 3 Parent, LLCTransitIPv432

Transit

Downstream networks

inferred

Networks for which AS5091 was observed as the last hop before the origin, meaning it appears to provide them transit.

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 26

Every AS seen directly next to AS5091 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4552
AS9244Diyixian.com (TW) LimitedHostingIPv450
AS9583Sify LimitedUnclassifiedIPv450
AS200780Eurofiber France SASUnclassifiedIPv450
AS8220COLT Technology Services Group LimitedHostingIPv449
AS2856British Telecommunications LimitedResidentialIPv448
AS6939Hurricane Electric LLCTransitIPv4 IPv643
AS33651Comcast Cable Communications, LLCUnclassifiedIPv439
AS3257GTT Communications Inc.TransitIPv436
AS3356Level 3 Parent, LLCTransitIPv432

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-10 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 71.97M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.