asn.dev

Observed topology

AS12732 GUTCON-NET Carrier51 GmbH, GutCon GmbH

Upstreams 22 carry this network
Downstreams 7 this network carries
Adjacent (IPv4) 27
Adjacent (IPv6) 26

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS12732: 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
AS30742Bremen Briteline GmbHUnclassifiedIPv4 IPv6211
AS3356Level 3 Parent, LLCTransitIPv4 IPv6146
AS174Cogent Communications, LLCTransitIPv4 IPv689
AS6939Hurricane Electric LLCTransitIPv4 IPv660
AS5405Inter.link GmbHUnclassifiedIPv4 IPv624
AS3257GTT Communications Inc.TransitIPv4 IPv613
AS9002RETN LimitedUnclassifiedIPv612
AS34549meerfarbig GmbH & Co. KGHostingIPv48
AS24482SG.GSHostingIPv4 IPv65
AS8218Zayo Infrastructure France SAUnclassifiedIPv63
AS34019Hivane AssociationUnclassifiedIPv42
AS57463NetIX Communications JSCUnclassifiedIPv42
AS12552GlobalConnect ABUnclassifiedIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42
AS48362Stadtwerke FeldkirchResidentialIPv42
AS212024Marc SchmittUnclassifiedIPv42
AS37100SEACOM LimitedUnclassifiedIPv42
AS17639Converge ICT Solutions Inc.UnclassifiedIPv42
AS20485Joint Stock Company TransTeleComUnclassifiedIPv42
AS12779IT.Gate S.p.A.UnclassifiedIPv41
AS12859BIT BVHostingIPv41
AS1836green.ch AGResidentialIPv41

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

ASNetworkTypeFamiliesPaths seen
AS8875sinma GmbHHostingIPv4 IPv6945
AS44716D-hosting die Rackspace & Connectivity GmbHHostingIPv4560
AS15657Speedbone Internet & Connectivity GmbHHostingIPv4 IPv6344
AS203965FRITZ! Technology GmbHUnclassifiedIPv4 IPv6222
AS39614Dawico Deutschland GmbHUnclassifiedIPv4 IPv6116
AS25516init AG fuer digitale KommunikationHostingIPv4 IPv6111
AS201257Johannes BehrndtUnclassifiedIPv634

Adjacency

Adjacent networks

53 shown

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

ASNetworkTypeFamiliesPaths seen
AS8875sinma GmbHHostingIPv4 IPv6945
AS3356Level 3 Parent, LLCTransitIPv4 IPv6632
AS5405Inter.link GmbHUnclassifiedIPv4 IPv6567
AS44716D-hosting die Rackspace & Connectivity GmbHHostingIPv4560
AS174Cogent Communications, LLCTransitIPv4 IPv6430
AS6939Hurricane Electric LLCTransitIPv4 IPv6406
AS15657Speedbone Internet & Connectivity GmbHHostingIPv4 IPv6353
AS3257GTT Communications Inc.TransitIPv4 IPv6263
AS203965FRITZ! Technology GmbHUnclassifiedIPv4 IPv6222
AS30742Bremen Briteline GmbHUnclassifiedIPv4 IPv6211
AS39614Dawico Deutschland GmbHUnclassifiedIPv4 IPv6122
AS25516init AG fuer digitale KommunikationHostingIPv4 IPv6111
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv682
AS24482SG.GSHostingIPv4 IPv645
AS29632Netassist International EOODUnclassifiedIPv635
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv635
AS201257Johannes BehrndtUnclassifiedIPv634
AS9002RETN LimitedUnclassifiedIPv628
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv628
AS8218Zayo Infrastructure France SAUnclassifiedIPv4 IPv625
AS34019Hivane AssociationUnclassifiedIPv4 IPv622
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv621
AS213241TECHIT.BE SRLResidentialIPv619
AS212024Marc SchmittUnclassifiedIPv4 IPv618
AS12859BIT BVHostingIPv4 IPv613
AS1836green.ch AGResidentialIPv4 IPv613
AS56662Marcin GondekUnclassifiedIPv612
AS20485Joint Stock Company TransTeleComUnclassifiedIPv49
AS12552GlobalConnect ABUnclassifiedIPv48
AS37100SEACOM LimitedUnclassifiedIPv48
AS57463NetIX Communications JSCUnclassifiedIPv48
AS12779IT.Gate S.p.A.UnclassifiedIPv41

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 AS12732, 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
DE-CIX FrankfurtFrankfurt, Germany80.81.196.141,073
Berlin Commercial Internet ExchangeBerlin, Germany193.178.185.1152
Megaport Dusseldorf IXDüsseldorf, Germany194.146.118.3098
Megaport Hamburg IXHamburg, Germany193.42.155.762
Megaport Berlin IXBerlin, Germany194.9.117.245

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.