bgpreport

Network · data from 2026-11-12

AS132040 Vital Ltd

Registry name: VITAL-CT-AP - Vital Data Ltd, NZ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS132040, 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.
218.100.24.0/24 No ROA RIR databaseAPNIC, RADB 669 99% 68
2001:4410:1001::/48 Valid Nonecovered by 2001:4410:1000::/40 317 50% 63
2001:4410:1002::/48 Valid Nonecovered by 2001:4410:1000::/40 317 50% 63
2001:4410:1004::/48 Valid Nonecovered by 2001:4410:1000::/40 317 50% 63
2001:4410:2006::/48 Valid Nonecovered by 2001:4410:2000::/40 317 50% 63
2001:4410:2014::/48 Valid Nonecovered by 2001:4410:2000::/40 317 50% 63
202.8.46.0/24 Valid Other IRR onlyRADB 671 100% 68
218.100.26.0/24 Valid Other IRR onlyRADB 671 100% 68
218.100.23.0/24 Valid Other IRR onlyRADB 669 99% 68
2001:4410::/32 Valid Other IRR onlyRADB 636 100% 69
2001:4410::/40 Valid Other IRR onlyRADB 636 100% 69
2001:4410:1000::/40 Valid Other IRR onlyRADB 636 100% 69
2001:4410:2000::/40 Valid Other IRR onlyRADB 636 100% 69
2001:4410:3000::/40 Valid Other IRR onlyRADB 636 100% 69
103.23.16.0/22 Valid RIR databaseAPNIC, RADB 671 100% 68
103.23.17.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
103.23.18.0/23 Valid RIR databaseAPNIC, RADB 671 100% 68
110.173.160.0/21 Valid RIR databaseAPNIC, RADB 671 100% 68
110.173.163.0/24 Valid RIR databaseAPNIC 671 100% 68
202.8.44.0/22 Valid RIR databaseAPNIC 671 100% 68
202.8.44.0/23 Valid RIR databaseAPNIC 671 100% 68
202.8.47.0/24 Valid RIR databaseAPNIC 671 100% 68

AS-SET

AS132040'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 55 are in fix.csv.

  • ROA: none1
  • Route object: none5
  • Route object: RIR8
  • Route object: not announced41
ChangePrefix or setDetailFull-table peers
ROA: none218.100.24.0/24No ROA covers it. Add a ROA for AS132040, maxLength 24.669 of 673
Route object: none2001:4410:1001::/48No route object for it. A route object for 2001:4410:1000::/40 with origin AS132040 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132040 in the RIR database for the space.317 of 636
Route object: none2001:4410:1002::/48No route object for it. A route object for 2001:4410:1000::/40 with origin AS132040 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132040 in the RIR database for the space.317 of 636
Route object: none2001:4410:1004::/48No route object for it. A route object for 2001:4410:1000::/40 with origin AS132040 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132040 in the RIR database for the space.317 of 636
Route object: none2001:4410:2006::/48No route object for it. A route object for 2001:4410:2000::/40 with origin AS132040 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132040 in the RIR database for the space.317 of 636
Route object: none2001:4410:2014::/48No route object for it. A route object for 2001:4410:2000::/40 with origin AS132040 covers it (filters allowing more-specifics accept it). Add a route object with origin AS132040 in the RIR database for the space.317 of 636
Route object: RIR202.8.46.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR218.100.26.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR218.100.23.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2001:4410::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2001:4410::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2001:4410:1000::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2001:4410:2000::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2001:4410:3000::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

103.23.16.0/23RADBValid
103.23.16.0/24RADBValid
103.23.18.0/24RADBValid
103.23.19.0/24RADBValid
110.173.160.0/20APNICValid
110.173.160.0/22APNICValid
110.173.160.0/23APNICValid
110.173.160.0/24APNICValid
110.173.161.0/24APNICValid
110.173.162.0/23APNICValid
110.173.162.0/24APNICValid
110.173.164.0/22APNICValid
110.173.164.0/23APNICValid
110.173.164.0/24APNICValid
110.173.165.0/24APNICValid
110.173.166.0/23APNICValid
110.173.166.0/24APNICValid
110.173.167.0/24APNICValid
110.173.168.0/21APNICValid
110.173.168.0/22APNIC, RADBValid
110.173.168.0/23APNICValid
110.173.168.0/24APNICValid
110.173.169.0/24APNICValid
110.173.170.0/23APNICValid
110.173.170.0/24APNICValid
110.173.171.0/24APNICValid
110.173.172.0/22APNICValid
110.173.172.0/23APNIC, RADBValid
110.173.172.0/24APNICValid
110.173.173.0/24APNICValid
110.173.174.0/23APNICValid
110.173.174.0/24APNICValid
110.173.175.0/24APNICValid
198.48.0.0/22APNICValid
198.48.0.0/23APNICValid
198.48.0.0/24APNICValid
198.48.1.0/24APNICValid
198.48.2.0/23APNICValid
198.48.2.0/24APNICValid
198.48.3.0/24APNICValid
218.100.21.0/24RADBValid

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.