bgpreport

Network · data from 2026-11-12

AS154562 CYBERJET PTE LTD

Registry name: CYBERJETPTELTD-AS-AP - CYBERJET PTE LTD, SG · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS154562, 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.

2402:5260:a01::/48 Invalid: maxLength Nonecovered by 2402:5260::/32 3 0%low visibility 1
163.128.98.0/23 Valid RIR databaseAPNIC 673 100% 67
2402:5260::/32 Valid RIR databaseAPNIC 634 100% 69

AS-SET

AS154562's PeeringDB record names no 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 2 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2402:5260:a01::/48ROA 2402:5260::/32 AS154562 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2402:5260:a01::/48.3 of 636
Route object: none2402:5260:a01::/48No route object for it. A route object for 2402:5260::/32 with origin AS154562 covers it (filters allowing more-specifics accept it). Add a route object with origin AS154562 in the RIR database for the space.3 of 636

Route objects not announced

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