Network · data from 2026-11-12
AS64501
Not in the RIR AS name list · not in PeeringDB
AS64501 is Reserved for use in documentation and sample code (RFC 5398) 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 AS64501, 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.
| 200.76.152.0/24 | Invalid: origin | Other origin only | 31 5%low visibility |
| 200.94.67.0/24 | Invalid: origin | Other origin only | 31 5%low visibility |
AS-SET
AS64501 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 1 are in fix.csv.
- Bogon origin1
| Change | Prefix or set | Detail |
|---|---|---|
| Bogon origin | AS64501 | AS64501 is Reserved for use in documentation and sample code (RFC 5398) in IANA's AS number registries; 2 routes in the global table have it as their origin. |
Route objects not announced
Every route object with origin AS64501 is announced.
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.