bgpreport

Network · data from 2026-11-12

AS64631

Not in the RIR AS name list · not in PeeringDB

AS64631 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.

5IPv4 routes 0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
5No ROA 5 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS64631, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS64631, 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.
41.173.60.0/23 No ROA None 38 6%low visibility 21
41.173.200.0/22 No ROA None 38 6%low visibility 21
41.173.224.0/22 No ROA None 38 6%low visibility 21
41.174.100.0/22 No ROA Other origin only 38 6%low visibility 21
41.174.112.0/21 No ROA Other origin only 38 6%low visibility 21

AS-SET

AS64631 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
ChangePrefix or setDetailFull-table peers
Bogon originAS64631AS64631 is Reserved for Private Use (RFC 6996) in IANA's AS number registries; 5 routes in the global table have it as their origin.

Route objects not announced

Every route object with origin AS64631 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.