Observed topology

AS39533 Asympto Networks Kft.

Upstreams 0 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 2

Adjacent (IPv6) 0

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS39533: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

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 AS39533 was observed as the last hop before the origin, meaning it appears to provide them transit.

AS	Network	Type	Families	Paths seen
AS6736	Institute for Research in Fundamental Sciences	Education	IPv4	900

Adjacency

Adjacent networks

2 shown

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

AS	Network	Type	Families	Paths seen
AS6736	Institute for Research in Fundamental Sciences	Education	IPv4	8,471
AS2914	NTT America, Inc.	Transit	IPv4	8,471

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 AS39533, 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 17 exchanges across 7 countries and 2 regions.

Exchange	Location	Their address	Member ports
4b42 Internet Exchange Point	Zurich, Switzerland	185.1.125.133	1,242
DE-CIX Frankfurt	Frankfurt, Germany	2001:7f8::9a6d:0:1	1,073
France-IX Paris	Paris, France	37.49.237.228	570
DE-CIX New York	New York, United States	2001:504:36::9a6d:0:1	279
DE-CIX Madrid	Madrid, Spain	2001:7f8:a0::9a6d:0:1	229
DE-CIX Dusseldorf	Düsseldorf, Germany	2001:7f8:9e::9a6d:0:1	225
DE-CIX Munich	Munich, Germany	2001:7f8:44::9a6d:0:1	207
DE-CIX Hamburg	Hamburg, Germany	185.1.210.121	195
Securebit Internet Exchange Zurich	Zurich, Switzerland	185.1.135.18	156
Berlin Commercial Internet Exchange	Berlin, Germany	193.178.185.129	150
DE-CIX Marseille	Marseille, France	2001:7f8:36::9a6d:0:1	113
CH Swiss Internet Exchange	Zurich, Switzerland	185.1.59.149	111
Massachusetts Internet Exchange	Boston, United States	206.53.143.70	72
DE-CIX Istanbul	Istanbul, Turkey	2001:7f8:3f::9a6d:0:2	67
DE-CIX Lisbon	Lisbon, Portugal	2001:7f8:d5::9a6d:0:2	63
LINX NoVa	Reston, United States	206.55.196.102	48
Community-IX.ch	Zurich, Switzerland	185.1.105.12	24

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.