bgpreport

Network · data from 2026-11-12

AS154927 HONEST-AS-AP - Honest Telecom Pty Ltd

Registry name: HONEST-AS-AP - Honest Telecom Pty Ltd, AU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS154927, 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.
2402:76e0:8100::/40 Invalid: maxLength Nonecovered by 2402:76e0::/32 2 0%low visibility 2
163.52.204.0/23 Valid RIR databaseAPNIC 672 100% 67
2402:76e0::/32 Valid RIR databaseAPNIC 635 100% 69

AS-SET

AS154927 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 4 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength2402:76e0:8100::/40ROA 2402:76e0::/32 AS154927 has maxLength 32; the route is a /40. Raise the maxLength, or add a ROA for 2402:76e0:8100::/40.2 of 636
Route object: none2402:76e0:8100::/40No route object for it. A route object for 2402:76e0::/32 with origin AS154927 covers it (filters allowing more-specifics accept it). Add a route object with origin AS154927 in the RIR database for the space.2 of 636

Route objects not announced

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

163.52.204.0/24APNICValid
163.52.205.0/24APNICValid

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.