Observed topology
AS1121 IDDQD-AS
Unclassified RIPE Route Server
Transit
Upstream networks
Networks observed carrying traffic for AS1121: 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.
Transit
Downstream networks
Networks for which AS1121 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9146 | BH Telecom d.d. Sarajevo | Residential | IPv4 | 12 |
| AS25255 | Hutchison Drei Austria GmbH | Residential | IPv4 | 8 |
| AS2686 | AT&T Enterprises, LLC | Unclassified | IPv4 | 7 |
| AS51265 | Mass Response Service GmbH | Residential | IPv4 | 5 |
| AS8245 | Video-Broadcast GmbH | Unclassified | IPv4 | 4 |
| AS48943 | KAPPER NETWORK-COMMUNICATIONS GmbH | Unclassified | IPv4 | 4 |
| AS2614 | Agentia de Administrare a Retelei Nationale de Informatica pentru Educatie si Cercetare | Education | IPv4 | 2 |
| AS25467 | Akton d.o.o. | Unclassified | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS1121 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS23764 | CTGNet | Unclassified | IPv4 | 46 |
| AS9146 | BH Telecom d.d. Sarajevo | Residential | IPv4 | 14 |
| AS25255 | Hutchison Drei Austria GmbH | Residential | IPv4 | 8 |
| AS2686 | AT&T Enterprises, LLC | Unclassified | IPv4 | 7 |
| AS51265 | Mass Response Service GmbH | Residential | IPv4 | 5 |
| AS8245 | Video-Broadcast GmbH | Unclassified | IPv4 | 4 |
| AS48943 | KAPPER NETWORK-COMMUNICATIONS GmbH | Unclassified | IPv4 | 4 |
| AS2614 | Agentia de Administrare a Retelei Nationale de Informatica pentru Educatie si Cercetare | Education | IPv4 | 2 |
| AS13004 | Serbian Open Exchange DOO | Unclassified | IPv4 | 1 |
| AS25467 | Akton d.o.o. | Unclassified | IPv4 | 1 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 12:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.