asn.dev

Observed topology

AS59877 VATELECOM

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS59877: 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
AS174Cogent Communications, LLCTransitIPv4358
AS5511Orange S.A.TransitIPv4 IPv6160
AS6939Hurricane Electric LLCTransitIPv428
AS24482SG.GSHostingIPv4 IPv611
AS49451Association Ouest NetworkUnclassifiedIPv4 IPv611
AS6696VERIXI SAUnclassifiedIPv49
AS25091IP-Max SAUnclassifiedIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS208957Ingenierie Informatique Systeme Et Reseau SARLUnclassifiedIPv4156
AS209686ATEMIS SASUnclassifiedIPv458
AS203797VA TELECOM SASUnclassifiedIPv457
AS208963RLG INFORMATIQUE SASUnclassifiedIPv457

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4583
AS5511Orange S.A.TransitIPv4 IPv6230
AS208957Ingenierie Informatique Systeme Et Reseau SARLUnclassifiedIPv4156
AS209686ATEMIS SASUnclassifiedIPv458
AS203797VA TELECOM SASUnclassifiedIPv457
AS208963RLG INFORMATIQUE SASUnclassifiedIPv457
AS6939Hurricane Electric LLCTransitIPv442
AS49451Association Ouest NetworkUnclassifiedIPv4 IPv618
AS24482SG.GSHostingIPv4 IPv617
AS6696VERIXI SAUnclassifiedIPv415

Provenance

Where this comes from

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