bgpreport

Network · data from 2026-11-12

AS64860

Not in the RIR AS name list · not in PeeringDB

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS64860, 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.
79.179.64.0/24 Invalid: origin None 1 0%low visibility 1
79.179.65.0/24 Invalid: origin None 1 0%low visibility 1
79.179.66.0/24 Invalid: origin None 1 0%low visibility 1
79.179.67.0/24 Invalid: origin None 1 0%low visibility 1

AS-SET

AS64860 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 originAS64860AS64860 is Reserved for Private Use (RFC 6996) in IANA's AS number registries; 4 routes in the global table have it as their origin.

Route objects not announced

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