Network · data from 2026-11-12
AS142019 GRIL-AS-AP - GZ REMITTANCE (CHINA) INDUSTRY LIMITED
Registry name: GRIL-AS-AP - GZ REMITTANCE (CHINA) INDUSTRY LIMITED, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS142019, 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.129.208.0/22 | No ROA | RIR databaseRIPE | 665 99% |
| 103.205.18.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.205.19.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.240.148.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 160.238.64.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 160.238.65.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 160.238.67.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.245.3.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.209.223.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.150.75.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.93.17.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.142.28.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.153.22.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.154.84.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.155.225.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.249.104.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.249.105.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.249.106.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.8.138.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.74.54.0/24 | Valid | RIR databaseARIN | 670 100% |
| 45.135.39.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS142019 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 1 are in fix.csv.
- ROA: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.129.208.0/22 | No ROA covers it. Add a ROA for AS142019, maxLength 22. |
Route objects not announced
Every route object with origin AS142019 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.