asn.dev

Observed topology

AS198290 AS-GITS

Upstreams 23 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 18
Adjacent (IPv6) 14

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS198290: 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
AS6661POST LuxembourgResidentialIPv4 IPv672
AS2914NTT America, Inc.TransitIPv4 IPv623
AS6939Hurricane Electric LLCTransitIPv622
AS23764CTGNetUnclassifiedIPv412
AS29467LUXNETWORK S.A.UnclassifiedIPv4 IPv611
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv69
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv46
AS12552GlobalConnect ABUnclassifiedIPv46
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv63
AS45049Mohamed El BoudduntiResidentialIPv4 IPv63
AS48185team.blue NVUnclassifiedIPv4 IPv63
AS24482SG.GSHostingIPv4 IPv63
AS212024Marc SchmittUnclassifiedIPv4 IPv63
AS17639Converge ICT Solutions Inc.UnclassifiedIPv42
AS29632Netassist International EOODUnclassifiedIPv62
AS20485Joint Stock Company TransTeleComUnclassifiedIPv42
AS3303Swisscom (Schweiz) AGResidentialIPv42
AS37100SEACOM LimitedUnclassifiedIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42
AS20766Association "Gitoyen"UnclassifiedIPv42
AS48362Stadtwerke FeldkirchResidentialIPv61
AS56662Marcin GondekUnclassifiedIPv61
AS213241TECHIT.BE SRLResidentialIPv61

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

32 shown

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

ASNetworkTypeFamiliesPaths seen
AS6661POST LuxembourgResidentialIPv4 IPv672
AS2914NTT America, Inc.TransitIPv4 IPv623
AS6939Hurricane Electric LLCTransitIPv622
AS23764CTGNetUnclassifiedIPv412
AS29467LUXNETWORK S.A.UnclassifiedIPv4 IPv611
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv69
AS12552GlobalConnect ABUnclassifiedIPv46
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv46
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv63
AS45049Mohamed El BoudduntiResidentialIPv4 IPv63
AS212024Marc SchmittUnclassifiedIPv4 IPv63
AS24482SG.GSHostingIPv4 IPv63
AS48185team.blue NVUnclassifiedIPv4 IPv63
AS37100SEACOM LimitedUnclassifiedIPv42
AS3303Swisscom (Schweiz) AGResidentialIPv42
AS20485Joint Stock Company TransTeleComUnclassifiedIPv42
AS17639Converge ICT Solutions Inc.UnclassifiedIPv42
AS37721Virtual Technologies & SolutionsResidentialIPv42
AS20766Association "Gitoyen"UnclassifiedIPv42
AS29632Netassist International EOODUnclassifiedIPv62
AS56662Marcin GondekUnclassifiedIPv61
AS48362Stadtwerke FeldkirchResidentialIPv61
AS213241TECHIT.BE SRLResidentialIPv61

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 AS198290, 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 6 exchanges across 4 countries and 1 region.

ExchangeLocationTheir addressMember ports
DE-CIX FrankfurtFrankfurt, Germany80.81.196.671,073
France-IX ParisParis, France37.49.236.123570
Megaport Frankfurt IXFrankfurt, Germany2001:7f8:8:20:3:692:0:1114
Luxembourg Internet ExchangeLuxembourg, Luxembourg188.93.170.51102
Megaport Dusseldorf IXDüsseldorf, Germany194.146.118.14298
Belgian National Internet ExchangeBrussels, Belgium194.53.172.8482

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-08 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,137 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.