Network · data from 2026-11-12
AS198753 STEPAN ODINTSOV PR BEOGRAD
Registry name: STEPAN-ODINTSOV-PR-BEOGRAD-AS Stepan Odintsov trading as STEPAN ODINTSOV PR BEOGRAD, RS · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS198753, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 62.192.178.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 62.192.179.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 62.192.176.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 62.192.177.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 104.222.176.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 104.249.42.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.228.16.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.228.17.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.228.18.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.202.204.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 155.133.86.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.197.28.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.218.52.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.218.54.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.218.55.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.244.121.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.244.122.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.244.123.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.217.98.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.217.99.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.217.100.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.217.102.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.217.103.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.217.224.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2.59.159.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 5.253.238.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 77.75.52.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 77.75.53.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 77.75.54.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 77.75.55.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 85.255.81.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 85.255.82.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 85.255.83.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.197.29.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 194.31.103.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 5.253.239.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.218.53.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 194.31.100.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 194.31.101.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 194.31.102.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 217.217.101.0/24 | Valid | RIR databaseRIPE | 669 99% |
AS-SET
AS198753's PeeringDB record names no AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS198753 is announced.
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.