asn.dev

Observed topology

AS15570 INAP-LON PACKETFABRIC (UK) LTD

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS15570: 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
AS1828Unitas GlobalUnclassifiedIPv4 IPv6978

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS20249Jefferies LLCUnclassifiedIPv4277
AS19812BT Americas, IncUnclassifiedIPv4232
AS32475Internap Holding LLCHostingIPv4 IPv6154
AS12884DRW Investments (UK) LimitedUnclassifiedIPv4134
AS40620QIAGEN Redwood City, Inc.UnclassifiedIPv460
AS393954CFN Services Inc.UnclassifiedIPv460
AS26931Schonfeld Strategic Techworx, LLC.UnclassifiedIPv459
AS44617HBK EUROPE MANAGEMENT LLPUnclassifiedIPv456
AS21734Trading Technologies Intl, Inc.UnclassifiedIPv450
AS34654Merula LimitedUnclassifiedIPv427

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS1828Unitas GlobalUnclassifiedIPv4 IPv62,682
AS393954CFN Services Inc.UnclassifiedIPv4655
AS20249Jefferies LLCUnclassifiedIPv4277
AS19812BT Americas, IncUnclassifiedIPv4232
AS32475Internap Holding LLCHostingIPv4 IPv6154
AS12884DRW Investments (UK) LimitedUnclassifiedIPv4134
AS40620QIAGEN Redwood City, Inc.UnclassifiedIPv460
AS26931Schonfeld Strategic Techworx, LLC.UnclassifiedIPv459
AS44617HBK EUROPE MANAGEMENT LLPUnclassifiedIPv456
AS21734Trading Technologies Intl, Inc.UnclassifiedIPv450

Provenance

Where this comes from

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