asn.dev

Observed topology

AS50629 LWLCOM

Unclassified RIPE

Upstreams 33 carry this network
Downstreams 217 this network carries
Adjacent (IPv4) 318
Adjacent (IPv6) 145
Upstream graph Who carries AS50629, and who carries them, drawn as a map up to the transit-free core. 22 exchanges Where AS50629 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 33

Networks observed carrying traffic for AS50629: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6192
AS3356Level 3 Parent, LLCTransitIPv4 IPv6175
AS1299Arelion Sweden ABTransitIPv4 IPv6160
AS2914NTT America, Inc.TransitIPv4144
AS174Cogent Communications, LLCTransitIPv4 IPv6113
AS3257GTT Communications Inc.TransitIPv4 IPv6112
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv680
AS50304Blix Solutions ASUnclassifiedIPv4 IPv664
AS3320Deutsche Telekom AGMobileIPv4 IPv632
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv632

Transit

Downstream networks

All 217

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

ASNetworkTypeFamiliesPaths seen
AS41110DSLmobil GmbHUnclassifiedIPv4 IPv61,364
AS59790Marco Bungalski GmbHResidentialIPv4 IPv61,157
AS207252Felix GassanUnclassifiedIPv4 IPv61,036
AS31543myNet GmbHResidentialIPv4 IPv6917
AS200482nexserv GmbHUnclassifiedIPv4 IPv6597
AS3214xTom GmbHHostingIPv4 IPv6572
AS12360KEVAG Telekom GmbHResidentialIPv4 IPv6521
AS214915Jan SmyrekUnclassifiedIPv4 IPv6442
AS15763DOKOM Gesellschaft fuer Telekommunikation mbHResidentialIPv4 IPv6436
AS59645Tobias FiebigUnclassifiedIPv4 IPv6416

Adjacency

Adjacent networks

All 352

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

ASNetworkTypeFamiliesPaths seen
AS31543myNet GmbHResidentialIPv4 IPv68,243
AS2914NTT America, Inc.TransitIPv4 IPv64,014
AS3356Level 3 Parent, LLCTransitIPv4 IPv63,174
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv63,020
AS207252Felix GassanUnclassifiedIPv4 IPv62,271
AS1299Arelion Sweden ABTransitIPv4 IPv62,149
AS174Cogent Communications, LLCTransitIPv4 IPv61,769
AS15763DOKOM Gesellschaft fuer Telekommunikation mbHResidentialIPv4 IPv61,636
AS41110DSLmobil GmbHUnclassifiedIPv4 IPv61,469
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv4 IPv61,365

Provenance

Where this comes from

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