bgpreport

Network · data from 2026-11-12

AS133878 UNICOM1-AS-AP - UNICOM NEW ZEALAND LIMITED

Registry name: UNICOM1-AS-AP - UNICOM NEW ZEALAND LIMITED, NZ · not in PeeringDB

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

Announced routes

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

43.225.200.0/22 No ROA Other IRR onlyRADB 672 100% 68
43.225.201.0/24 No ROA Other IRR onlyRADB 672 100% 68
43.225.202.0/24 No ROA Other IRR onlyRADB 672 100% 68
43.225.203.0/24 No ROA Other IRR onlyRADB 672 100% 68
103.44.164.0/22 No ROA Other IRR onlyRADB 672 100% 68
103.113.204.0/22 No ROA Other IRR onlyRADB 672 100% 68
103.113.204.0/24 No ROA Other IRR onlyRADB 672 100% 68
103.113.205.0/24 No ROA Other IRR onlyRADB 672 100% 68
103.113.206.0/24 No ROA Other IRR onlyRADB 672 100% 68
103.113.207.0/24 No ROA Other IRR onlyRADB 672 100% 68
202.180.79.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
120.136.6.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

AS133878 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 21 are in fix.csv.

  • ROA: none10
  • Route object: RIR10
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none43.225.200.0/22No ROA covers it. Add a ROA for AS133878, maxLength 22.672 of 673
Route object: RIR43.225.200.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none43.225.201.0/24No ROA covers it. Add a ROA for AS133878, maxLength 24.672 of 673
Route object: RIR43.225.201.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none43.225.202.0/24No ROA covers it. Add a ROA for AS133878, maxLength 24.672 of 673
Route object: RIR43.225.202.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none43.225.203.0/24No ROA covers it. Add a ROA for AS133878, maxLength 24.672 of 673
Route object: RIR43.225.203.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.44.164.0/22No ROA covers it. Add a ROA for AS133878, maxLength 22.672 of 673
Route object: RIR103.44.164.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.113.204.0/22No ROA covers it. Add a ROA for AS133878, maxLength 22.672 of 673
Route object: RIR103.113.204.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.113.204.0/24No ROA covers it. Add a ROA for AS133878, maxLength 24.672 of 673
Route object: RIR103.113.204.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.113.205.0/24No ROA covers it. Add a ROA for AS133878, maxLength 24.672 of 673
Route object: RIR103.113.205.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.113.206.0/24No ROA covers it. Add a ROA for AS133878, maxLength 24.672 of 673
Route object: RIR103.113.206.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.113.207.0/24No ROA covers it. Add a ROA for AS133878, maxLength 24.672 of 673
Route object: RIR103.113.207.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

103.44.164.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.