Network · data from 2026-11-12
AS4913 NET-CPRK - Speedcast Communications, Inc
Registry name: NET-CPRK - Speedcast Communications, Inc, US · not in PeeringDB
72IPv4 routes
94.4% RPKI valid · 87.5% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
4No ROA
9 with no route object for this origin
3Low visibility
seen by under 10% of full-table peers
40Route objects not announced
registered with origin AS4913, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS4913, 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.
| 186.208.32.0/23 | No ROA | Other IRR onlyRADB | 669 99% |
| 186.208.36.0/22 | No ROA | Other IRR onlyRADB | 669 99% |
| 186.208.44.0/22 | No ROA | Other IRR onlyRADB | 669 99% |
| 186.208.46.0/24 | No ROA | Other IRR onlyRADB | 2 0%low visibility |
| 212.39.161.0/24 | Valid | Nonecovered by 212.39.160.0/19 | 673 100% |
| 212.39.172.0/24 | Valid | Nonecovered by 212.39.160.0/19 | 673 100% |
| 212.39.176.0/24 | Valid | Nonecovered by 212.39.160.0/19 | 673 100% |
| 212.39.177.0/24 | Valid | Nonecovered by 212.39.160.0/19 | 673 100% |
| 212.39.178.0/24 | Valid | Nonecovered by 212.39.160.0/19 | 673 100% |
| 212.39.184.0/24 | Valid | Nonecovered by 212.39.160.0/19 | 673 100% |
| 212.39.185.0/24 | Valid | Nonecovered by 212.39.160.0/19 | 673 100% |
| 84.22.76.0/24 | Valid | None | 672 100% |
| 212.39.170.0/24 | Valid | Nonecovered by 212.39.160.0/19 | 671 100% |
| 61.200.83.144/28 | Valid | Other IRR onlyNTTCOM | 28 4%low visibility |
| 64.19.240.0/20 | Valid | RIR databaseARIN | 673 100% |
| 64.49.144.0/24 | Valid | RIR databaseARIN | 673 100% |
| 72.2.224.0/20 | Valid | RIR databaseARIN | 673 100% |
| 79.140.200.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 89.21.180.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.254.19.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 103.27.162.0/24 | Valid | RIR databaseAPNIC, REACH | 673 100% |
| 185.7.15.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 202.80.161.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 202.80.163.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 202.80.169.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 202.80.170.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 202.80.171.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 202.80.172.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 202.80.174.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 202.80.175.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 202.174.155.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.88.86.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 203.88.87.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.88.88.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 203.88.89.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 203.88.90.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 207.241.174.0/24 | Valid | RIR databaseARIN | 673 100% |
| 216.226.74.0/23 | Valid | RIR databaseARIN | 673 100% |
| 72.2.236.0/24 | Valid | RIR databaseARIN | 672 100% |
| 72.2.239.0/24 | Valid | RIR databaseARIN | 672 100% |
| 74.119.160.0/24 | Valid | RIR databaseARIN | 672 100% |
| 74.119.161.0/24 | Valid | RIR databaseARIN | 672 100% |
| 74.119.163.0/24 | Valid | RIR databaseARIN | 672 100% |
| 74.119.164.0/24 | Valid | RIR databaseARIN | 672 100% |
| 74.119.165.0/24 | Valid | RIR databaseARIN | 672 100% |
| 74.119.166.0/24 | Valid | RIR databaseARIN | 672 100% |
| 74.119.167.0/24 | Valid | RIR databaseARIN | 672 100% |
| 89.254.18.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 103.27.160.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.27.161.0/24 | Valid | RIR databaseAPNIC, REACH | 672 100% |
| 111.92.178.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.80.160.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 202.80.162.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
| 202.80.165.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 202.80.166.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 202.80.167.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 672 100% |
| 202.174.130.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.174.157.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.174.159.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 203.88.95.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 79.140.194.0/24 | Valid | RIR databaseNTTCOM, RIPE | 671 100% |
| 79.140.202.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 202.174.156.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 212.39.162.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.39.164.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.39.166.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.39.167.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.39.173.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.39.174.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.39.180.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.39.190.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.39.160.0/19 | Valid | RIR databaseALTDB, RIPE | 2 0%low visibility |
AS-SET
AS4913 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 58 are in fix.csv.
- ROA: none4
- Route object: none9
- Route object: RIR5
- Route object: not announced40
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 186.208.32.0/23 | No ROA covers it. Add a ROA for AS4913, maxLength 23. |
| Route object: RIR | 186.208.32.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 186.208.36.0/22 | No ROA covers it. Add a ROA for AS4913, maxLength 22. |
| Route object: RIR | 186.208.36.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 186.208.44.0/22 | No ROA covers it. Add a ROA for AS4913, maxLength 22. |
| Route object: RIR | 186.208.44.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 186.208.46.0/24 | No ROA covers it. Add a ROA for AS4913, maxLength 24. |
| Route object: RIR | 186.208.46.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 212.39.161.0/24 | No route object for it. A route object for 212.39.160.0/19 with origin AS4913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4913 in the RIR database for the space. |
| Route object: none | 212.39.172.0/24 | No route object for it. A route object for 212.39.160.0/19 with origin AS4913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4913 in the RIR database for the space. |
| Route object: none | 212.39.176.0/24 | No route object for it. A route object for 212.39.160.0/19 with origin AS4913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4913 in the RIR database for the space. |
| Route object: none | 212.39.177.0/24 | No route object for it. A route object for 212.39.160.0/19 with origin AS4913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4913 in the RIR database for the space. |
| Route object: none | 212.39.178.0/24 | No route object for it. A route object for 212.39.160.0/19 with origin AS4913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4913 in the RIR database for the space. |
| Route object: none | 212.39.184.0/24 | No route object for it. A route object for 212.39.160.0/19 with origin AS4913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4913 in the RIR database for the space. |
| Route object: none | 212.39.185.0/24 | No route object for it. A route object for 212.39.160.0/19 with origin AS4913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4913 in the RIR database for the space. |
| Route object: none | 84.22.76.0/24 | No route object for it. Add a route object with origin AS4913 in the RIR database for the space. |
| Route object: none | 212.39.170.0/24 | No route object for it. A route object for 212.39.160.0/19 with origin AS4913 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4913 in the RIR database for the space. |
| Route object: RIR | 61.200.83.144/28 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS4913 whose prefix no peer sees AS4913 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.235.0.0/24 | RIPE | Invalid: origin |
| 46.235.3.0/24 | RIPE | Invalid: origin |
| 72.2.238.0/24 | ARIN | Valid |
| 119.252.225.0/24 | NTTCOM | No ROA |
| 119.252.226.0/24 | NTTCOM | No ROA |
| 119.252.227.0/24 | NTTCOM | No ROA |
| 119.252.228.0/24 | NTTCOM | No ROA |
| 119.252.229.0/24 | NTTCOM | No ROA |
| 119.252.230.0/24 | NTTCOM | No ROA |
| 119.252.231.0/24 | NTTCOM | No ROA |
| 119.252.232.0/24 | NTTCOM | No ROA |
| 119.252.233.0/24 | NTTCOM | No ROA |
| 119.252.234.0/24 | NTTCOM | No ROA |
| 119.252.235.0/24 | NTTCOM | No ROA |
| 119.252.236.0/24 | NTTCOM | No ROA |
| 119.252.237.0/24 | NTTCOM | No ROA |
| 119.252.238.0/24 | NTTCOM | No ROA |
| 119.252.239.0/24 | NTTCOM | No ROA |
| 175.176.247.0/24 | NTTCOM | No ROA |
| 175.176.249.0/24 | NTTCOM | No ROA |
| 186.208.32.0/20 | RADB | No ROA |
| 186.208.32.0/21 | RADB | No ROA |
| 186.208.40.0/21 | RADB | No ROA |
| 204.177.208.0/22 | ARIN | No ROA |
| 204.255.216.0/21 | ARIN | No ROA |
| 209.245.214.0/23 | ARIN | No ROA |
| 212.39.160.0/24 | RIPE | Valid |
| 212.39.163.0/24 | RIPE | Valid |
| 212.39.165.0/24 | RIPE | Valid |
| 212.39.168.0/24 | RIPE | Valid |
| 212.39.169.0/24 | RIPE | Valid |
| 212.39.171.0/24 | RIPE | Valid |
| 212.39.175.0/24 | RIPE | Valid |
| 212.39.179.0/24 | RIPE | Valid |
| 212.39.181.0/24 | RIPE | Valid |
| 212.39.182.0/24 | RIPE | Valid |
| 212.39.183.0/24 | RIPE | Valid |
| 212.39.186.0/23 | RIPE | Valid |
| 212.39.188.0/23 | RIPE | Valid |
| 212.39.191.0/24 | RIPE | 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.