Observed topology
AS8990 AHRT-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS8990: 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.
Transit
Downstream networks
Networks for which AS8990 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS41885 | Hungaro DigiTel Tavkozlesi Korlatolt Felelossegu Tarsasag | Unclassified | IPv4 | 291 |
| AS35792 | Takinfo Kft | Unclassified | IPv4 | 80 |
| AS41251 | XELLA Hungary Ltd | Unclassified | IPv4 | 58 |
| AS47324 | KDB Bank Hungary Ltd. | Unclassified | IPv4 | 58 |
| AS205914 | Nemzeti Media- es Hirkozlesi Hatosag | Unclassified | IPv4 | 58 |
| AS210611 | HFC Technics Ipari Kereskedelmi es Szolgaltato Kft. | Unclassified | IPv6 | 32 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8990 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 845 |
| AS41885 | Hungaro DigiTel Tavkozlesi Korlatolt Felelossegu Tarsasag | Unclassified | IPv4 | 291 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 279 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 241 |
| AS35792 | Takinfo Kft | Unclassified | IPv4 | 80 |
| AS210611 | HFC Technics Ipari Kereskedelmi es Szolgaltato Kft. | Unclassified | IPv4 IPv6 | 77 |
| AS41251 | XELLA Hungary Ltd | Unclassified | IPv4 | 58 |
| AS47324 | KDB Bank Hungary Ltd. | Unclassified | IPv4 | 58 |
| AS205914 | Nemzeti Media- es Hirkozlesi Hatosag | Unclassified | IPv4 | 58 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 44 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-16 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.23M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.
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. 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.
Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.