bgpreport

Network · data from 2026-11-12

AS58232 haderan Parsun Network Solutions PTY LTD

Registry name: haderan Parsun Network Solutions PTY LTD, AU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS58232, 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.
217.144.156.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2a05:9080:5::/48 No ROA RIR databaseRIPE 633 100% 67
95.135.125.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
151.245.218.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
176.65.140.0/24 Valid RIR databaseRIPE 673 100% 66
176.65.141.0/24 Valid RIR databaseRIPE 673 100% 66
185.113.10.0/24 Valid RIR databaseRIPE 673 100% 66
45.135.195.0/24 Valid RIR databaseRIPE 672 100% 66
185.83.186.0/24 Valid RIR databaseRIPE 672 100% 66
213.189.26.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
94.183.160.0/24 Valid RIR databaseRIPE 671 100% 66
94.183.192.0/24 Valid RIR databaseRIPE 671 100% 66
94.183.216.0/24 Valid RIR databaseRIPE 671 100% 66
94.183.218.0/24 Valid RIR databaseRIPE 671 100% 66
94.184.37.0/24 Valid RIR databaseRIPE 671 100% 66
176.117.107.0/24 Valid RIR databaseRIPE 670 100% 67
31.56.54.0/24 Valid RIR databaseRIPE 648 96% 67

AS-SET

AS58232 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 5 are in fix.csv.

  • ROA: origin1
  • ROA: none1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin217.144.156.0/24ROAs covering it name AS834, AS8851, AS19905, not AS58232. If AS58232 should announce it, add a ROA for AS58232.2 of 673
Route object: none217.144.156.0/24Route objects for it name AS834. Add a route object with origin AS58232 in the RIR database for the space.2 of 673
ROA: none2a05:9080:5::/48No ROA covers it. Add a ROA for AS58232, maxLength 48.633 of 636

Route objects not announced

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

185.83.185.0/24RIPEValid
185.83.187.0/24RIPEValid

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.