bgpreport

Network · data from 2026-11-12

AS141682 ARENA-PAC

Registry name: AIPL-AS-AP - APIDT Infrastructure Pty Ltd, AU · PeeringDB

1IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 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
2Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS141682, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS141682, 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.
103.161.244.0/23 Valid RIR databaseAPNIC, RADB 668 99% 69
2407:940::/32 Valid RIR databaseAPNIC, RADB 633 100% 69
2407:940:ff05::/48 Valid RIR databaseAPNIC 14 2%low visibility 17
2407:940:ff02::/48 Valid RIR databaseAPNIC 5 1%low visibility 7

AS-SET

AS141682'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 6 are in fix.csv.

  • Route object: not announced6

Route objects not announced

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

2407:940:ff00::/48APNICValid
2407:940:ff01::/48APNICValid
2407:940:ff03::/48APNICValid
2407:940:ff04::/48APNICValid
2407:940:ff06::/48APNICValid
2407:940:ff07::/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.