bgpreport

Network · data from 2026-11-12

AS58869 RAY-AS-AP - Ray White (Real Estate) Pty Ltd

Registry name: RAY-AS-AP - Ray White (Real Estate) Pty Ltd, AU · not in PeeringDB

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

Announced routes

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

2403:5f40::/36 No ROA None 632 99% 69
103.248.128.0/22 Valid RIR databaseAPNIC 673 100% 67
2001:df5::/48 Valid RIR databaseAPNIC 635 100% 69
2403:5f40:1::/48 Valid RIR databaseAPNIC 635 100% 69

AS-SET

AS58869 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 5 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2403:5f40::/36No ROA covers it. Add a ROA for AS58869, maxLength 36.632 of 636
Route object: none2403:5f40::/36No route object for it. Add a route object with origin AS58869 in the RIR database for the space.632 of 636

Route objects not announced

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

103.248.128.0/24APNICValid
2403:5f40:4::/48APNICValid
2403:5f40:a::/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.