Observed topology
AS33991 IGRA-SERVICE-AS IGRA-SERVICE LLC
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS33991: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 | 690 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 427 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 241 |
| AS8359 | MTS PJSC | Mobile | IPv4 | 140 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 52 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 36 |
| AS48858 | JSC "ER-Telecom Holding" | Unclassified | IPv4 IPv6 | 30 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 25 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 25 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 24 |
Transit
Downstream networks
Networks for which AS33991 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS209372 | WS Telecom Inc | Unclassified | IPv4 IPv6 | 1,803 |
| AS57261 | YarTV Ltd. | Unclassified | IPv4 | 264 |
| AS8496 | Optizon Ltd | Hosting | IPv4 IPv6 | 194 |
| AS209687 | IGRA-SERVICE LLC | Unclassified | IPv4 | 188 |
| AS43238 | Optizon Ltd | Unclassified | IPv4 IPv6 | 101 |
| AS30920 | Mobilon Telecommunications LLC | Unclassified | IPv4 | 70 |
| AS56326 | 9-ka.ru Ltd. | Unclassified | IPv4 | 66 |
| AS207978 | FITS KNTS SO RAN | Unclassified | IPv4 | 30 |
| AS41831 | PRAVOVED LLC | Unclassified | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS33991 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 1,824 |
| AS209372 | WS Telecom Inc | Unclassified | IPv4 IPv6 | 1,803 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 1,190 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 | 1,093 |
| AS57261 | YarTV Ltd. | Unclassified | IPv4 | 264 |
| AS8359 | MTS PJSC | Mobile | IPv4 | 233 |
| AS209687 | IGRA-SERVICE LLC | Unclassified | IPv4 | 230 |
| AS8496 | Optizon Ltd | Hosting | IPv4 IPv6 | 216 |
| AS43238 | Optizon Ltd | Unclassified | IPv4 IPv6 | 193 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 74 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.40M 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.