asn.dev

Observed topology

AS42020 LibanTelecom OGERO

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42020: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6656
AS5511Orange S.A.TransitIPv4 IPv6203

Transit

Downstream networks

All 107

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

ASNetworkTypeFamiliesPaths seen
AS31126SODETEL S.A.L.UnclassifiedIPv4 IPv614,846
AS9051Data Management salUnclassifiedIPv4 IPv612,519
AS39010TerraNet salUnclassifiedIPv4 IPv69,284
AS41833Moscanet SALUnclassifiedIPv44,957
AS42334Broadband Plus S.a.l.ResidentialIPv44,509
AS42003OGEROUnclassifiedIPv4 IPv64,296
AS24634Transmog Inc S.A.LUnclassifiedIPv42,483
AS35197Virtual ISP s.a.l.UnclassifiedIPv41,380
AS56902Energy Bridge SarlUnclassifiedIPv41,147
AS43824Masco Group LLCUnclassifiedIPv4 IPv61,117

All 107 downstreams →

Adjacency

Adjacent networks

All 109

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv646,330
AS5511Orange S.A.TransitIPv4 IPv642,671
AS31126SODETEL S.A.L.UnclassifiedIPv4 IPv615,966
AS9051Data Management salUnclassifiedIPv4 IPv614,659
AS39010TerraNet salUnclassifiedIPv4 IPv610,458
AS41833Moscanet SALUnclassifiedIPv45,138
AS42334Broadband Plus S.a.l.ResidentialIPv44,509
AS42003OGEROUnclassifiedIPv4 IPv64,296
AS24634Transmog Inc S.A.LUnclassifiedIPv43,525
AS35197Virtual ISP s.a.l.UnclassifiedIPv41,380

All 109 adjacent →

Provenance

Where this comes from

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