bgpreport

Network · data from 2026-11-12

AS24126 UNISYS-AP-UI-AS-AP - Unisys AsiaPac Intranet Access to Internet

Registry name: UNISYS-AP-UI-AS-AP - Unisys AsiaPac Intranet Access to Internet, AU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS24126, 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.
129.220.60.0/24 No ROA Other IRR onlyRADB 671 100% 67
103.192.33.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.192.34.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.192.35.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
202.9.55.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66

AS-SET

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

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none129.220.60.0/24No ROA covers it. Add a ROA for AS24126, maxLength 24.671 of 673
Route object: RIR129.220.60.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

103.192.32.0/22APNICValid
103.192.32.0/23APNICValid
103.192.32.0/24APNIC, RADBValid
103.192.34.0/23APNICValid
129.226.0.0/17RADBNo ROA
192.59.175.0/24NTTCOMNo ROA
192.146.251.0/24RADBNo ROA
192.146.252.0/24RADBNo ROA
192.146.253.0/24RADBNo ROA
192.207.98.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.