bgpreport

Network · data from 2026-11-12

AS65593

Not in the RIR AS name list · not in PeeringDB

AS65593 is Reserved in IANA's AS number registries. The routes below have it as their origin anyway, as seen by the collectors' peers.

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS65593, 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.
84.44.80.0/24 Valid None 321 48% 64

AS-SET

AS65593 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 originAS65593AS65593 is Reserved in IANA's AS number registries; 1 routes in the global table have it as their origin.

Route objects not announced

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