bgpreport

Network · data from 2026-11-12

AS45924 GLOBAL-AS-AP - Global Technologies Limited

Registry name: GLOBAL-AS-AP - Global Technologies Limited, PG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45924, 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.
202.1.52.0/24 No ROA Other origin only 671 100% 67
202.171.240.0/21 No ROA Other origin only 671 100% 68
202.171.242.0/24 No ROA Other origin only 671 100% 67

AS-SET

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

  • ROA: none3
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: none202.1.52.0/24No ROA covers it. Add a ROA for AS45924, maxLength 24.671 of 673
Route object: none202.1.52.0/24Route objects for it name AS24516. Add a route object with origin AS45924 in the RIR database for the space.671 of 673
ROA: none202.171.240.0/21No ROA covers it. Add a ROA for AS45924, maxLength 21.671 of 673
Route object: none202.171.240.0/21Route objects for it name AS7545, AS9398, AS17828, AS24516. Add a route object with origin AS45924 in the RIR database for the space.671 of 673
ROA: none202.171.242.0/24No ROA covers it. Add a ROA for AS45924, maxLength 24.671 of 673
Route object: none202.171.242.0/24Route objects for it name AS24516. Add a route object with origin AS45924 in the RIR database for the space.671 of 673

Route objects not announced

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