bgpreport

Network · data from 2026-11-12

AS65650

Not in the RIR AS name list · not in PeeringDB

AS65650 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 0.0% RPKI valid · 0.0% with a route object
1IPv6 routes 0.0% RPKI valid · 0.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
1No ROA 2 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS65650, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS65650, 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.
103.246.64.0/23 Invalid: origin Other origin only 5 1%low visibility 5
2801:17:2800::/48 No ROA Other origin only 324 51% 63

AS-SET

AS65650 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 originAS65650AS65650 is Reserved 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 AS65650 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.