Observed topology
AS57724 DDOS-GUARD
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS57724: 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 |
|---|---|---|---|---|
| AS59692 | IQWeb FZ-LLC | Unclassified | IPv4 IPv6 | 1,706 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 87 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 36 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 34 |
| AS12552 | GlobalConnect AB | Unclassified | IPv4 | 32 |
| AS56655 | Gigahost AS | Unclassified | IPv4 IPv6 | 32 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 4 |
| AS24482 | SG.GS | Hosting | IPv4 | 2 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 2 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 2 |
Transit
Downstream networks
Networks for which AS57724 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS57271 | BitWeb LLC | Unclassified | IPv4 IPv6 | 318 |
| AS8904 | Bank of Russia | Unclassified | IPv4 | 159 |
| AS59692 | IQWeb FZ-LLC | Unclassified | IPv4 | 91 |
| AS9123 | JSC "TIMEWEB" | Hosting | IPv4 | 75 |
| AS43045 | Svyaz-Holding Ltd. | Residential | IPv4 | 64 |
| AS198255 | JSC SETTLEMENT SOLUTIONS | Unclassified | IPv4 | 44 |
| AS200436 | Patron Technology Persia Ltd | Unclassified | IPv4 | 36 |
| AS57043 | HOSTKEY B.V. | Hosting | IPv4 | 35 |
| AS50867 | HOSTKEY B.V. | Hosting | IPv4 | 30 |
| AS50340 | JSC Selectel | Hosting | IPv4 | 27 |
Adjacency
Adjacent networks
Every AS seen directly next to AS57724 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS39561 | "Domain names registrar REG.RU", Ltd | Unclassified | IPv4 IPv6 | 2,035 |
| AS59692 | IQWeb FZ-LLC | Unclassified | IPv4 IPv6 | 1,797 |
| AS12389 | PJSC Rostelecom | Residential | IPv4 IPv6 | 1,481 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 417 |
| AS3216 | PJSC "Vimpelcom" | Mobile | IPv4 IPv6 | 404 |
| AS56655 | Gigahost AS | Unclassified | IPv4 IPv6 | 397 |
| AS12552 | GlobalConnect AB | Unclassified | IPv4 | 388 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 356 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 335 |
| AS57271 | BitWeb LLC | Unclassified | IPv4 IPv6 | 318 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.25M 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.