bgpreport

Network · data from 2026-11-12

AS18055 CENTRELINK - Department of Human Services

Registry name: CENTRELINK - Department of Human Services, AU · not in PeeringDB

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

Announced routes

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

192.195.44.0/22 No ROA Other origin only 672 100% 67
192.195.48.0/22 No ROA Other origin only 672 100% 67
203.13.43.0/24 No ROA Other origin only 672 100% 67
192.195.49.0/24 No ROA RIR databaseAPNIC 672 100% 67
192.195.55.0/24 No ROA RIR databaseAPNIC 672 100% 67
161.146.160.0/24 Valid RIR databaseAPNIC 673 100% 67
103.45.254.0/23 Valid RIR databaseAPNIC 672 100% 67
161.146.161.0/24 Valid RIR databaseAPNIC 672 100% 67
161.146.192.0/19 Valid RIR databaseAPNIC 672 100% 67
161.146.195.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
161.146.201.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
161.146.224.0/20 Valid RIR databaseAPNIC 672 100% 67
161.146.235.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
161.146.236.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
192.108.99.0/24 Valid RIR databaseAPNIC 672 100% 67
202.59.247.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
203.13.0.0/20 Valid RIR databaseAPNIC 672 100% 67
203.13.0.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
203.13.10.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
203.80.58.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
203.80.59.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
203.217.150.0/23 Valid RIR databaseAPNIC 672 100% 67
2001:df0:86::/48 Valid RIR databaseAPNIC 635 100% 69
2407:6a00::/32 Valid RIR databaseAPNIC 635 100% 69

AS-SET

AS18055 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 98 are in fix.csv.

  • ROA: none5
  • Route object: none3
  • Route object: not announced90
ChangePrefix or setDetailFull-table peers
ROA: none192.195.44.0/22No ROA covers it. Add a ROA for AS18055, maxLength 22.672 of 673
Route object: none192.195.44.0/22Route objects for it name AS17477. Add a route object with origin AS18055 in the RIR database for the space.672 of 673
ROA: none192.195.48.0/22No ROA covers it. Add a ROA for AS18055, maxLength 22.672 of 673
Route object: none192.195.48.0/22Route objects for it name AS17477. Add a route object with origin AS18055 in the RIR database for the space.672 of 673
ROA: none203.13.43.0/24No ROA covers it. Add a ROA for AS18055, maxLength 24.672 of 673
Route object: none203.13.43.0/24Route objects for it name AS7545. Add a route object with origin AS18055 in the RIR database for the space.672 of 673
ROA: none192.195.49.0/24No ROA covers it. Add a ROA for AS18055, maxLength 24.672 of 673
ROA: none192.195.55.0/24No ROA covers it. Add a ROA for AS18055, maxLength 24.672 of 673

Route objects not announced

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

161.146.192.0/20APNICValid
161.146.192.0/21APNICValid
161.146.192.0/22APNICValid
161.146.192.0/23APNICValid
161.146.192.0/24APNICValid
161.146.193.0/24APNICValid
161.146.194.0/23APNICValid
161.146.194.0/24APNICValid
161.146.196.0/22APNICValid
161.146.196.0/23APNICValid
161.146.196.0/24APNICValid
161.146.197.0/24APNICValid
161.146.198.0/23APNICValid
161.146.198.0/24APNICValid
161.146.199.0/24APNICValid
161.146.200.0/21APNICValid
161.146.200.0/22APNICValid
161.146.200.0/23APNICValid
161.146.200.0/24APNICValid
161.146.202.0/23APNICValid
161.146.202.0/24APNICValid
161.146.203.0/24APNICValid
161.146.204.0/22APNICValid
161.146.204.0/23APNICValid
161.146.204.0/24APNICValid
161.146.205.0/24APNICValid
161.146.206.0/23APNICValid
161.146.206.0/24APNICValid
161.146.207.0/24APNICValid
161.146.208.0/20APNICValid
161.146.208.0/21APNICValid
161.146.208.0/22APNICValid
161.146.208.0/23APNICValid
161.146.208.0/24APNICValid
161.146.209.0/24APNICValid
161.146.210.0/23APNICValid
161.146.210.0/24APNICValid
161.146.211.0/24APNICValid
161.146.212.0/22APNICValid
161.146.212.0/23APNICValid
161.146.212.0/24APNICValid
161.146.213.0/24APNICValid
161.146.214.0/23APNICValid
161.146.214.0/24APNICValid
161.146.215.0/24APNICValid
161.146.216.0/21APNICValid
161.146.216.0/22APNICValid
161.146.216.0/23APNICValid
161.146.216.0/24APNICValid
161.146.217.0/24APNICValid
161.146.218.0/23APNICValid
161.146.218.0/24APNICValid
161.146.219.0/24APNICValid
161.146.220.0/22APNICValid
161.146.220.0/23APNICValid
161.146.220.0/24APNICValid
161.146.221.0/24APNICValid
161.146.222.0/23APNICValid
161.146.222.0/24APNICValid
161.146.223.0/24APNICValid
202.129.237.0/24APNICValid
203.13.0.0/21APNICValid
203.13.0.0/22APNICValid
203.13.0.0/23APNICValid
203.13.1.0/24APNICValid
203.13.2.0/23APNICValid
203.13.2.0/24APNICValid
203.13.3.0/24APNICValid
203.13.4.0/22APNICValid
203.13.4.0/23APNICValid
203.13.4.0/24APNICValid
203.13.5.0/24APNICValid
203.13.6.0/23APNICValid
203.13.6.0/24APNICValid
203.13.7.0/24APNICValid
203.13.8.0/21APNICValid
203.13.8.0/22APNICValid
203.13.8.0/23APNICValid
203.13.8.0/24APNICValid
203.13.9.0/24APNICValid
203.13.10.0/23APNICValid
203.13.11.0/24APNICValid
203.13.12.0/22APNICValid
203.13.12.0/23APNICValid
203.13.12.0/24APNICValid
203.13.13.0/24APNICValid
203.13.14.0/23APNICValid
203.13.14.0/24APNICValid
203.13.15.0/24APNICValid
203.80.58.0/23APNIC, RADBValid

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.