bgpreport

Network · data from 2026-11-12

AS55001 CYBERSTREET-NET - CyberStreet

Registry name: CYBERSTREET-NET - CyberStreet, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55001, 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.
204.145.237.0/24 No ROA None 672 100% 67
206.197.189.0/24 No ROA None 672 100% 67
162.219.208.0/22 No ROA None 669 99% 67
68.68.204.0/24 Valid RIR databaseARIN 672 100% 67
68.68.205.0/24 Valid RIR databaseARIN 671 100% 67
162.219.209.0/24 Valid RIR databaseARIN 671 100% 67
162.219.210.0/24 Valid RIR databaseARIN 671 100% 67
162.219.211.0/24 Valid RIR databaseARIN 671 100% 67

AS-SET

AS55001 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 8 are in fix.csv.

  • ROA: none3
  • Route object: none3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none204.145.237.0/24No ROA covers it. Add a ROA for AS55001, maxLength 24.672 of 673
Route object: none204.145.237.0/24No route object for it. Add a route object with origin AS55001 in the RIR database for the space.672 of 673
ROA: none206.197.189.0/24No ROA covers it. Add a ROA for AS55001, maxLength 24.672 of 673
Route object: none206.197.189.0/24No route object for it. Add a route object with origin AS55001 in the RIR database for the space.672 of 673
ROA: none162.219.208.0/22No ROA covers it. Add a ROA for AS55001, maxLength 22.669 of 673
Route object: none162.219.208.0/22No route object for it. Add a route object with origin AS55001 in the RIR database for the space.669 of 673

Route objects not announced

Route objects with origin AS55001 whose prefix no peer sees AS55001 announce. Many are kept on purpose (backup routes, space announced only in some places).

68.68.204.0/23ARINValid
162.219.208.0/24ARINValid

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.