bgpreport

Network · data from 2026-11-12

AS7492 NEXON GLOBAL

Registry name: NEXON-GLOBAL-BACKBONE-ASN - Nexon Global Backbone, AU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS7492, 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.
192.68.110.0/23 No ROA Other IRR onlyRADB 671 100% 67
2400:3400::/32 No ROA Other IRR onlyRADB 636 100% 69
103.157.244.0/23 Valid RIR databaseAPNIC 672 100% 67
2001:df2:3340::/48 Valid RIR databaseAPNIC 635 100% 69
2001:df2:33c0::/48 Valid RIR databaseAPNIC 635 100% 69
2001:df5:3680::/48 Valid RIR databaseAPNIC 635 100% 69

AS-SET

AS7492'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 23 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
ROA: none192.68.110.0/23No ROA covers it. Add a ROA for AS7492, maxLength 23.671 of 673
Route object: RIR192.68.110.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2400:3400::/32No ROA covers it. Add a ROA for AS7492, maxLength 32.636 of 636
Route object: RIR2400:3400::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

103.157.244.0/24APNICValid
103.157.245.0/24APNICValid
202.124.32.0/20RADBNo ROA
203.22.247.0/24RADBNo ROA
203.23.194.0/24RADBNo ROA
203.27.50.0/24RADBNo ROA
203.31.226.0/24RADBNo ROA
203.62.138.0/24RADBNo ROA
203.80.168.0/21RADBNo ROA
203.80.168.0/22RADBNo ROA
203.80.168.0/23RADBNo ROA
203.80.169.0/24RADBNo ROA
203.80.172.0/22RADBNo ROA
203.80.172.0/23RADBNo ROA
203.80.172.0/24RADBNo ROA
203.80.173.0/24RADBNo ROA
203.80.174.0/23RADBNo ROA
203.80.174.0/24RADBNo ROA
203.80.175.0/24RADBNo 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.