asn.dev

Observed topology

AS8851 EDGE GCI Network Solutions Limited

Residential DROP-listed space RIPE

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

Transit

Upstream networks

All 16

Networks observed carrying traffic for AS8851: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv611,763
AS3356Level 3 Parent, LLCTransitIPv43,619
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6954
AS33891Core-Backbone GmbHHostingIPv4631
AS24482SG.GSHostingIPv4 IPv6322
AS48185team.blue NVUnclassifiedIPv4 IPv6322
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv6322
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv6321
AS3741Dimension DataUnclassifiedIPv4316
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4316

All 16 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS29726Vonage Holdings, Inc.UnclassifiedIPv447
AS31632OAG Aviation WorldWide LimitedUnclassifiedIPv441

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv611,858
AS3356Level 3 Parent, LLCTransitIPv43,622
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6963
AS33891Core-Backbone GmbHHostingIPv4631
AS24482SG.GSHostingIPv4 IPv6324
AS48185team.blue NVUnclassifiedIPv4 IPv6324
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv6323
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv6321
AS3741Dimension DataUnclassifiedIPv4319
AS37100SEACOM LimitedUnclassifiedIPv4319

All 19 adjacent →

Provenance

Where this comes from

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