Network · data from 2026-11-12
AS139589
Not in the RIR AS name list · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS139589, 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.
| 2406:840:f200::/48 | No ROA | Nonecovered by 2406:840:f200::/44 | 1 0%low visibility |
| 2406:840:f203::/48 | No ROA | Other IRR onlyALTDB | 1 0%low visibility |
| 2a0e:aa01:1fff::/48 | Valid | RIR databaseRADB, RIPE | 1 0%low visibility |
AS-SET
AS139589 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 11 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: RIR1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2406:840:f200::/48 | No ROA covers it. Add a ROA for AS139589, maxLength 48. |
| Route object: none | 2406:840:f200::/48 | No route object for it. A route object for 2406:840:f200::/44 with origin AS139589 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139589 in the RIR database for the space. |
| ROA: none | 2406:840:f203::/48 | No ROA covers it. Add a ROA for AS139589, maxLength 48. |
| Route object: RIR | 2406:840:f203::/48 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS139589 whose prefix no peer sees AS139589 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 44.129.17.0/24 | ALTDB, RADB | No ROA |
| 2406:840:f200::/44 | ALTDB, RADB | No ROA |
| 2a0e:46c6:200::/48 | RIPE | No ROA |
| 2a0e:b107:170::/44 | RADB | No ROA |
| 2a0f:5707:ac00::/48 | RADB, RIPE | Valid |
| 2a0f:5707:ac01::/48 | RIPE | Valid |
| 2a0f:5707:ac02::/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.