asn.dev

Observed topology

AS2484 NIC-FR-DNS-ANYCAST-AFNIC AFNIC Association Francaise pour le Nommage Internet en Cooperation

Upstreams 23 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 20
Adjacent (IPv6) 13

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS2484: 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 IPv643
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv65
AS2914NTT America, Inc.TransitIPv4 IPv63
AS3257GTT Communications Inc.TransitIPv42
AS39392SH.cz s.r.o.HostingIPv42
AS29632Netassist International EOODUnclassifiedIPv62
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv62
AS212024Marc SchmittUnclassifiedIPv4 IPv62
AS204092Association GRIFONUnclassifiedIPv4 IPv62
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv62
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv62
AS24482SG.GSHostingIPv4 IPv62
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv62
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv41
AS50304Blix Solutions ASUnclassifiedIPv41
AS17639Converge ICT Solutions Inc.UnclassifiedIPv41
AS48185team.blue NVUnclassifiedIPv41
AS20485Joint Stock Company TransTeleComUnclassifiedIPv41
AS213241TECHIT.BE SRLResidentialIPv61
AS37100SEACOM LimitedUnclassifiedIPv41
AS56662Marcin GondekUnclassifiedIPv61
AS35625Eurofiber France SASHostingIPv41
AS3741Dimension DataUnclassifiedIPv41

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.

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

33 shown

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv643
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv65
AS2914NTT America, Inc.TransitIPv4 IPv63
AS39392SH.cz s.r.o.HostingIPv42
AS29632Netassist International EOODUnclassifiedIPv62
AS3257GTT Communications Inc.TransitIPv42
AS204092Association GRIFONUnclassifiedIPv4 IPv62
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv62
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv62
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv62
AS212024Marc SchmittUnclassifiedIPv4 IPv62
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv62
AS24482SG.GSHostingIPv4 IPv62
AS17639Converge ICT Solutions Inc.UnclassifiedIPv41
AS50304Blix Solutions ASUnclassifiedIPv41
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv41
AS56662Marcin GondekUnclassifiedIPv61
AS213241TECHIT.BE SRLResidentialIPv61
AS37100SEACOM LimitedUnclassifiedIPv41
AS3741Dimension DataUnclassifiedIPv41
AS20485Joint Stock Company TransTeleComUnclassifiedIPv41
AS35625Eurofiber France SASHostingIPv41
AS48185team.blue NVUnclassifiedIPv41

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.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS2484, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it. Recorded at 11 exchanges across 8 countries and 2 regions.

ExchangeLocationTheir addressMember ports
DE-CIX FrankfurtFrankfurt, Germany80.81.194.1551,073
LINX LON1London, United Kingdom195.66.227.3925
AMS-IX AmsterdamAmsterdam, Netherlands80.249.208.242893
Neutral Internet ExchangeAmsterdam, Netherlands193.239.116.211665
France-IX ParisParis, France37.49.236.20570
New York International Internet ExchangeNew York, United States198.32.160.148217
Peering.czPrague, Czech Republic185.0.21.22212
France-IX MarseilleMarseille, France37.49.232.36127
Torino Piemonte Exchange PointTorino, Italy194.116.96.208123
Luxembourg Internet ExchangeLuxembourg, Luxembourg188.93.170.29102
France-IX LyonLyon, France77.95.71.3494

Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.

Provenance

Where this comes from

Derived from routing tables collected at 2026-08-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.

Exchange presence comes from a separate dataset: the directory collected 2026-08-09 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,164 recorded member ports, licensed CC BY-NC-SA 3.0.

PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.