bgpreport

Network · data from 2026-11-12

AS9519 Vertical Telecoms Pty Ltd

Registry name: VERTELNET - Vertical Telecoms Pty Ltd, AU · PeeringDB

12IPv4 routes 0.0% RPKI valid · 83.3% with a route object
1IPv6 routes 0.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
13No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
47Route objects not announced registered with origin AS9519, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS9519, 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.82.104.0/23 No ROA Nonecovered by 203.82.104.0/22 672 100% 67
203.82.110.0/23 No ROA Nonecovered by 203.82.108.0/22 671 100% 67
2400:1900:2000::/36 No ROA Nonecovered by 2400:1900::/32 635 100% 67
203.82.96.0/23 No ROA Other IRR onlyRADB 672 100% 67
203.82.98.0/23 No ROA Other IRR onlyRADB 672 100% 67
203.82.100.0/23 No ROA Other IRR onlyRADB 672 100% 67
203.82.102.0/23 No ROA Other IRR onlyRADB 672 100% 67
203.82.106.0/23 No ROA Other IRR onlyRADB 672 100% 67
203.82.108.0/23 No ROA Other IRR onlyRADB 672 100% 67
203.188.218.0/23 No ROA Other IRR onlyRADB 672 100% 67
203.188.220.0/23 No ROA Other IRR onlyRADB 672 100% 67
203.188.222.0/23 No ROA Other IRR onlyRADB 672 100% 67
203.188.216.0/23 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

AS9519'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 73 are in fix.csv.

  • ROA: none13
  • Route object: none3
  • Route object: RIR10
  • Route object: not announced47
ChangePrefix or setDetailFull-table peers
ROA: none203.82.104.0/23No ROA covers it. Add a ROA for AS9519, maxLength 23.672 of 673
Route object: none203.82.104.0/23No route object for it. A route object for 203.82.104.0/22 with origin AS9519 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9519 in the RIR database for the space.672 of 673
ROA: none203.82.110.0/23No ROA covers it. Add a ROA for AS9519, maxLength 23.671 of 673
Route object: none203.82.110.0/23No route object for it. A route object for 203.82.108.0/22 with origin AS9519 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9519 in the RIR database for the space.671 of 673
ROA: none2400:1900:2000::/36No ROA covers it. Add a ROA for AS9519, maxLength 36.635 of 636
Route object: none2400:1900:2000::/36No route object for it. A route object for 2400:1900::/32 with origin AS9519 covers it (filters allowing more-specifics accept it). Add a route object with origin AS9519 in the RIR database for the space.635 of 636
ROA: none203.82.96.0/23No ROA covers it. Add a ROA for AS9519, maxLength 23.672 of 673
Route object: RIR203.82.96.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.82.98.0/23No ROA covers it. Add a ROA for AS9519, maxLength 23.672 of 673
Route object: RIR203.82.98.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.82.100.0/23No ROA covers it. Add a ROA for AS9519, maxLength 23.672 of 673
Route object: RIR203.82.100.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.82.102.0/23No ROA covers it. Add a ROA for AS9519, maxLength 23.672 of 673
Route object: RIR203.82.102.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.82.106.0/23No ROA covers it. Add a ROA for AS9519, maxLength 23.672 of 673
Route object: RIR203.82.106.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.82.108.0/23No ROA covers it. Add a ROA for AS9519, maxLength 23.672 of 673
Route object: RIR203.82.108.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.188.218.0/23No ROA covers it. Add a ROA for AS9519, maxLength 23.672 of 673
Route object: RIR203.188.218.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.188.220.0/23No ROA covers it. Add a ROA for AS9519, maxLength 23.672 of 673
Route object: RIR203.188.220.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.188.222.0/23No ROA covers it. Add a ROA for AS9519, maxLength 23.672 of 673
Route object: RIR203.188.222.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none203.188.216.0/23No ROA covers it. Add a ROA for AS9519, maxLength 23.671 of 673
Route object: RIR203.188.216.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

45.124.200.0/22RADBNo ROA
103.5.106.0/24RADBNo ROA
103.27.188.0/22RADBNo ROA
103.28.216.0/23RADBNo ROA
103.28.216.0/24RADBNo ROA
103.28.217.0/24RADBNo ROA
103.39.136.0/23RADBNo ROA
103.39.136.0/24RADBNo ROA
103.39.137.0/24RADBNo ROA
103.75.204.0/22RADBNo ROA
103.79.180.0/24RADBNo ROA
103.198.55.0/24RADBNo ROA
103.198.112.0/23RADBNo ROA
103.198.112.0/24RADBNo ROA
103.198.113.0/24RADBNo ROA
103.227.63.0/24RADBNo ROA
103.232.208.0/22RADBNo ROA
202.0.64.0/24RADBNo ROA
202.86.48.0/22RADBNo ROA
202.86.48.0/23RADBNo ROA
202.86.48.0/24RADBNo ROA
202.86.49.0/24RADBNo ROA
202.86.50.0/23RADBNo ROA
202.86.50.0/24RADBNo ROA
202.86.51.0/24RADBNo ROA
202.86.52.0/23RADBNo ROA
202.86.54.0/23RADBNo ROA
202.182.131.0/24RADBNo ROA
202.182.158.0/23RADBNo ROA
202.182.159.0/24RADBNo ROA
203.22.251.0/24RADBNo ROA
203.82.96.0/21RADBNo ROA
203.82.96.0/22RADBNo ROA
203.82.100.0/22RADBNo ROA
203.82.104.0/21RADBNo ROA
203.82.104.0/22RADBNo ROA
203.82.104.0/24RADBNo ROA
203.82.105.0/24RADBNo ROA
203.82.106.0/24RADBNo ROA
203.82.107.0/24RADBNo ROA
203.82.108.0/22RADBNo ROA
203.82.108.0/24RADBNo ROA
203.82.109.0/24RADBNo ROA
203.82.110.0/24RADBNo ROA
203.175.178.0/23RADBNo ROA
203.185.250.0/23RADBNo ROA
2400:1900::/32RADBNo 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.