bgpreport

Network · data from 2026-11-12

AS66666

Not in the RIR AS name list · not in PeeringDB

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS66666, 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.

123.242.148.0/22 No ROA Other origin only 286 42% 59
123.242.172.0/22 No ROA Other origin only 286 42% 59
123.242.176.0/22 No ROA Other origin only 286 42% 59
164.115.224.0/22 No ROA Other origin only 286 42% 59
164.115.228.0/22 No ROA Other origin only 286 42% 59
164.115.232.0/22 No ROA Other origin only 286 42% 59
164.115.236.0/22 No ROA Other origin only 286 42% 59
164.115.240.0/22 No ROA Other origin only 286 42% 59
164.115.244.0/22 No ROA Other origin only 286 42% 59
164.115.245.0/24 No ROA Other origin only 286 42% 59
164.115.248.0/22 No ROA Other origin only 286 42% 59
164.115.250.0/24 No ROA Other origin only 286 42% 59
164.115.252.0/22 No ROA Other origin only 286 42% 59
123.242.152.0/22 No ROA Other origin only 284 42% 59
123.242.156.0/22 No ROA Other origin only 284 42% 59
123.242.160.0/22 No ROA Other origin only 284 42% 59
123.242.164.0/22 No ROA Other origin only 284 42% 59
123.242.168.0/22 No ROA Other origin only 284 42% 59
123.242.180.0/22 No ROA Other origin only 273 41% 59
123.242.184.0/22 No ROA Other origin only 69 10% 41
123.242.188.0/22 No ROA Other origin only 69 10% 41
164.115.224.0/19 No ROA Other origin only 69 10% 41
164.115.251.0/24 No ROA Other origin only 1 0%low visibility 1

AS-SET

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

Route objects not announced

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