bgpreport

Network · data from 2026-11-12

AS40864 Targo Communications

Registry name: TARGO - Targo Communications Inc., CA · PeeringDB

9IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 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
0Route objects not announced registered with origin AS40864, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS40864, 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.
23.159.240.0/24 Valid RIR databaseARIN 673 100% 67
74.116.156.0/22 Valid RIR databaseARIN 673 100% 67
96.125.192.0/20 Valid RIR databaseALTDB, ARIN, RADB 673 100% 67
104.245.64.0/23 Valid RIR databaseARIN, RADB 673 100% 67
104.245.66.0/24 Valid RIR databaseARIN, RADB 673 100% 67
209.209.116.0/22 Valid RIR databaseARIN, RADB 673 100% 67
209.142.84.0/22 Valid RIR databaseARIN, RADB 670 100% 67
2604:840::/32 Valid RIR databaseARIN 635 100% 67
2606:1b80::/32 Valid RIR databaseARIN 634 100% 68
23.144.128.0/24 Valid RIR databaseARIN 274 41% 59
69.171.160.0/19 Valid RIR databaseARIN 274 41% 59

AS-SET

PeeringDB's irr_as_set for AS40864: AS40864. 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 (AS40864 isn't in the set, or no route object for AS40864 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 objectsAS40864 in itNot covered
AS40864 A single AS number, not a set: AS40864 (this network), 11 route objects.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS40864 is announced.

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.