asn.dev

Observed topology

AS199221 TBG-NET-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS199221: 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
AS57344Telehouse EADResidentialIPv4 IPv6384
AS6939Hurricane Electric LLCTransitIPv4 IPv650
AS5511Orange S.A.TransitIPv4 IPv633
AS24482SG.GSHostingIPv4 IPv65
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv65
AS56655Gigahost ASUnclassifiedIPv4 IPv65
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv65
AS49673Truenetwork LLCUnclassifiedIPv44

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS61996ILLUSION NET EOODUnclassifiedIPv4176
AS204266CENTRAL PARK BURGAS -EOODUnclassifiedIPv428

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS57344Telehouse EADResidentialIPv4 IPv6401
AS61996ILLUSION NET EOODUnclassifiedIPv4176
AS6939Hurricane Electric LLCTransitIPv4 IPv6122
AS5511Orange S.A.TransitIPv4 IPv688
AS204266CENTRAL PARK BURGAS -EOODUnclassifiedIPv428
AS24482SG.GSHostingIPv4 IPv617
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv617
AS56655Gigahost ASUnclassifiedIPv4 IPv617
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv617
AS49673Truenetwork LLCUnclassifiedIPv416

Provenance

Where this comes from

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