bgpreport

Network · data from 2026-11-12

AS58683 Rackspace Sydney

Registry name: RACKSPACE-AS - Rackspace.com Sydney, HK · PeeringDB

3IPv4 routes 0.0% RPKI valid · 66.7% with a route object
2IPv6 routes 0.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS58683, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS58683, 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.
119.9.160.0/21 No ROA Nonecovered by 119.9.128.0/18 671 100% 67
2401:1801:f000::/36 No ROA Nonecovered by 2401:1801::/32 636 100% 67
119.9.0.0/18 No ROA Other IRR onlyRADB 671 100% 67
119.9.128.0/18 No ROA Other IRR onlyRADB 671 100% 67
2401:1801::/32 No ROA Other IRR onlyRADB 636 100% 69

AS-SET

AS58683'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 14 are in fix.csv.

  • ROA: none5
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none119.9.160.0/21No ROA covers it. Add a ROA for AS58683, maxLength 21.671 of 673
Route object: none119.9.160.0/21No route object for it. A route object for 119.9.128.0/18 with origin AS58683 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58683 in the RIR database for the space.671 of 673
ROA: none2401:1801:f000::/36No ROA covers it. Add a ROA for AS58683, maxLength 36.636 of 636
Route object: none2401:1801:f000::/36No route object for it. A route object for 2401:1801::/32 with origin AS58683 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58683 in the RIR database for the space.636 of 636
ROA: none119.9.0.0/18No ROA covers it. Add a ROA for AS58683, maxLength 18.671 of 673
Route object: RIR119.9.0.0/18Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none119.9.128.0/18No ROA covers it. Add a ROA for AS58683, maxLength 18.671 of 673
Route object: RIR119.9.128.0/18Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2401:1801::/32No ROA covers it. Add a ROA for AS58683, maxLength 32.636 of 636
Route object: RIR2401:1801::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

119.9.0.0/16RADBNo ROA
119.9.19.192/27APNICValid
202.1.234.0/24RADBNo ROA
202.1.235.0/24RADBNo 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.