Network · data from 2026-11-12
AS15143
Not in the RIR AS name list · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS15143, 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.
| 2a0b:4340:5b0::/48 | No ROA | Nonecovered by 2a0b:4340:5b0::/44 | 26 4%low visibility |
| 2a0b:4340:5b0::/44 | No ROA | RIR databaseRIPE | 636 100% |
| 151.242.224.0/24 | Valid | Other IRR onlyRADB | 403 60% |
| 151.242.224.0/23 | Valid | RIR databaseRADB, RIPE | 672 100% |
AS-SET
AS15143 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 8 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: RIR1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a0b:4340:5b0::/48 | No ROA covers it. Add a ROA for AS15143, maxLength 48. |
| Route object: none | 2a0b:4340:5b0::/48 | No route object for it. A route object for 2a0b:4340:5b0::/44 with origin AS15143 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15143 in the RIR database for the space. |
| ROA: none | 2a0b:4340:5b0::/44 | No ROA covers it. Add a ROA for AS15143, maxLength 44. |
| Route object: RIR | 151.242.224.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS15143 whose prefix no peer sees AS15143 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.99.60.0/23 | APNIC, RADB | Valid |
| 103.99.60.0/24 | APNIC | Valid |
| 103.99.61.0/24 | APNIC | Valid |
| 151.242.225.0/24 | RADB | 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.