Network · data from 2026-11-12
AS393844 PINE-NET - Pine Telephone Company, INC.
Registry name: PINE-NET - Pine Telephone Company, INC., US · not in PeeringDB
37IPv4 routes
100.0% RPKI valid · 2.7% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
36 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
7Route objects not announced
registered with origin AS393844, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS393844, 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.
| 69.12.125.0/24 | Valid | Nonecovered by 69.12.112.0/20 | 673 100% |
| 69.12.112.0/21 | Valid | Nonecovered by 69.12.112.0/20 | 671 100% |
| 69.12.124.0/24 | Valid | Nonecovered by 69.12.112.0/20 | 671 100% |
| 69.12.127.0/24 | Valid | Nonecovered by 69.12.112.0/20 | 671 100% |
| 104.160.96.0/21 | Valid | Nonecovered by 104.160.96.0/19 | 670 100% |
| 104.160.104.0/22 | Valid | Nonecovered by 104.160.96.0/19 | 670 100% |
| 104.160.108.0/24 | Valid | Nonecovered by 104.160.96.0/19 | 670 100% |
| 104.160.110.0/24 | Valid | Nonecovered by 104.160.96.0/19 | 670 100% |
| 104.160.111.0/24 | Valid | Nonecovered by 104.160.96.0/19 | 670 100% |
| 104.160.112.0/22 | Valid | Nonecovered by 104.160.96.0/19 | 670 100% |
| 104.160.116.0/22 | Valid | Nonecovered by 104.160.96.0/19 | 670 100% |
| 104.160.120.0/22 | Valid | Nonecovered by 104.160.96.0/19 | 670 100% |
| 104.160.120.0/24 | Valid | Nonecovered by 104.160.96.0/19 | 670 100% |
| 104.160.124.0/22 | Valid | Nonecovered by 104.160.96.0/19 | 670 100% |
| 167.160.224.0/20 | Valid | Nonecovered by 167.160.224.0/19 | 670 100% |
| 167.160.240.0/21 | Valid | Nonecovered by 167.160.224.0/19 | 670 100% |
| 167.160.248.0/22 | Valid | Nonecovered by 167.160.224.0/19 | 670 100% |
| 167.160.252.0/24 | Valid | Nonecovered by 167.160.224.0/19 | 670 100% |
| 167.160.253.0/24 | Valid | Nonecovered by 167.160.224.0/19 | 670 100% |
| 167.160.254.0/24 | Valid | Nonecovered by 167.160.224.0/19 | 670 100% |
| 167.160.255.0/24 | Valid | Nonecovered by 167.160.224.0/19 | 670 100% |
| 168.203.16.0/24 | Valid | Nonecovered by 168.203.16.0/20 | 670 100% |
| 168.203.17.0/24 | Valid | Nonecovered by 168.203.16.0/20 | 670 100% |
| 168.203.18.0/23 | Valid | Nonecovered by 168.203.16.0/20 | 670 100% |
| 168.203.18.0/24 | Valid | Nonecovered by 168.203.16.0/20 | 670 100% |
| 168.203.19.0/24 | Valid | Nonecovered by 168.203.16.0/20 | 670 100% |
| 168.203.20.0/23 | Valid | Nonecovered by 168.203.16.0/20 | 670 100% |
| 168.203.20.0/24 | Valid | Nonecovered by 168.203.16.0/20 | 670 100% |
| 168.203.21.0/24 | Valid | Nonecovered by 168.203.16.0/20 | 670 100% |
| 168.203.24.0/24 | Valid | Nonecovered by 168.203.16.0/20 | 670 100% |
| 168.203.25.0/24 | Valid | Nonecovered by 168.203.16.0/20 | 670 100% |
| 168.203.26.0/23 | Valid | Nonecovered by 168.203.16.0/20 | 670 100% |
| 168.203.28.0/24 | Valid | Nonecovered by 168.203.16.0/20 | 670 100% |
| 168.203.29.0/24 | Valid | Nonecovered by 168.203.16.0/20 | 670 100% |
| 168.203.30.0/24 | Valid | Nonecovered by 168.203.16.0/20 | 670 100% |
| 168.203.31.0/24 | Valid | Nonecovered by 168.203.16.0/20 | 670 100% |
| 192.24.16.0/20 | Valid | RIR databaseARIN, RADB | 670 100% |
AS-SET
AS393844 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 43 are in fix.csv.
- Route object: none36
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 69.12.125.0/24 | No route object for it. A route object for 69.12.112.0/20 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 69.12.112.0/21 | No route object for it. A route object for 69.12.112.0/20 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 69.12.124.0/24 | No route object for it. A route object for 69.12.112.0/20 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 69.12.127.0/24 | No route object for it. A route object for 69.12.112.0/20 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 104.160.96.0/21 | No route object for it. A route object for 104.160.96.0/19 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 104.160.104.0/22 | No route object for it. A route object for 104.160.96.0/19 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 104.160.108.0/24 | No route object for it. A route object for 104.160.96.0/19 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 104.160.110.0/24 | No route object for it. A route object for 104.160.96.0/19 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 104.160.111.0/24 | No route object for it. A route object for 104.160.96.0/19 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 104.160.112.0/22 | No route object for it. A route object for 104.160.96.0/19 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 104.160.116.0/22 | No route object for it. A route object for 104.160.96.0/19 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 104.160.120.0/22 | No route object for it. A route object for 104.160.96.0/19 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 104.160.120.0/24 | No route object for it. A route object for 104.160.96.0/19 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 104.160.124.0/22 | No route object for it. A route object for 104.160.96.0/19 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 167.160.224.0/20 | No route object for it. A route object for 167.160.224.0/19 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 167.160.240.0/21 | No route object for it. A route object for 167.160.224.0/19 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 167.160.248.0/22 | No route object for it. A route object for 167.160.224.0/19 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 167.160.252.0/24 | No route object for it. A route object for 167.160.224.0/19 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 167.160.253.0/24 | No route object for it. A route object for 167.160.224.0/19 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 167.160.254.0/24 | No route object for it. A route object for 167.160.224.0/19 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 167.160.255.0/24 | No route object for it. A route object for 167.160.224.0/19 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 168.203.16.0/24 | No route object for it. A route object for 168.203.16.0/20 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 168.203.17.0/24 | No route object for it. A route object for 168.203.16.0/20 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 168.203.18.0/23 | No route object for it. A route object for 168.203.16.0/20 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 168.203.18.0/24 | No route object for it. A route object for 168.203.16.0/20 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 168.203.19.0/24 | No route object for it. A route object for 168.203.16.0/20 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 168.203.20.0/23 | No route object for it. A route object for 168.203.16.0/20 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 168.203.20.0/24 | No route object for it. A route object for 168.203.16.0/20 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 168.203.21.0/24 | No route object for it. A route object for 168.203.16.0/20 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 168.203.24.0/24 | No route object for it. A route object for 168.203.16.0/20 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 168.203.25.0/24 | No route object for it. A route object for 168.203.16.0/20 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 168.203.26.0/23 | No route object for it. A route object for 168.203.16.0/20 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 168.203.28.0/24 | No route object for it. A route object for 168.203.16.0/20 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 168.203.29.0/24 | No route object for it. A route object for 168.203.16.0/20 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 168.203.30.0/24 | No route object for it. A route object for 168.203.16.0/20 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
| Route object: none | 168.203.31.0/24 | No route object for it. A route object for 168.203.16.0/20 with origin AS393844 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393844 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS393844 whose prefix no peer sees AS393844 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 69.12.112.0/20 | ARIN, RADB | Valid |
| 104.160.96.0/19 | ARIN, RADB | Valid |
| 167.160.224.0/19 | ARIN, RADB | Valid |
| 168.203.16.0/20 | ARIN | Valid |
| 206.126.232.0/23 | ARIN, RADB | Valid |
| 2001:470:450::/48 | ARIN | Valid |
| 2600:a400::/28 | 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.