asn.dev

Observed topology

AS8487 PHIBEE

Unclassified RIPE NSP

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS8487: 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
AS1299Arelion Sweden ABTransitIPv4 IPv6297
AS3356Level 3 Parent, LLCTransitIPv4130
AS2914NTT America, Inc.TransitIPv4122
AS6939Hurricane Electric LLCTransitIPv496
AS3257GTT Communications Inc.TransitIPv473
AS44407Linkt SASHostingIPv427
AS24482SG.GSHostingIPv412
AS37721Virtual Technologies & SolutionsResidentialIPv412
AS12779IT.Gate S.p.A.UnclassifiedIPv411
AS50628Leonix Telecom SASUnclassifiedIPv411

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS206874Kyxar SARLResidentialIPv4330
AS204805Voiped Wholesale BVResidentialIPv4172
AS199485JL SYSTEMS SASUnclassifiedIPv4123
AS206656AUDAXIS SASUnclassifiedIPv4 IPv637
AS197551Ameos SARLHostingIPv413

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS1299Arelion Sweden ABTransitIPv4 IPv6561
AS206874Kyxar SARLResidentialIPv4330
AS3356Level 3 Parent, LLCTransitIPv4294
AS2914NTT America, Inc.TransitIPv4232
AS204805Voiped Wholesale BVResidentialIPv4172
AS3257GTT Communications Inc.TransitIPv4142
AS6939Hurricane Electric LLCTransitIPv4129
AS199485JL SYSTEMS SASUnclassifiedIPv4123
AS206656AUDAXIS SASUnclassifiedIPv4 IPv637
AS44407Linkt SASHostingIPv427

All 18 adjacent →

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.