asn.dev

Observed topology

AS41000 FREETHOUGHT-AS

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS41000: 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 IPv6229
AS6939Hurricane Electric LLCTransitIPv4 IPv6143
AS174Cogent Communications, LLCTransitIPv4 IPv6112
AS34549meerfarbig GmbH & Co. KGHostingIPv440
AS50304Blix Solutions ASUnclassifiedIPv420
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv612
AS24482SG.GSHostingIPv4 IPv612
AS48185team.blue NVUnclassifiedIPv4 IPv612
AS12552GlobalConnect ABUnclassifiedIPv410
AS57463NetIX Communications JSCUnclassifiedIPv410
AS37721Virtual Technologies & SolutionsResidentialIPv410
AS48362Stadtwerke FeldkirchResidentialIPv410
AS29169GANDI SASHostingIPv410
AS12779IT.Gate S.p.A.UnclassifiedIPv410
AS7575Australian Academic and Research Network (AARNet)EducationIPv410
AS3741Dimension DataUnclassifiedIPv410
AS17639Converge ICT Solutions Inc.UnclassifiedIPv410
AS31500Global Network Management IncUnclassifiedIPv410
AS37100SEACOM LimitedUnclassifiedIPv410
AS20562Broadband Hosting B.V.HostingIPv45

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 AS41000 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

26 shown

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv6229
AS6939Hurricane Electric LLCTransitIPv4 IPv6143
AS174Cogent Communications, LLCTransitIPv4 IPv6112
AS34549meerfarbig GmbH & Co. KGHostingIPv440
AS50304Blix Solutions ASUnclassifiedIPv420
AS48185team.blue NVUnclassifiedIPv4 IPv612
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv612
AS24482SG.GSHostingIPv4 IPv612
AS12779IT.Gate S.p.A.UnclassifiedIPv410
AS48362Stadtwerke FeldkirchResidentialIPv410
AS29169GANDI SASHostingIPv410
AS7575Australian Academic and Research Network (AARNet)EducationIPv410
AS17639Converge ICT Solutions Inc.UnclassifiedIPv410
AS37721Virtual Technologies & SolutionsResidentialIPv410
AS57463NetIX Communications JSCUnclassifiedIPv410
AS37100SEACOM LimitedUnclassifiedIPv410
AS3741Dimension DataUnclassifiedIPv410
AS12552GlobalConnect ABUnclassifiedIPv410
AS31500Global Network Management IncUnclassifiedIPv410
AS20562Broadband Hosting B.V.HostingIPv45

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 AS41000, 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 3 exchanges across 1 country and 1 region.

ExchangeLocationTheir addressMember ports
LINX LON1London, United Kingdom195.66.226.215925
London Network Access PointLondon, United Kingdom5.57.81.150316
LINX ManchesterManchester, United Kingdom195.66.244.78145

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.