asn.dev

Observed topology

AS48219 ThreeData-AS 3DATA LLC

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS48219: 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
AS201706SERVICEPIPE LLCUnclassifiedIPv4507
AS29226JSC MastertelUnclassifiedIPv4348
AS31133PJSC MegaFonMobileIPv4201
AS57304JSC "RetnNet"UnclassifiedIPv4153
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv4132
AS25227JSC "ER-Telecom Holding"UnclassifiedIPv498

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS198769LLC 3data DCUnclassifiedIPv4108
AS41388JSC OriginalUnclassifiedIPv455
AS213555ITH Ltd.UnclassifiedIPv424
AS204049LLC 3dataUnclassifiedIPv413

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS201706SERVICEPIPE LLCUnclassifiedIPv4560
AS29226JSC MastertelUnclassifiedIPv4348
AS9049JSC "ER-Telecom Holding"UnclassifiedIPv4267
AS31133PJSC MegaFonMobileIPv4241
AS57304JSC "RetnNet"UnclassifiedIPv4153
AS198769LLC 3data DCUnclassifiedIPv4153
AS25227JSC "ER-Telecom Holding"UnclassifiedIPv4121
AS41388JSC OriginalUnclassifiedIPv455
AS213555ITH Ltd.UnclassifiedIPv424
AS204049LLC 3dataUnclassifiedIPv419

Provenance

Where this comes from

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