Network · data from 2026-11-12
AS142578 ELARGEHONGKONGLI-AS-AP - E-Large (HongKong)
Registry name: ELARGEHONGKONGLI-AS-AP - E-Large (HongKong), HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS142578, 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.
| 45.93.18.0/23 | No ROA | None | 673 100% |
| 213.176.16.0/22 | No ROA | None | 673 100% |
| 213.176.76.0/22 | No ROA | None | 673 100% |
| 91.209.182.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 103.169.248.0/24 | No ROA | RIR databaseAPNIC | 673 100% |
| 103.169.249.0/24 | No ROA | RIR databaseAPNIC | 673 100% |
| 213.176.111.0/24 | Valid | Nonecovered by 213.176.96.0/20 | 673 100% |
| 85.92.113.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.107.219.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.176.8.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 213.176.32.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 213.176.80.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 213.176.96.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 45.93.18.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.93.19.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS142578 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 52 are in fix.csv.
- ROA: none6
- Route object: none4
- Route object: not announced42
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.93.18.0/23 | No ROA covers it. Add a ROA for AS142578, maxLength 23. |
| Route object: none | 45.93.18.0/23 | No route object for it. Add a route object with origin AS142578 in the RIR database for the space. |
| ROA: none | 213.176.16.0/22 | No ROA covers it. Add a ROA for AS142578, maxLength 22. |
| Route object: none | 213.176.16.0/22 | No route object for it. Add a route object with origin AS142578 in the RIR database for the space. |
| ROA: none | 213.176.76.0/22 | No ROA covers it. Add a ROA for AS142578, maxLength 22. |
| Route object: none | 213.176.76.0/22 | No route object for it. Add a route object with origin AS142578 in the RIR database for the space. |
| ROA: none | 91.209.182.0/24 | No ROA covers it. Add a ROA for AS142578, maxLength 24. |
| ROA: none | 103.169.248.0/24 | No ROA covers it. Add a ROA for AS142578, maxLength 24. |
| ROA: none | 103.169.249.0/24 | No ROA covers it. Add a ROA for AS142578, maxLength 24. |
| Route object: none | 213.176.111.0/24 | No route object for it. A route object for 213.176.96.0/20 with origin AS142578 covers it (filters allowing more-specifics accept it). Add a route object with origin AS142578 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS142578 whose prefix no peer sees AS142578 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.169.248.0/23 | APNIC | No ROA |
| 213.176.8.0/24 | RIPE | Valid |
| 213.176.9.0/24 | RIPE | Valid |
| 213.176.10.0/24 | RIPE | Valid |
| 213.176.11.0/24 | RIPE | Valid |
| 213.176.12.0/24 | RIPE | Valid |
| 213.176.13.0/24 | RIPE | Valid |
| 213.176.14.0/24 | RIPE | Valid |
| 213.176.15.0/24 | RIPE | Valid |
| 213.176.32.0/24 | RIPE | Valid |
| 213.176.33.0/24 | RIPE | Valid |
| 213.176.34.0/24 | RIPE | Valid |
| 213.176.35.0/24 | RIPE | Valid |
| 213.176.36.0/24 | RIPE | Valid |
| 213.176.37.0/24 | RIPE | Valid |
| 213.176.38.0/24 | RIPE | Valid |
| 213.176.39.0/24 | RIPE | Valid |
| 213.176.40.0/24 | RIPE | Valid |
| 213.176.41.0/24 | RIPE | Valid |
| 213.176.42.0/24 | RIPE | Valid |
| 213.176.43.0/24 | RIPE | Valid |
| 213.176.44.0/24 | RIPE | Valid |
| 213.176.45.0/24 | RIPE | Valid |
| 213.176.46.0/24 | RIPE | Valid |
| 213.176.47.0/24 | RIPE | Valid |
| 213.176.48.0/24 | RIPE | Valid |
| 213.176.49.0/24 | RIPE | Valid |
| 213.176.50.0/24 | RIPE | Valid |
| 213.176.51.0/24 | RIPE | Valid |
| 213.176.52.0/24 | RIPE | Valid |
| 213.176.53.0/24 | RIPE | Valid |
| 213.176.54.0/24 | RIPE | Valid |
| 213.176.55.0/24 | RIPE | Valid |
| 213.176.56.0/24 | RIPE | Valid |
| 213.176.57.0/24 | RIPE | Valid |
| 213.176.58.0/24 | RIPE | Valid |
| 213.176.59.0/24 | RIPE | Valid |
| 213.176.60.0/24 | RIPE | Valid |
| 213.176.61.0/24 | RIPE | Valid |
| 213.176.62.0/24 | RIPE | Valid |
| 213.176.63.0/24 | RIPE | Valid |
| 213.176.77.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.