bgpreport

Network · data from 2026-11-12

AS142125 Capti Networks Pty Ltd

Registry name: CAPTI-AS-AP - Capti Networks Pty Ltd, AU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS142125, 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.166.148.0/24 Valid RIR databaseAPNIC, RADB 667 99% 67
103.166.149.0/24 Valid RIR databaseAPNIC, RADB 667 99% 67
2001:df6:9380::/48 Valid RIR databaseAPNIC, RADB 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS142125: AS142125:AS-CAPTINETWORKS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS142125 isn't in the set, or no route object for AS142125 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS142125 in itNot covered
AS142125:AS-CAPTINETWORKS APNIC 237 Yes 0

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

  • Route object: not announced2

Route objects not announced

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

103.166.148.0/23APNIC, RADBValid
160.22.42.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.