Network · data from 2026-11-12
AS59651 AS-QualityNetwork Alex Largman
Registry name: AS-QualityNetwork Alex Largman, IL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS59651, 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.
| 102.64.121.0/24 | No ROA | RIR databaseAFRINIC | 669 99% |
| 5.181.168.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 5.181.169.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 5.183.255.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 45.80.104.0/23 | Valid | RIR databaseRIPE | 669 99% |
| 62.233.39.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 122.8.92.0/22 | Valid | RIR databaseAPNIC | 669 99% |
| 130.49.8.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 130.49.9.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 130.49.10.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 130.49.11.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 146.19.140.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 170.168.28.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 170.168.29.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 170.168.30.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 170.168.31.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 170.168.96.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 170.168.97.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 170.168.98.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 170.168.99.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 170.168.172.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 170.168.173.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 170.168.174.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 170.168.175.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 170.168.240.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 170.168.241.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 170.168.242.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 170.168.243.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.89.42.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.89.43.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.94.32.0/22 | Valid | RIR databaseRIPE | 669 99% |
| 192.101.65.0/24 | Valid | RIR databaseARIN | 669 99% |
| 192.101.66.0/23 | Valid | RIR databaseARIN | 669 99% |
| 193.202.8.0/23 | Valid | RIR databaseRIPE | 669 99% |
| 213.232.120.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 213.232.122.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 122.8.44.0/22 | Valid | RIR databaseAPNIC | 668 99% |
| 185.68.152.0/22 | Valid | RIR databaseRIPE | 663 99% |
| 193.202.82.0/23 | Valid | RIR databaseRIPE | 663 99% |
AS-SET
AS59651 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 2 are in fix.csv.
- ROA: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 102.64.121.0/24 | No ROA covers it. Add a ROA for AS59651, maxLength 24. |
Route objects not announced
Route objects with origin AS59651 whose prefix no peer sees AS59651 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 146.19.39.0/24 | RIPE | Invalid: origin |
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.