asn.dev

Observed topology

AS204779 LOCALNET

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS204779: 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
AS6667Elisa OyjResidentialIPv4 IPv665
AS1299Arelion Sweden ABTransitIPv4 IPv664
AS6939Hurricane Electric LLCTransitIPv4 IPv639
AS47605FNE-Finland OyUnclassifiedIPv4 IPv633
AS50304Blix Solutions ASUnclassifiedIPv46
AS20764CJSC RASCOMUnclassifiedIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS31389Atomidata OyUnclassifiedIPv4 IPv6208
AS8145Trans-Atlantic CommunicationsUnclassifiedIPv4 IPv6184
AS197351Fluentscale OyUnclassifiedIPv4 IPv6151
AS16331Tele-entre OyUnclassifiedIPv459
AS207265Remedy Entertainment OyjUnclassifiedIPv4 IPv638
AS210252Mintly OyUnclassifiedIPv4 IPv619
AS202509Cloud City OyHostingIPv62

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS6667Elisa OyjResidentialIPv4 IPv6457
AS31389Atomidata OyUnclassifiedIPv4 IPv6208
AS1299Arelion Sweden ABTransitIPv4 IPv6191
AS8145Trans-Atlantic CommunicationsUnclassifiedIPv4 IPv6184
AS197351Fluentscale OyUnclassifiedIPv4 IPv6151
AS6939Hurricane Electric LLCTransitIPv4 IPv6130
AS47605FNE-Finland OyUnclassifiedIPv4 IPv6111
AS16331Tele-entre OyUnclassifiedIPv459
AS207265Remedy Entertainment OyjUnclassifiedIPv4 IPv638
AS210252Mintly OyUnclassifiedIPv4 IPv619

Provenance

Where this comes from

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