Network · data from 2026-11-12
AS62714 PHILLIPSDATA - Phillips Data, Inc.
Registry name: PHILLIPSDATA - Phillips Data, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS62714, 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.
| 162.220.76.0/24 | Valid | Nonecovered by 162.220.76.0/22 | 673 100% |
| 162.220.77.0/24 | Valid | Nonecovered by 162.220.76.0/22 | 673 100% |
| 162.220.78.0/24 | Valid | Nonecovered by 162.220.76.0/22 | 673 100% |
| 162.220.79.0/24 | Valid | Nonecovered by 162.220.76.0/22 | 673 100% |
| 2602:fe7a:1::/48 | Valid | Nonecovered by 2602:fe7a::/36 | 634 100% |
| 2602:fe7a::/48 | Valid | Nonecovered by 2602:fe7a::/36 | 633 100% |
| 2602:fe7a:2::/48 | Valid | Nonecovered by 2602:fe7a::/36 | 633 100% |
| 2602:fe7a:3::/48 | Valid | Nonecovered by 2602:fe7a::/36 | 633 100% |
| 2602:fe7a:4::/48 | Valid | Nonecovered by 2602:fe7a::/36 | 633 100% |
AS-SET
AS62714 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 11 are in fix.csv.
- Route object: none9
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 162.220.76.0/24 | No route object for it. A route object for 162.220.76.0/22 with origin AS62714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62714 in the RIR database for the space. |
| Route object: none | 162.220.77.0/24 | No route object for it. A route object for 162.220.76.0/22 with origin AS62714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62714 in the RIR database for the space. |
| Route object: none | 162.220.78.0/24 | No route object for it. A route object for 162.220.76.0/22 with origin AS62714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62714 in the RIR database for the space. |
| Route object: none | 162.220.79.0/24 | No route object for it. A route object for 162.220.76.0/22 with origin AS62714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62714 in the RIR database for the space. |
| Route object: none | 2602:fe7a:1::/48 | No route object for it. A route object for 2602:fe7a::/36 with origin AS62714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62714 in the RIR database for the space. |
| Route object: none | 2602:fe7a::/48 | No route object for it. A route object for 2602:fe7a::/36 with origin AS62714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62714 in the RIR database for the space. |
| Route object: none | 2602:fe7a:2::/48 | No route object for it. A route object for 2602:fe7a::/36 with origin AS62714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62714 in the RIR database for the space. |
| Route object: none | 2602:fe7a:3::/48 | No route object for it. A route object for 2602:fe7a::/36 with origin AS62714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62714 in the RIR database for the space. |
| Route object: none | 2602:fe7a:4::/48 | No route object for it. A route object for 2602:fe7a::/36 with origin AS62714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62714 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS62714 whose prefix no peer sees AS62714 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 162.220.76.0/22 | ARIN, RADB | Valid |
| 2602:fe7a::/36 | 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.