Network · data from 2026-11-12
AS13804 ARROW-TECHNOLOGY-GROUP - ATG Arrow Technology Group Limited Partnership
Registry name: ARROW-TECHNOLOGY-GROUP - ATG Arrow Technology Group Limited Partnership, CA · not in PeeringDB
14IPv4 routes
92.9% RPKI valid · 100.0% with a route object
18IPv6 routes
72.2% RPKI valid · 72.2% with a route object
0RPKI invalid
0 origin · 0 maxLength
6No ROA
5 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
9Route objects not announced
registered with origin AS13804, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS13804, 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.
| 2600:d801:10::/44 | No ROA | Nonecovered by 2600:d800::/28 | 635 100% |
| 2600:d801:a0::/44 | No ROA | Nonecovered by 2600:d800::/28 | 635 100% |
| 2600:d801:140::/44 | No ROA | Nonecovered by 2600:d800::/28 | 635 100% |
| 2600:d801:190::/44 | No ROA | Nonecovered by 2600:d800::/28 | 635 100% |
| 2600:d801:1b0::/44 | No ROA | Nonecovered by 2600:d800::/28 | 635 100% |
| 69.196.84.0/23 | No ROA | Other IRR onlyRADB | 670 100% |
| 192.199.63.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 192.199.61.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 192.199.50.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 192.199.51.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 192.199.52.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 192.199.53.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 192.199.54.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 192.199.55.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 192.199.56.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 192.199.57.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 192.199.58.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 192.199.59.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 192.199.60.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 2600:d800::/32 | Valid | RIR databaseARIN | 635 100% |
| 2600:d801::/44 | Valid | RIR databaseARIN | 634 100% |
| 2600:d801:30::/44 | Valid | RIR databaseARIN | 634 100% |
| 2600:d801:50::/44 | Valid | RIR databaseARIN | 634 100% |
| 2600:d801:60::/44 | Valid | RIR databaseARIN | 634 100% |
| 2600:d801:70::/44 | Valid | RIR databaseARIN | 634 100% |
| 2600:d801:80::/44 | Valid | RIR databaseARIN | 634 100% |
| 2600:d801:90::/44 | Valid | RIR databaseARIN | 634 100% |
| 2600:d801:b0::/44 | Valid | RIR databaseARIN | 634 100% |
| 2600:d801:c0::/44 | Valid | RIR databaseARIN | 634 100% |
| 2600:d801:e0::/44 | Valid | RIR databaseARIN | 634 100% |
| 2600:d801:100::/44 | Valid | RIR databaseARIN | 634 100% |
| 2600:d801:170::/44 | Valid | RIR databaseARIN | 634 100% |
AS-SET
AS13804 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 34 are in fix.csv.
- ROA: none6
- Route object: none5
- Route object: RIR14
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2600:d801:10::/44 | No ROA covers it. Add a ROA for AS13804, maxLength 44. |
| Route object: none | 2600:d801:10::/44 | No route object for it. A route object for 2600:d800::/28 with origin AS13804 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13804 in the RIR database for the space. |
| ROA: none | 2600:d801:a0::/44 | No ROA covers it. Add a ROA for AS13804, maxLength 44. |
| Route object: none | 2600:d801:a0::/44 | No route object for it. A route object for 2600:d800::/28 with origin AS13804 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13804 in the RIR database for the space. |
| ROA: none | 2600:d801:140::/44 | No ROA covers it. Add a ROA for AS13804, maxLength 44. |
| Route object: none | 2600:d801:140::/44 | No route object for it. A route object for 2600:d800::/28 with origin AS13804 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13804 in the RIR database for the space. |
| ROA: none | 2600:d801:190::/44 | No ROA covers it. Add a ROA for AS13804, maxLength 44. |
| Route object: none | 2600:d801:190::/44 | No route object for it. A route object for 2600:d800::/28 with origin AS13804 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13804 in the RIR database for the space. |
| ROA: none | 2600:d801:1b0::/44 | No ROA covers it. Add a ROA for AS13804, maxLength 44. |
| Route object: none | 2600:d801:1b0::/44 | No route object for it. A route object for 2600:d800::/28 with origin AS13804 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13804 in the RIR database for the space. |
| ROA: none | 69.196.84.0/23 | No ROA covers it. Add a ROA for AS13804, maxLength 23. |
| Route object: RIR | 69.196.84.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.199.63.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.199.61.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.199.50.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.199.51.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.199.52.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.199.53.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.199.54.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.199.55.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.199.56.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.199.57.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.199.58.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.199.59.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 192.199.60.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS13804 whose prefix no peer sees AS13804 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 63.238.64.0/24 | RADB | No ROA |
| 192.199.48.0/20 | ARIN, RADB | Valid |
| 192.199.48.0/24 | RADB | Valid |
| 192.199.49.0/24 | RADB | Valid |
| 192.199.62.0/24 | RADB | Valid |
| 2600:d800::/28 | RADB | No ROA |
| 2600:d801:d0::/44 | ARIN | Valid |
| 2600:d801:f0::/44 | ARIN | Valid |
| 2600:d801:130::/44 | ARIN | Valid |
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.