Network · data from 2026-11-12
AS65512
Not in the RIR AS name list · not in PeeringDB
AS65512 is Reserved for Private Use (RFC 6996) in IANA's AS number registries. The routes below have it as their origin anyway, as seen by the collectors' peers.
Announced routes
Every prefix a peer of the route collectors sees with origin AS65512, 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.
| 2405:7600:4620::/44 | Invalid: origin | None | 0 0%low visibility |
| 2405:7600:4630::/44 | Invalid: origin | None | 0 0%low visibility |
AS-SET
AS65512 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 4 are in fix.csv.
- Bogon origin1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Bogon origin | AS65512 | AS65512 is Reserved for Private Use (RFC 6996) in IANA's AS number registries; 2 routes in the global table have it as their origin. |
Route objects not announced
Route objects with origin AS65512 whose prefix no peer sees AS65512 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 140.168.128.0/19 | APNIC | Valid |
| 140.168.135.0/24 | APNIC | Valid |
| 140.168.160.0/19 | APNIC | 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.