bgpreport

Network · data from 2026-11-12

AS5500 Chess

Registry name: CHESS Chess ICT Ltd, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS5500, 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.
80.92.144.0/20 No ROA None 672 100% 67
192.153.153.0/24 No ROA RIR databaseRIPE 673 100% 67
2a00:1160::/29 No ROA RIR databaseRIPE 593 93% 66
193.93.203.0/24 Valid RIR databaseRIPE 673 100% 67
193.108.218.0/24 Valid RIR databaseRIPE 673 100% 67
195.128.250.0/23 Valid RIR databaseRIPE 673 100% 67
195.206.192.0/19 Valid RIR databaseRIPE 673 100% 67
217.22.80.0/20 Valid RIR databaseRIPE 673 100% 67
195.72.113.0/24 Valid RIR databaseRIPE 647 96% 67
195.72.114.0/23 Valid RIR databaseRIPE 647 96% 67
2a02:56c0::/32 Valid RIR databaseRIPE 636 100% 67
2a05:aa40::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS5500: AS-CHESS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS5500 isn't in the set, or no route object for AS5500 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS5500 in itNot covered
AS-CHESS In no IRR database read today.

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

  • ROA: none3
  • Route object: none1
  • AS-SET: not found1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none80.92.144.0/20No ROA covers it. Add a ROA for AS5500, maxLength 20.672 of 673
Route object: none80.92.144.0/20No route object for it. Add a route object with origin AS5500 in the RIR database for the space.672 of 673
ROA: none192.153.153.0/24No ROA covers it. Add a ROA for AS5500, maxLength 24.673 of 673
ROA: none2a00:1160::/29No ROA covers it. Add a ROA for AS5500, maxLength 29.593 of 636
AS-SET: not foundAS-CHESSPeeringDB names AS-CHESS; no IRR database read has it.

Route objects not announced

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

193.109.50.0/23RIPENo 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.