asn.dev

Observed topology

AS3249 ESTPAK

Residential APNIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS3249: 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
AS1299Arelion Sweden ABTransitIPv4 IPv61,716
AS9002RETN LimitedUnclassifiedIPv4 IPv6237
AS1257Tele2 Sverige ABMobileIPv4 IPv635

Transit

Downstream networks

All 51

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

ASNetworkTypeFamiliesPaths seen
AS198068CLOUD.DOG OUUnclassifiedIPv4 IPv6632
AS43937Playtech Software LtdUnclassifiedIPv4 IPv6466
AS202759RJ Network OUUnclassifiedIPv4 IPv6438
AS42300TOP CONNECT OUUnclassifiedIPv4418
AS204595UUS PROGRAMMUnclassifiedIPv4360
AS201906Eesti Post ASUnclassifiedIPv4 IPv6175
AS43958AS Tallink GruppUnclassifiedIPv4171
AS31605Titanium OUUnclassifiedIPv4 IPv6152
AS196743OU InterframeUnclassifiedIPv4120
AS213757Impressive Solutions OUUnclassifiedIPv4120

All 51 downstreams →

Adjacency

Adjacent networks

All 54

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv65,968
AS9002RETN LimitedUnclassifiedIPv4 IPv6714
AS198068CLOUD.DOG OUUnclassifiedIPv4 IPv6632
AS43937Playtech Software LtdUnclassifiedIPv4 IPv6466
AS202759RJ Network OUUnclassifiedIPv4 IPv6438
AS42300TOP CONNECT OUUnclassifiedIPv4418
AS204595UUS PROGRAMMUnclassifiedIPv4360
AS201906Eesti Post ASUnclassifiedIPv4 IPv6175
AS43958AS Tallink GruppUnclassifiedIPv4171
AS31605Titanium OUUnclassifiedIPv4 IPv6152

All 54 adjacent →

Provenance

Where this comes from

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