asn.dev

Observed topology

AS49403 AVK-WELLCOM-AS

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS49403: 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
AS31500Global Network Management IncUnclassifiedIPv490
AS35598INETCOM CARRIER LLCUnclassifiedIPv464
AS24482SG.GSHostingIPv422
AS37721Virtual Technologies & SolutionsResidentialIPv422
AS49673Truenetwork LLCUnclassifiedIPv421
AS31133PJSC MegaFonMobileIPv420
AS25091IP-Max SAUnclassifiedIPv419
AS34927iFog GmbHHostingIPv419
AS6939Hurricane Electric LLCTransitIPv47
AS62255BiMajLink d.o.o.UnclassifiedIPv42

All 12 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS209755Newlime LLCUnclassifiedIPv4122
AS48051Alpla LLCUnclassifiedIPv412
AS201498"MX Management" Ltd.UnclassifiedIPv42

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS31500Global Network Management IncUnclassifiedIPv4164
AS209755Newlime LLCUnclassifiedIPv4122
AS35598INETCOM CARRIER LLCUnclassifiedIPv464
AS31133PJSC MegaFonMobileIPv460
AS24482SG.GSHostingIPv424
AS37721Virtual Technologies & SolutionsResidentialIPv424
AS49673Truenetwork LLCUnclassifiedIPv423
AS6939Hurricane Electric LLCTransitIPv421
AS25091IP-Max SAUnclassifiedIPv419
AS34927iFog GmbHHostingIPv419

All 15 adjacent →

Provenance

Where this comes from

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