asn.dev

Observed topology

AS201207 INT-GTB

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS201207: 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
AS60068Datacamp LimitedHostingIPv4600

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS212238Datacamp LimitedHostingIPv4 IPv625,714
AS201341trafficforce, UABUnclassifiedIPv4 IPv6978
AS132817DZCRD Networks LtdUnclassifiedIPv4183
AS205659UAB code200UnclassifiedIPv668
AS149428Code200, UABUnclassifiedIPv634
AS202044Getechbrothers, MBUnclassifiedIPv634
AS133944trafficforce, UABUnclassifiedIPv632
AS205964UAB code200UnclassifiedIPv632

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS60068Datacamp LimitedHostingIPv4 IPv627,675
AS212238Datacamp LimitedHostingIPv4 IPv625,714
AS201341trafficforce, UABUnclassifiedIPv4 IPv6978
AS132817DZCRD Networks LtdUnclassifiedIPv4183
AS205659UAB code200UnclassifiedIPv668
AS149428Code200, UABUnclassifiedIPv634
AS202044Getechbrothers, MBUnclassifiedIPv634
AS133944trafficforce, UABUnclassifiedIPv632
AS205964UAB code200UnclassifiedIPv632

Provenance

Where this comes from

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