bgpreport

Network · data from 2026-11-12

AS58940 Dedicated Servers Australia

Registry name: DEDAUS-AS-AP - Dedicated Servers Australia, AU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS58940, 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.242.42.0/24 No ROA Other IRR onlyRADB 672 100% 66
43.245.165.0/24 No ROA Other IRR onlyRADB 672 100% 66
43.245.166.0/24 No ROA Other IRR onlyRADB 672 100% 66
103.18.41.0/24 No ROA Other IRR onlyNTTCOM, RADB 672 100% 66
103.18.42.0/24 No ROA Other IRR onlyRADB 672 100% 66
103.18.43.0/24 No ROA Other IRR onlyRADB 672 100% 66
113.52.144.0/22 No ROA Other IRR onlyRADB 672 100% 66
103.4.18.0/24 No ROA RIR databaseAPNIC, RADB 672 100% 66
2407:500:4000::/34 Valid RIR databaseAPNIC, RADB 635 100% 69
2407:500:4101::/48 Valid RIR databaseAPNIC, RADB 635 100% 69
2407:500:4102::/48 Valid RIR databaseAPNIC, RADB 635 100% 69
2407:500:4103::/48 Valid RIR databaseAPNIC, RADB 635 100% 69
2407:500:4104::/48 Valid RIR databaseAPNIC, RADB 635 100% 69
2407:500:4110::/48 Valid RIR databaseAPNIC, RADB 635 100% 69
2407:500:4167::/48 Valid RIR databaseAPNIC 634 100% 69

AS-SET

AS58940'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 57 are in fix.csv.

  • ROA: none8
  • Route object: RIR7
  • Route object: not announced42
ChangePrefix or setDetailFull-table peers
ROA: none43.242.42.0/24No ROA covers it. Add a ROA for AS58940, maxLength 24.672 of 673
Route object: RIR43.242.42.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none43.245.165.0/24No ROA covers it. Add a ROA for AS58940, maxLength 24.672 of 673
Route object: RIR43.245.165.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none43.245.166.0/24No ROA covers it. Add a ROA for AS58940, maxLength 24.672 of 673
Route object: RIR43.245.166.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.18.41.0/24No ROA covers it. Add a ROA for AS58940, maxLength 24.672 of 673
Route object: RIR103.18.41.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.18.42.0/24No ROA covers it. Add a ROA for AS58940, maxLength 24.672 of 673
Route object: RIR103.18.42.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.18.43.0/24No ROA covers it. Add a ROA for AS58940, maxLength 24.672 of 673
Route object: RIR103.18.43.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none113.52.144.0/22No ROA covers it. Add a ROA for AS58940, maxLength 22.672 of 673
Route object: RIR113.52.144.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.4.18.0/24No ROA covers it. Add a ROA for AS58940, maxLength 24.672 of 673

Route objects not announced

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

43.242.40.0/24NTTCOM, RADBNo ROA
43.245.164.0/24NTTCOM, RADBNo ROA
43.245.167.0/24NTTCOM, RADBNo ROA
103.4.16.0/23NTTCOM, RADBNo ROA
103.4.16.0/24APNIC, RADBNo ROA
103.4.17.0/24APNIC, RADBNo ROA
103.4.19.0/24APNIC, NTTCOM, RADBNo ROA
103.18.40.0/23RADBNo ROA
103.18.40.0/24NTTCOM, RADBNo ROA
103.73.86.0/23NTTCOMNo ROA
103.225.164.0/22NTTCOMNo ROA
103.225.164.0/24NTTCOM, RADBNo ROA
103.225.165.0/24NTTCOM, RADBNo ROA
103.225.166.0/24NTTCOM, RADBNo ROA
103.225.167.0/24NTTCOM, RADBNo ROA
113.52.144.0/23RADBNo ROA
113.52.144.0/24RADBNo ROA
113.52.145.0/24RADBNo ROA
113.52.146.0/23RADBNo ROA
113.52.146.0/24RADBNo ROA
113.52.147.0/24RADBNo ROA
163.47.124.0/22RADBNo ROA
163.47.124.0/24APNIC, NTTCOM, RADBNo ROA
163.47.125.0/24APNIC, NTTCOM, RADBNo ROA
163.47.126.0/24APNIC, NTTCOM, RADBNo ROA
163.47.127.0/24APNIC, NTTCOM, RADBNo ROA
185.77.155.0/24RADBNo ROA
203.16.241.0/24NTTCOMNo ROA
2407:500::/32RADBNo ROA
2407:500::/33RADBNo ROA
2407:500::/48NTTCOM, RADBNo ROA
2407:500:1::/48NTTCOM, RADBNo ROA
2407:500:2::/48NTTCOMNo ROA
2407:500:3::/48NTTCOMNo ROA
2407:500:4::/48NTTCOMNo ROA
2407:500:5::/48NTTCOM, RADBNo ROA
2407:500:100::/48RADBNo ROA
2407:500:167::/48RADBNo ROA
2407:500:500::/48RADBNo ROA
2407:500:502::/48RADBNo ROA
2407:500:503::/48RADBNo ROA
2407:500:1000::/48RADBNo 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.