bgpreport

Network · data from 2026-11-12

AS400899 CYCLONESERVERS-LLC - Cyclone Servers

Registry name: CYCLONESERVERS-LLC - Cyclone Servers, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS400899, 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.
212.189.8.0/24 Invalid: origin Other origin only 5 1%low visibility 4
2602:f50a::/40 No ROA Other IRR onlyRADB 635 100% 69
2602:fed2:7e01::/48 No ROA RIR databaseARIN, RADB 635 100% 70
2602:fed2:7e03::/48 No ROA RIR databaseARIN, RADB 635 100% 70
23.27.6.0/24 Valid RIR databaseARIN, RADB 673 100% 67
23.148.12.0/24 Valid RIR databaseARIN, RADB 673 100% 67
192.42.51.0/24 Valid RIR databaseARIN, RADB 673 100% 67
207.90.207.0/24 Valid RIR databaseARIN, RADB 673 100% 67

AS-SET

AS400899 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: origin1
  • ROA: none3
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin212.189.8.0/24ROAs covering it name AS834, AS3257, not AS400899. If AS400899 should announce it, add a ROA for AS400899.5 of 673
Route object: none212.189.8.0/24Route objects for it name AS834, AS3257. Add a route object with origin AS400899 in the RIR database for the space.5 of 673
ROA: none2602:f50a::/40No ROA covers it. Add a ROA for AS400899, maxLength 40.635 of 636
Route object: RIR2602:f50a::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2602:fed2:7e01::/48No ROA covers it. Add a ROA for AS400899, maxLength 48.635 of 636
ROA: none2602:fed2:7e03::/48No ROA covers it. Add a ROA for AS400899, maxLength 48.635 of 636

Route objects not announced

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

104.253.195.0/24ARINValid
2602:fed2:7082::/48RADBNo ROA

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.