bgpreport

Network · data from 2026-11-12

AS28816 CHESS-ICT-MAN Chess ICT Ltd

Registry name: CHESS-ICT-MAN Chess ICT Ltd, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28816, 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.
195.72.113.0/24 Invalid: origin RIR databaseRIPE 26 4%low visibility 24
195.72.114.0/23 Invalid: origin RIR databaseRIPE 26 4%low visibility 24
2a00:1160::/29 No ROA Other origin only 41 6%low visibility 21

AS-SET

AS28816 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 4 are in fix.csv.

  • ROA: origin2
  • ROA: none1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin195.72.113.0/24ROAs covering it name AS5500, AS28818, not AS28816. If AS28816 should announce it, add a ROA for AS28816.26 of 673
ROA: origin195.72.114.0/23ROAs covering it name AS5500, AS28818, not AS28816. If AS28816 should announce it, add a ROA for AS28816.26 of 673
ROA: none2a00:1160::/29No ROA covers it. Add a ROA for AS28816, maxLength 29.41 of 636
Route object: none2a00:1160::/29Route objects for it name AS5500. Add a route object with origin AS28816 in the RIR database for the space.41 of 636

Route objects not announced

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