bgpreport

Network · data from 2026-11-12

AS35895 CMMG-LTD - CMMG Ltd

Registry name: CMMG-LTD - CMMG Ltd, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS35895, 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.11.68.0/24 Valid Nonecovered by 204.11.68.0/22 668 99% 67
204.11.69.0/24 Valid Nonecovered by 204.11.68.0/22 668 99% 67
199.188.224.0/22 Valid RIR databaseARIN 668 99% 67
204.11.68.0/22 Valid RIR databaseARIN 668 99% 67
2602:ff5e::/36 Valid RIR databaseARIN 21 3%low visibility 13

AS-SET

AS35895 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 3 are in fix.csv.

  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none204.11.68.0/24No route object for it. A route object for 204.11.68.0/22 with origin AS35895 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35895 in the RIR database for the space.668 of 673
Route object: none204.11.69.0/24No route object for it. A route object for 204.11.68.0/22 with origin AS35895 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35895 in the RIR database for the space.668 of 673

Route objects not announced

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

209.142.125.0/24RADBNo 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.