asn.dev

Observed topology

AS12390 KINGSTON-UK-AS

Unclassified RIPE

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

Transit

Upstream networks

All 21

Networks observed carrying traffic for AS12390: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6284
AS174Cogent Communications, LLCTransitIPv4 IPv6272
AS6939Hurricane Electric LLCTransitIPv4 IPv6166
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv655
AS50304Blix Solutions ASUnclassifiedIPv434
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv619
AS24482SG.GSHostingIPv4 IPv619
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv619
AS48185team.blue NVUnclassifiedIPv4 IPv619
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv619

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS203067GIACOM (CLOUD) LIMITEDUnclassifiedIPv4290

Adjacency

Adjacent networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6393
AS3356Level 3 Parent, LLCTransitIPv4 IPv6319
AS203067GIACOM (CLOUD) LIMITEDUnclassifiedIPv4290
AS6939Hurricane Electric LLCTransitIPv4 IPv6211
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv670
AS50304Blix Solutions ASUnclassifiedIPv444
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv624
AS24482SG.GSHostingIPv4 IPv624
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv624
AS48185team.blue NVUnclassifiedIPv4 IPv624

Provenance

Where this comes from

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