bgpreport

Network · data from 2026-11-12

AS199959 GWY IT PTY LTD

Registry name: CrownCloud GWY IT PTY LTD, AU · PeeringDB

69IPv4 routes 73.9% RPKI valid · 85.5% with a route object
13IPv6 routes 76.9% RPKI valid · 92.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
21No ROA 11 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
11Route objects not announced registered with origin AS199959, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS199959, 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.
104.238.34.0/24 No ROA Nonecovered by 104.238.34.0/23 672 100% 66
104.238.61.0/24 No ROA Nonecovered by 104.238.60.0/23 672 100% 66
166.0.178.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
23.152.0.0/24 No ROA RIR databaseARIN 672 100% 66
23.163.0.0/24 No ROA RIR databaseARIN 672 100% 66
66.85.26.0/24 No ROA RIR databaseARIN 672 100% 66
66.85.27.0/24 No ROA RIR databaseARIN 672 100% 66
104.194.214.0/24 No ROA RIR databaseARIN 672 100% 66
104.194.215.0/24 No ROA RIR databaseARIN 672 100% 66
104.200.67.0/24 No ROA RIR databaseARIN 672 100% 66
104.200.73.0/24 No ROA RIR databaseARIN 672 100% 66
104.238.56.0/23 No ROA RIR databaseARIN 672 100% 66
45.56.162.0/24 No ROA RIR databaseARIN 671 100% 66
45.56.163.0/24 No ROA RIR databaseARIN 671 100% 66
45.56.164.0/24 No ROA RIR databaseARIN 671 100% 66
192.169.6.0/24 No ROA RIR databaseARIN 671 100% 66
192.169.7.0/24 No ROA RIR databaseARIN 671 100% 66
104.200.72.0/24 No ROA RIR databaseARIN 667 99% 67
2a07:efc0:2000::/36 No ROA RIR databaseRIPE 636 100% 67
2602:ff75::/36 No ROA RIR databaseARIN 635 100% 67
2602:ff75:2000::/36 No ROA RIR databaseARIN 632 99% 67
31.220.14.0/24 Valid Other origin only 672 100% 66
45.12.52.0/23 Valid Other origin only 672 100% 66
185.238.249.0/24 Valid Other origin only 672 100% 66
185.238.251.0/24 Valid Other origin only 672 100% 66
192.52.166.0/24 Valid Nonecovered by 192.52.166.0/23 672 100% 66
192.52.167.0/24 Valid Nonecovered by 192.52.166.0/23 672 100% 66
193.9.45.0/24 Valid Other origin only 672 100% 66
45.12.91.0/24 Valid Other origin only 671 100% 66
2602:f992:50::/44 Valid None 635 100% 68
102.129.214.0/24 Valid Other IRR onlyRADB 672 100% 66
104.239.102.0/24 Valid RIR databaseRIPE 673 100% 67
155.117.237.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
195.88.191.0/24 Valid RIR databaseRIPE 673 100% 67
2.58.14.0/23 Valid RIR databaseRIPE 672 100% 66
5.183.95.0/24 Valid RIR databaseRIPE 672 100% 67
45.86.163.0/24 Valid RIR databaseRIPE 672 100% 67
45.128.156.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
46.30.189.0/24 Valid RIR databaseRIPE 672 100% 67
46.30.190.0/24 Valid RIR databaseRIPE 672 100% 67
64.204.84.0/22 Valid RIR databaseARIN, RADB 672 100% 66
64.204.108.0/22 Valid RIR databaseARIN, RADB 672 100% 66
64.204.184.0/22 Valid RIR databaseARIN, RADB 672 100% 66
65.75.207.0/24 Valid RIR databaseARIN 672 100% 66
65.86.180.0/22 Valid RIR databaseARIN, RADB 672 100% 66
65.86.188.0/22 Valid RIR databaseARIN, RADB 672 100% 66
72.244.188.0/22 Valid RIR databaseARIN, RADB 672 100% 66
72.244.200.0/22 Valid RIR databaseARIN, RADB 672 100% 66
103.79.76.0/24 Valid RIR databaseAPNIC 672 100% 66
103.79.77.0/24 Valid RIR databaseAPNIC 672 100% 66
103.79.78.0/24 Valid RIR databaseAPNIC 672 100% 66
103.79.79.0/24 Valid RIR databaseAPNIC 672 100% 66
103.79.118.0/24 Valid RIR databaseAPNIC 672 100% 66
103.91.144.0/24 Valid RIR databaseAPNIC 672 100% 66
103.91.145.0/24 Valid RIR databaseAPNIC 672 100% 66
103.216.162.0/23 Valid RIR databaseAPNIC 672 100% 66
104.249.20.0/24 Valid RIR databaseRIPE 672 100% 66
143.20.208.0/22 Valid RIR databaseRADB, RIPE 672 100% 66
185.121.176.0/24 Valid RIR databaseRIPE 672 100% 66
192.48.192.0/24 Valid RIR databaseARIN, RADB 672 100% 66
192.189.2.0/24 Valid RIR databaseARIN 672 100% 66
194.40.248.0/24 Valid RIR databaseRIPE 672 100% 66
202.91.32.0/24 Valid RIR databaseAPNIC 672 100% 66
212.108.122.0/24 Valid RIR databaseRIPE 672 100% 66
45.86.162.0/24 Valid RIR databaseRIPE 671 100% 66
46.30.188.0/24 Valid RIR databaseRIPE 671 100% 66
46.30.191.0/24 Valid RIR databaseRIPE 671 100% 66
84.75.232.0/22 Valid RIR databaseRADB, RIPE 667 99% 67
104.238.60.0/24 Valid RIR databaseARIN 667 99% 67
178.83.248.0/22 Valid RIR databaseRADB, RIPE 667 99% 67
185.227.83.0/24 Valid RIR databaseRIPE 667 99% 67
186.190.220.0/24 Valid RIR databaseARIN 667 99% 67
45.61.114.0/24 Valid RIR databaseARIN 666 99% 67
2a14:640:2::/48 Valid RIR databaseRIPE 635 100% 68
2a14:640:3::/48 Valid RIR databaseRIPE 635 100% 68
2a14:640:4::/48 Valid RIR databaseRIPE 635 100% 68
2a14:640:5::/48 Valid RIR databaseRIPE 635 100% 68
2a14:640:6::/48 Valid RIR databaseRIPE 635 100% 68
2a14:640:7::/48 Valid RIR databaseRIPE 635 100% 68
2a14:640:8::/48 Valid RIR databaseRIPE 635 100% 68
2a07:efc0:1000::/36 Valid RIR databaseRADB, RIPE 634 100% 68
2a0b:3c40:50::/48 Valid RIR databaseRIPE 634 100% 68

AS-SET

AS199959'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 45 are in fix.csv.

  • ROA: none21
  • Route object: none11
  • Route object: RIR2
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none104.238.34.0/24No ROA covers it. Add a ROA for AS199959, maxLength 24.672 of 673
Route object: none104.238.34.0/24No route object for it. A route object for 104.238.34.0/23 with origin AS199959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199959 in the RIR database for the space.672 of 673
ROA: none104.238.61.0/24No ROA covers it. Add a ROA for AS199959, maxLength 24.672 of 673
Route object: none104.238.61.0/24No route object for it. A route object for 104.238.60.0/23 with origin AS199959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199959 in the RIR database for the space.672 of 673
ROA: none166.0.178.0/24No ROA covers it. Add a ROA for AS199959, maxLength 24.2 of 673
Route object: RIR166.0.178.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none23.152.0.0/24No ROA covers it. Add a ROA for AS199959, maxLength 24.672 of 673
ROA: none23.163.0.0/24No ROA covers it. Add a ROA for AS199959, maxLength 24.672 of 673
ROA: none66.85.26.0/24No ROA covers it. Add a ROA for AS199959, maxLength 24.672 of 673
ROA: none66.85.27.0/24No ROA covers it. Add a ROA for AS199959, maxLength 24.672 of 673
ROA: none104.194.214.0/24No ROA covers it. Add a ROA for AS199959, maxLength 24.672 of 673
ROA: none104.194.215.0/24No ROA covers it. Add a ROA for AS199959, maxLength 24.672 of 673
ROA: none104.200.67.0/24No ROA covers it. Add a ROA for AS199959, maxLength 24.672 of 673
ROA: none104.200.73.0/24No ROA covers it. Add a ROA for AS199959, maxLength 24.672 of 673
ROA: none104.238.56.0/23No ROA covers it. Add a ROA for AS199959, maxLength 23.672 of 673
ROA: none45.56.162.0/24No ROA covers it. Add a ROA for AS199959, maxLength 24.671 of 673
ROA: none45.56.163.0/24No ROA covers it. Add a ROA for AS199959, maxLength 24.671 of 673
ROA: none45.56.164.0/24No ROA covers it. Add a ROA for AS199959, maxLength 24.671 of 673
ROA: none192.169.6.0/24No ROA covers it. Add a ROA for AS199959, maxLength 24.671 of 673
ROA: none192.169.7.0/24No ROA covers it. Add a ROA for AS199959, maxLength 24.671 of 673
ROA: none104.200.72.0/24No ROA covers it. Add a ROA for AS199959, maxLength 24.667 of 673
ROA: none2a07:efc0:2000::/36No ROA covers it. Add a ROA for AS199959, maxLength 36.636 of 636
ROA: none2602:ff75::/36No ROA covers it. Add a ROA for AS199959, maxLength 36.635 of 636
ROA: none2602:ff75:2000::/36No ROA covers it. Add a ROA for AS199959, maxLength 36.632 of 636
Route object: none31.220.14.0/24Route objects for it name AS40676. Add a route object with origin AS199959 in the RIR database for the space.672 of 673
Route object: none45.12.52.0/23Route objects for it name AS40676. Add a route object with origin AS199959 in the RIR database for the space.672 of 673
Route object: none185.238.249.0/24Route objects for it name AS40676. Add a route object with origin AS199959 in the RIR database for the space.672 of 673
Route object: none185.238.251.0/24Route objects for it name AS40676. Add a route object with origin AS199959 in the RIR database for the space.672 of 673
Route object: none192.52.166.0/24No route object for it. A route object for 192.52.166.0/23 with origin AS199959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199959 in the RIR database for the space.672 of 673
Route object: none192.52.167.0/24No route object for it. A route object for 192.52.166.0/23 with origin AS199959 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199959 in the RIR database for the space.672 of 673
Route object: none193.9.45.0/24Route objects for it name AS40676. Add a route object with origin AS199959 in the RIR database for the space.672 of 673
Route object: none45.12.91.0/24Route objects for it name AS40676. Add a route object with origin AS199959 in the RIR database for the space.671 of 673
Route object: none2602:f992:50::/44No route object for it. Add a route object with origin AS199959 in the RIR database for the space.635 of 636
Route object: RIR102.129.214.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 AS199959 whose prefix no peer sees AS199959 announce. Many are kept on purpose (backup routes, space announced only in some places).

45.56.138.0/23ARINNo ROA
45.56.166.0/23ARINNo ROA
45.56.166.0/24ARINNo ROA
45.141.60.0/24RIPEValid
93.123.76.0/22RIPEValid
103.79.76.0/22APNICValid
104.194.214.0/23ARINNo ROA
104.238.34.0/23ARINNo ROA
104.238.60.0/23ARINNo ROA
192.52.166.0/23ARINValid
192.169.6.0/23ARINNo 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.