bgpreport

Network · data from 2026-11-12

AS200282 CIMAX-LLC CIMAX Technologies LLC

Registry name: CIMAX-LLC CIMAX Technologies LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS200282, 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.
2a0f:85c1:cf5::/48 Invalid: origin RIR databaseRIPE 56 9%low visibility 32
89.46.1.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
2a06:9801:5f::/48 Valid RIR databaseRIPE 634 100% 69
2a13:9500:14b::/48 Valid RIR databaseRIPE 634 100% 69

AS-SET

AS200282 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.

  • ROA: origin1
ChangePrefix or setDetailFull-table peers
ROA: origin2a0f:85c1:cf5::/48ROAs covering it name AS205374, not AS200282. If AS200282 should announce it, add a ROA for AS200282.56 of 636

Route objects not announced

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