Observed topology
AS12555 IMAQLIQ iqdata.center
Hosting RIPE Content
Transit
Upstream networks
Networks observed carrying traffic for AS12555: 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 |
|---|---|---|---|---|
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 422 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 373 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 242 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 193 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 175 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 28 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 28 |
| AS56655 | Gigahost AS | Unclassified | IPv4 IPv6 | 28 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 28 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 26 |
Transit
Downstream networks
Networks for which AS12555 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS44676 | Perviy TSOD LLC | Unclassified | IPv4 | 660 |
| AS48430 | Perviy TSOD LLC | Unclassified | IPv4 IPv6 | 309 |
| AS51783 | The Center of Dedicated Servers LLC | Unclassified | IPv4 IPv6 | 287 |
| AS198070 | LLC "Pudlink" | Unclassified | IPv4 | 174 |
| AS3227 | Git In Sky LLC | Unclassified | IPv4 | 60 |
| AS16222 | Fort Ltd | Unclassified | IPv4 | 60 |
| AS49905 | Joint Stock Company "Primekartonpak" | Unclassified | IPv4 | 60 |
| AS200624 | LLC-RZD-PARTNER | Unclassified | IPv4 | 60 |
| AS210827 | Aurora Telecom LLC | Unclassified | IPv4 | 60 |
| AS212247 | IT Services Ltd | Unclassified | IPv4 | 60 |
Adjacency
Adjacent networks
Every AS seen directly next to AS12555 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS31133 | PJSC MegaFon | Mobile | IPv4 IPv6 | 837 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 IPv6 | 819 |
| AS44676 | Perviy TSOD LLC | Unclassified | IPv4 | 660 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 IPv6 | 482 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 446 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 419 |
| AS48430 | Perviy TSOD LLC | Unclassified | IPv4 IPv6 | 309 |
| AS51783 | The Center of Dedicated Servers LLC | Unclassified | IPv4 IPv6 | 287 |
| AS198070 | LLC "Pudlink" | Unclassified | IPv4 | 174 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 65 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.