Network · data from 2026-11-12
AS140915
Not in the RIR AS name list · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS140915, 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:e234::/48 | Invalid: origin | Other origin only | 9 1%low visibility |
AS-SET
AS140915 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 7 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2406:840:e234::/48 | ROAs covering it name AS204244, not AS140915. If AS140915 should announce it, add a ROA for AS140915. |
| Route object: none | 2406:840:e234::/48 | Route objects for it name AS204244. Add a route object with origin AS140915 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS140915 whose prefix no peer sees AS140915 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2602:f92a:e100::/44 | ARIN | Valid |
| 2602:f92a:f000::/40 | ARIN | Valid |
| 2a0f:9400:6110::/48 | RIPE | Valid |
| 2a13:a5c3:ff10::/44 | RIPE | Valid |
| 2a13:a5c3:ff11::/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.