Network · data from 2026-11-12
AS62250 ATINET SINA ATINET Company (Ltd)
Registry name: ATINET SINA ATINET Company (Ltd), IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS62250, 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.
| 185.110.253.0/24 | Valid | Nonecovered by 185.110.252.0/23 | 670 100% |
| 185.110.254.0/24 | Valid | Nonecovered by 185.110.254.0/23 | 670 100% |
| 185.118.154.0/24 | Valid | Nonecovered by 185.118.154.0/23 | 670 100% |
| 185.110.252.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.110.255.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.118.152.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 185.118.152.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.118.153.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.118.155.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.119.164.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 185.119.165.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.119.166.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.119.167.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.166.60.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 185.209.188.0/22 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS62250 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 16 are in fix.csv.
- Route object: none3
- Route object: not announced13
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.110.253.0/24 | No route object for it. A route object for 185.110.252.0/23 with origin AS62250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62250 in the RIR database for the space. |
| Route object: none | 185.110.254.0/24 | No route object for it. A route object for 185.110.254.0/23 with origin AS62250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62250 in the RIR database for the space. |
| Route object: none | 185.118.154.0/24 | No route object for it. A route object for 185.118.154.0/23 with origin AS62250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62250 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS62250 whose prefix no peer sees AS62250 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2.182.0.0/19 | RIPE | Invalid: origin |
| 89.36.48.0/21 | RIPE | Invalid: origin |
| 89.36.56.0/21 | RIPE | Invalid: origin |
| 89.38.184.0/22 | RIPE | Invalid: origin |
| 89.38.188.0/22 | RIPE | Invalid: origin |
| 89.38.192.0/21 | RIPE | Invalid: origin |
| 185.110.252.0/22 | RIPE | Valid |
| 185.110.252.0/23 | RIPE | Invalid: maxLength |
| 185.110.254.0/23 | RIPE | Invalid: maxLength |
| 185.118.152.0/23 | RIPE | Invalid: maxLength |
| 185.118.154.0/23 | RIPE | Invalid: maxLength |
| 185.119.164.0/23 | RIPE | Invalid: maxLength |
| 185.119.166.0/23 | RIPE | Valid |
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.