Network · data from 2026-11-12
AS133846 IMLONGHAO
Registry name: IMLONGHAO-AS-AP - IMLONGHAO, CN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS133846, 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.
| 44.31.42.0/24 | No ROA | Other IRR onlyNTTCOM, RADB | 672 100% |
| 2602:feda:1bf::/48 | Valid | Other IRR onlyALTDB, NTTCOM, RADB | 635 100% |
| 2a09:b280:ff84::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2602:fab0:11::/48 | Valid | RIR databaseALTDB, ARIN, RADB | 635 100% |
| 2a09:b280:ff81::/48 | Valid | RIR databaseNTTCOM, RIPE | 635 100% |
| 2a09:b280:ff83::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a09:b280:ff85::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS133846: AS-IMLONGHAO. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS133846 isn't in the set, or no route object for AS133846 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS133846 in it | Not covered |
|---|---|---|---|---|---|
| AS-IMLONGHAO | RIPE | 1 | 1 | Yes | 0 |
| NTTCOM (also) | 1 | 1 | Yes | 0 |
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 10 are in fix.csv.
- ROA: none1
- Route object: RIR2
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 44.31.42.0/24 | No ROA covers it. Add a ROA for AS133846, maxLength 24. |
| Route object: RIR | 44.31.42.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2602:feda:1bf::/48 | Route object only in ALTDB, NTTCOM, RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS133846 whose prefix no peer sees AS133846 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2402:9e80:18::/48 | APNIC, NTTCOM | Valid |
| 2402:e380:302::/48 | APNIC | No ROA |
| 2602:fafd:f10::/48 | ARIN | Valid |
| 2602:feda:1b0::/44 | ARIN | Valid |
| 2602:feda:1b2::/48 | ALTDB, NTTCOM | Valid |
| 2a09:b280:ff80::/48 | ALTDB, NTTCOM, RADB, RIPE | Valid |
| 2a09:b280:ff82::/48 | 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.