bgpreport

Network · data from 2026-11-12

AS55022 QUESYS-AS1 - Quesys Inc.

Registry name: QUESYS-AS1 - Quesys Inc., CA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55022, 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.
2602:fffd:800::/37 No ROA Nonecovered by 2602:fffd::/36 605 95% 67
198.153.76.0/24 No ROA Other IRR onlyRADB 673 100% 67
198.153.77.0/24 No ROA Other IRR onlyRADB 673 100% 67
198.153.78.0/24 No ROA Other IRR onlyRADB 673 100% 67
198.153.79.0/24 No ROA Other IRR onlyRADB 673 100% 67
2602:fffd::/37 No ROA Other IRR onlyRADB 635 100% 69

AS-SET

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

  • ROA: none6
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2602:fffd:800::/37No ROA covers it. Add a ROA for AS55022, maxLength 37.605 of 636
Route object: none2602:fffd:800::/37No route object for it. A route object for 2602:fffd::/36 with origin AS55022 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55022 in the RIR database for the space.605 of 636
ROA: none198.153.76.0/24No ROA covers it. Add a ROA for AS55022, maxLength 24.673 of 673
Route object: RIR198.153.76.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none198.153.77.0/24No ROA covers it. Add a ROA for AS55022, maxLength 24.673 of 673
Route object: RIR198.153.77.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none198.153.78.0/24No ROA covers it. Add a ROA for AS55022, maxLength 24.673 of 673
Route object: RIR198.153.78.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none198.153.79.0/24No ROA covers it. Add a ROA for AS55022, maxLength 24.673 of 673
Route object: RIR198.153.79.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2602:fffd::/37No ROA covers it. Add a ROA for AS55022, maxLength 37.635 of 636
Route object: RIR2602:fffd::/37Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

198.153.76.0/22ALTDB, RADBNo ROA
2602:fffd::/36RADBNo 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.