Network · data from 2026-11-12
AS219001 E-LARGE E-LARGE (HONG KONG) LIMITED
Registry name: E-LARGE E-LARGE (HONG KONG) LIMITED, HK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS219001, 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.
| 91.243.119.0/24 | Valid | Other origin only | 672 100% |
| 79.182.48.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 217.216.203.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 141.11.66.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 178.95.39.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 216.75.143.0/24 | Valid | RIR databaseARIN, RADB | 672 100% |
| 217.216.204.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 79.182.134.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 2a0b:1f02:200::/40 | Valid | RIR databaseRIPE | 635 100% |
| 2a0b:1f02:300::/40 | Valid | RIR databaseRIPE | 635 100% |
| 2a0b:1f02:400::/40 | Valid | RIR databaseRIPE | 635 100% |
| 2a0b:1f02:500::/40 | Valid | RIR databaseRIPE | 635 100% |
| 2a0b:1f02::/40 | Valid | RIR databaseRIPE | 634 100% |
| 2a0b:1f02:100::/40 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS219001 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.
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 91.243.119.0/24 | Route objects for it name AS62257. Add a route object with origin AS219001 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS219001 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.