asn.dev

Observed topology

AS41718 VITRINATV-AS Vitrina TV LLC

Unclassified RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS41718: 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
AS59692IQWeb FZ-LLCUnclassifiedIPv4228
AS35598INETCOM CARRIER LLCUnclassifiedIPv484
AS31500Global Network Management IncUnclassifiedIPv431
AS31133PJSC MegaFonMobileIPv418
AS3216PJSC "Vimpelcom"MobileIPv416
AS62255BiMajLink d.o.o.UnclassifiedIPv415
AS202984Chernyshov Aleksandr AleksandrovichUnclassifiedIPv49
AS57724DDOS-GUARD LTDUnclassifiedIPv48
AS6939Hurricane Electric LLCTransitIPv47
AS24482SG.GSHostingIPv43

All 13 upstreams →

Transit

Downstream networks

inferred

Networks for which AS41718 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 13

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

ASNetworkTypeFamiliesPaths seen
AS59692IQWeb FZ-LLCUnclassifiedIPv4228
AS35598INETCOM CARRIER LLCUnclassifiedIPv484
AS31500Global Network Management IncUnclassifiedIPv431
AS31133PJSC MegaFonMobileIPv418
AS3216PJSC "Vimpelcom"MobileIPv416
AS62255BiMajLink d.o.o.UnclassifiedIPv415
AS202984Chernyshov Aleksandr AleksandrovichUnclassifiedIPv49
AS57724DDOS-GUARD LTDUnclassifiedIPv48
AS6939Hurricane Electric LLCTransitIPv47
AS24482SG.GSHostingIPv43

All 13 adjacent →

Provenance

Where this comes from

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