asn.dev

Observed topology

AS719 ELISA-AS ELISA OYJ

Unclassified APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS719: 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 IPv69,090

Transit

Downstream networks

All 56

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

ASNetworkTypeFamiliesPaths seen
AS8983Nokia Solutions and Networks OyUnclassifiedIPv4 IPv6751
AS206175Meidan IT ja talous OyUnclassifiedIPv4594
AS215776KansanelakelaitosUnclassifiedIPv4295
AS41701Capgemini Finland OyUnclassifiedIPv4 IPv6202
AS57664F-Solutions OyUnclassifiedIPv4 IPv6195
AS28883Oy Samlink AbUnclassifiedIPv4175
AS209457Etela-Pohjanmaan HyvinvointialueUnclassifiedIPv4157
AS8145Trans-Atlantic CommunicationsUnclassifiedIPv4 IPv6150
AS58003Planeetta Internet OyUnclassifiedIPv4 IPv6138
AS5420Kemira OyjUnclassifiedIPv4 IPv6118

Adjacency

Adjacent networks

All 57

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

ASNetworkTypeFamiliesPaths seen
AS6667Elisa OyjResidentialIPv4 IPv614,719
AS8983Nokia Solutions and Networks OyUnclassifiedIPv4 IPv6751
AS207003Web1 OyHostingIPv4 IPv6638
AS206175Meidan IT ja talous OyUnclassifiedIPv4594
AS215776KansanelakelaitosUnclassifiedIPv4295
AS41701Capgemini Finland OyUnclassifiedIPv4 IPv6202
AS57664F-Solutions OyUnclassifiedIPv4 IPv6195
AS28883Oy Samlink AbUnclassifiedIPv4175
AS209457Etela-Pohjanmaan HyvinvointialueUnclassifiedIPv4157
AS8145Trans-Atlantic CommunicationsUnclassifiedIPv4 IPv6150

Provenance

Where this comes from

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