asn.dev

Observed topology

AS214749 PAW James Cahill

Unclassified RIPE

Upstreams 10 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 12
Adjacent (IPv6) 12
Upstream graph Who carries AS214749, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS214749 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS214749: 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
AS6939Hurricane Electric LLCTransitIPv6139
AS47272HYEHOST LLCHostingIPv637
AS215638Cilix LimitedResidentialIPv613
AS52025ParadoxNetworks LimitedUnclassifiedIPv69
AS24482SG.GSHostingIPv65
AS48185team.blue NVUnclassifiedIPv65
AS50300CustodianDC LimitedUnclassifiedIPv65
AS34927iFog GmbHHostingIPv63
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv63
AS214915Jan SmyrekUnclassifiedIPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS219522Pupnet LTDUnclassifiedIPv4 IPv699
AS199745terrible llcUnclassifiedIPv4 IPv683

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6213
AS219522Pupnet LTDUnclassifiedIPv4 IPv699
AS199745terrible llcUnclassifiedIPv4 IPv683
AS215638Cilix LimitedResidentialIPv4 IPv656
AS52025ParadoxNetworks LimitedUnclassifiedIPv4 IPv655
AS47272HYEHOST LLCHostingIPv637
AS24482SG.GSHostingIPv4 IPv69
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv69
AS48185team.blue NVUnclassifiedIPv4 IPv67
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv67

All 15 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.