bgpreport

Network · data from 2026-11-12

AS9449 QLD VoIP Services Australia

Registry name: QLDVOIP-AU - QLD VoIP Services Australia, AU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9449, 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.
203.0.80.0/24 Valid RIR databaseAPNIC 672 100% 66
203.4.168.0/24 Valid RIR databaseAPNIC 672 100% 67
203.7.197.0/24 Valid RIR databaseAPNIC 672 100% 66
203.4.170.0/23 Valid RIR databaseAPNIC 671 100% 67
203.4.171.0/24 Valid RIR databaseAPNIC 671 100% 67
103.160.116.0/24 Valid RIR databaseAPNIC 670 100% 67
103.160.117.0/24 Valid RIR databaseAPNIC 670 100% 67
203.4.170.0/24 Valid RIR databaseAPNIC 670 100% 67
203.28.181.0/24 Valid RIR databaseALTDB, APNIC 670 100% 67
2406:e940::/32 Valid RIR databaseAPNIC 635 100% 69
2406:e940::/48 Valid RIR databaseAPNIC 635 100% 69
2406:e940:4006::/48 Valid RIR databaseAPNIC 635 100% 69
2406:e940:4680::/48 Valid RIR databaseAPNIC 635 100% 69

AS-SET

AS9449'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 23 are in fix.csv.

  • Route object: not announced23

Route objects not announced

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

203.3.78.0/24ALTDBNo ROA
203.3.160.0/22ALTDBNo ROA
203.4.206.0/24ALTDBNo ROA
203.4.240.0/21ALTDBNo ROA
203.5.193.0/24ALTDBNo ROA
203.7.202.0/23ALTDBNo ROA
203.7.204.0/24ALTDBNo ROA
203.8.92.0/23ALTDBNo ROA
203.9.224.0/20ALTDBNo ROA
203.14.128.0/20ALTDBNo ROA
203.17.11.0/24ALTDBNo ROA
203.19.67.0/24ALTDBNo ROA
203.25.118.0/24ALTDBNo ROA
203.27.74.0/23ALTDBNo ROA
203.28.213.0/24ALTDBNo ROA
203.30.132.0/23ALTDBNo ROA
203.30.202.0/23ALTDBNo ROA
203.31.71.0/24ALTDBNo ROA
203.31.242.0/23ALTDBNo ROA
203.32.208.0/22ALTDBNo ROA
203.55.164.0/23ALTDBNo ROA
203.56.88.0/23ALTDBNo ROA
2406:e940:f055::/48APNICValid

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.