Network · data from 2026-11-12
AS49959 readspeaker ReadSpeaker AB
Registry name: readspeaker ReadSpeaker AB, SE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49959, 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.
| 2a0d:9a81::/40 | No ROA | Other IRR onlyNTTCOM | 634 100% |
| 185.78.172.0/24 | No ROA | RIR databaseNTTCOM, RIPE | 673 100% |
| 185.78.173.0/24 | No ROA | RIR databaseNTTCOM, RIPE | 673 100% |
| 185.78.175.0/24 | No ROA | RIR databaseNTTCOM, RIPE | 673 100% |
| 185.78.174.0/24 | No ROA | RIR databaseNTTCOM, RIPE | 671 100% |
| 2a0d:9a80:200::/40 | No ROA | RIR databaseNTTCOM, RIPE | 636 100% |
| 2a0d:9a80:100::/40 | No ROA | RIR databaseNTTCOM, RIPE | 635 100% |
| 2a0d:9a80:300::/40 | No ROA | RIR databaseNTTCOM, RIPE | 635 100% |
| 2a0d:9a80:400::/40 | No ROA | RIR databaseRIPE | 635 100% |
AS-SET
AS49959 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 18 are in fix.csv.
- ROA: none9
- Route object: RIR1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a0d:9a81::/40 | No ROA covers it. Add a ROA for AS49959, maxLength 40. |
| Route object: RIR | 2a0d:9a81::/40 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| ROA: none | 185.78.172.0/24 | No ROA covers it. Add a ROA for AS49959, maxLength 24. |
| ROA: none | 185.78.173.0/24 | No ROA covers it. Add a ROA for AS49959, maxLength 24. |
| ROA: none | 185.78.175.0/24 | No ROA covers it. Add a ROA for AS49959, maxLength 24. |
| ROA: none | 185.78.174.0/24 | No ROA covers it. Add a ROA for AS49959, maxLength 24. |
| ROA: none | 2a0d:9a80:200::/40 | No ROA covers it. Add a ROA for AS49959, maxLength 40. |
| ROA: none | 2a0d:9a80:100::/40 | No ROA covers it. Add a ROA for AS49959, maxLength 40. |
| ROA: none | 2a0d:9a80:300::/40 | No ROA covers it. Add a ROA for AS49959, maxLength 40. |
| ROA: none | 2a0d:9a80:400::/40 | No ROA covers it. Add a ROA for AS49959, maxLength 40. |
Route objects not announced
Route objects with origin AS49959 whose prefix no peer sees AS49959 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.78.172.0/22 | NTTCOM, RIPE | No ROA |
| 2a0d:9a80::/29 | NTTCOM, RIPE | No ROA |
| 2a0d:9a80:100::/48 | NTTCOM, RIPE | No ROA |
| 2a0d:9a80:200::/48 | NTTCOM, RIPE | No ROA |
| 2a0d:9a80:300::/48 | NTTCOM, RIPE | No ROA |
| 2a0d:9a80:400::/48 | RIPE | No ROA |
| 2a0d:9a81::/48 | NTTCOM, RIPE | No ROA |
| 2a0d:9a81::/64 | RIPE | No ROA |
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.