asn.dev

Observed topology

AS204188 AS-ITSG

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS204188: 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
AS5405Inter.link GmbHUnclassifiedIPv4 IPv675
AS33891Core-Backbone GmbHHostingIPv4 IPv658
AS6939Hurricane Electric LLCTransitIPv4 IPv639
AS1299Arelion Sweden ABTransitIPv4 IPv632
AS3356Level 3 Parent, LLCTransitIPv424
AS3257GTT Communications Inc.TransitIPv418
AS24482SG.GSHostingIPv4 IPv65
AS29632Netassist International EOODUnclassifiedIPv64
AS57463NetIX Communications JSCUnclassifiedIPv43
AS37100SEACOM LimitedUnclassifiedIPv43

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

15 shown

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

ASNetworkTypeFamiliesPaths seen
AS5405Inter.link GmbHUnclassifiedIPv4 IPv675
AS33891Core-Backbone GmbHHostingIPv4 IPv658
AS6939Hurricane Electric LLCTransitIPv4 IPv639
AS1299Arelion Sweden ABTransitIPv4 IPv632
AS3356Level 3 Parent, LLCTransitIPv424
AS3257GTT Communications Inc.TransitIPv418
AS24482SG.GSHostingIPv4 IPv65
AS29632Netassist International EOODUnclassifiedIPv64
AS57463NetIX Communications JSCUnclassifiedIPv43
AS37100SEACOM LimitedUnclassifiedIPv43

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

ExchangeLocationTheir addressMember ports
Megaport Frankfurt IXFrankfurt, Germany62.69.146.137114
Megaport Dusseldorf IXDüsseldorf, Germany194.146.118.17498
Megaport Hamburg IXHamburg, Germany193.42.155.8062
Megaport Berlin IXBerlin, Germany194.9.117.10145
Megaport Munich IXMunich, Germany194.59.190.9938

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.