bgpreport

Network · data from 2026-11-12

AS45459 Umbrellar Auckland DC

Registry name: SOLARIX-INTERNET-AS-AP - Solarix Networks Limited, NZ · PeeringDB

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

Announced routes

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

2404:3800:a::/48 Invalid: maxLength Nonecovered by 2404:3800:8::/46 36 6%low visibility 27
2404:3800:b::/48 Invalid: maxLength Nonecovered by 2404:3800:8::/46 36 6%low visibility 27
67.215.112.0/21 Valid RIR databaseAPNIC 671 100% 68
103.14.40.0/24 Valid RIR databaseAPNIC 671 100% 68
103.14.41.0/24 Valid RIR databaseAPNIC 671 100% 68
103.14.42.0/24 Valid RIR databaseAPNIC 671 100% 68
103.14.43.0/24 Valid RIR databaseAPNIC 671 100% 68
112.109.64.0/21 Valid RIR databaseAPNIC 671 100% 68
112.109.72.0/23 Valid RIR databaseAPNIC 671 100% 68
112.109.75.0/24 Valid RIR databaseAPNIC 671 100% 68
112.109.76.0/22 Valid RIR databaseAPNIC 671 100% 68
112.109.80.0/24 Valid RIR databaseAPNIC 671 100% 68
112.109.85.0/24 Valid RIR databaseAPNIC 671 100% 68
112.109.86.0/23 Valid RIR databaseAPNIC 671 100% 68
119.47.116.0/24 Valid RIR databaseAPNIC 671 100% 68
119.47.120.0/23 Valid RIR databaseAPNIC 671 100% 68
119.47.125.0/24 Valid RIR databaseAPNIC 671 100% 68
119.47.126.0/23 Valid RIR databaseAPNIC 671 100% 68
202.174.116.0/24 Valid RIR databaseAPNIC 671 100% 68
210.79.50.0/24 Valid RIR databaseAPNIC 671 100% 68
210.79.52.0/24 Valid RIR databaseAPNIC 671 100% 68
210.79.53.0/24 Valid RIR databaseAPNIC 671 100% 68
210.79.54.0/24 Valid RIR databaseAPNIC 671 100% 68
210.79.55.0/24 Valid RIR databaseAPNIC 671 100% 68
2404:3800::/48 Valid RIR databaseAPNIC 635 100% 69
2404:3800:1::/48 Valid RIR databaseAPNIC 635 100% 69
2404:3800:8::/46 Valid RIR databaseAPNIC 635 100% 69

AS-SET

AS45459'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 60 are in fix.csv.

  • ROA: maxLength2
  • Route object: none2
  • Route object: not announced56
ChangePrefix or setDetailFull-table peers
ROA: maxLength2404:3800:a::/48ROA 2404:3800:8::/46 AS45459 has maxLength 46; the route is a /48. Raise the maxLength, or add a ROA for 2404:3800:a::/48.36 of 636
Route object: none2404:3800:a::/48No route object for it. A route object for 2404:3800:8::/46 with origin AS45459 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45459 in the RIR database for the space.36 of 636
ROA: maxLength2404:3800:b::/48ROA 2404:3800:8::/46 AS45459 has maxLength 46; the route is a /48. Raise the maxLength, or add a ROA for 2404:3800:b::/48.36 of 636
Route object: none2404:3800:b::/48No route object for it. A route object for 2404:3800:8::/46 with origin AS45459 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45459 in the RIR database for the space.36 of 636

Route objects not announced

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

67.215.112.0/22APNICValid
67.215.112.0/23APNICValid
67.215.112.0/24APNICValid
67.215.113.0/24APNICValid
67.215.114.0/23APNICValid
67.215.114.0/24APNICValid
67.215.115.0/24APNICValid
67.215.116.0/22APNICValid
67.215.116.0/23APNICValid
67.215.116.0/24APNICValid
67.215.117.0/24APNICValid
67.215.118.0/23APNICValid
67.215.118.0/24APNICValid
67.215.119.0/24APNICValid
103.14.40.0/22APNICValid
103.14.40.0/23APNICValid
103.14.42.0/23APNICValid
112.109.64.0/20RADBNo ROA
112.109.64.0/22APNICValid
112.109.64.0/23APNICValid
112.109.64.0/24APNICValid
112.109.65.0/24APNICValid
112.109.66.0/23APNICValid
112.109.66.0/24APNICValid
112.109.67.0/24APNICValid
112.109.68.0/22APNICValid
112.109.68.0/23APNICValid
112.109.68.0/24APNICValid
112.109.69.0/24APNICValid
112.109.70.0/23APNICValid
112.109.70.0/24APNICValid
112.109.71.0/24APNICValid
112.109.72.0/24APNICValid
112.109.73.0/24APNICValid
112.109.76.0/23APNICValid
112.109.76.0/24APNICValid
112.109.77.0/24APNICValid
112.109.78.0/23APNICValid
112.109.78.0/24APNICValid
112.109.79.0/24APNICValid
112.109.80.0/21RADBNo ROA
112.109.86.0/24APNICValid
112.109.87.0/24APNICValid
119.47.112.0/20RADBNo ROA
119.47.120.0/24APNICValid
119.47.121.0/24APNICValid
119.47.126.0/24APNICValid
119.47.127.0/24APNICValid
202.89.57.0/24APNICValid
203.89.178.0/24APNICValid
203.89.187.0/24APNICValid
210.79.48.0/22APNICValid
210.79.48.0/23APNICValid
210.79.49.0/24APNICValid
210.79.50.0/23APNICValid
210.79.51.0/24APNICValid

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.