asn.dev

Observed topology

AS31126 SODETEL-AS SODETEL S.A.L.

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS31126: 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
AS42020OGEROUnclassifiedIPv4 IPv614,846

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS15739Berytech SCALUnclassifiedIPv4 IPv6184
AS51938GlobeMed Solutions SALUnclassifiedIPv4122
AS205348Lebanese Swiss Bank s.a.lUnclassifiedIPv4122
AS206169Societe Generale De Banque Au Liban SALUnclassifiedIPv4120
AS206197BLOM BANK S.A.L.UnclassifiedIPv4120
AS219307Multi Technology Access S.A.LUnclassifiedIPv4119
AS62144BBAC S.A.L.UnclassifiedIPv461
AS201544Cimenterie Nationale SALUnclassifiedIPv461
AS209685INDEVCO SALUnclassifiedIPv461
AS39918Azadea Group Holding SALUnclassifiedIPv460

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS42020OGEROUnclassifiedIPv4 IPv615,966
AS15739Berytech SCALUnclassifiedIPv4 IPv6274
AS51938GlobeMed Solutions SALUnclassifiedIPv4122
AS205348Lebanese Swiss Bank s.a.lUnclassifiedIPv4122
AS206169Societe Generale De Banque Au Liban SALUnclassifiedIPv4120
AS206197BLOM BANK S.A.L.UnclassifiedIPv4120
AS219307Multi Technology Access S.A.LUnclassifiedIPv4119
AS62144BBAC S.A.L.UnclassifiedIPv461
AS201544Cimenterie Nationale SALUnclassifiedIPv461
AS209685INDEVCO SALUnclassifiedIPv461

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.