Network · data from 2026-11-12
AS14408 AS-EMPIRECLS-SECAUCUS - Empire International, Ltd.
Registry name: AS-EMPIRECLS-SECAUCUS - Empire International, Ltd., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS14408, 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.
| 66.207.152.0/24 | No ROA | Nonecovered by 66.207.144.0/20 | 673 100% |
| 66.207.154.0/24 | No ROA | Nonecovered by 66.207.144.0/20 | 673 100% |
| 66.207.157.0/24 | No ROA | Other origin onlycovered by 66.207.144.0/20 | 673 100% |
| 66.207.144.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 66.207.147.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 66.207.149.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 66.207.153.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 66.207.158.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
AS-SET
AS14408 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 25 are in fix.csv.
- ROA: none8
- Route object: none3
- Route object: RIR5
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 66.207.152.0/24 | No ROA covers it. Add a ROA for AS14408, maxLength 24. |
| Route object: none | 66.207.152.0/24 | No route object for it. A route object for 66.207.144.0/20 with origin AS14408 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14408 in the RIR database for the space. |
| ROA: none | 66.207.154.0/24 | No ROA covers it. Add a ROA for AS14408, maxLength 24. |
| Route object: none | 66.207.154.0/24 | No route object for it. A route object for 66.207.144.0/20 with origin AS14408 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14408 in the RIR database for the space. |
| ROA: none | 66.207.157.0/24 | No ROA covers it. Add a ROA for AS14408, maxLength 24. |
| Route object: none | 66.207.157.0/24 | Route objects for it name AS7029. A route object for 66.207.144.0/20 with origin AS14408 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14408 in the RIR database for the space. |
| ROA: none | 66.207.144.0/24 | No ROA covers it. Add a ROA for AS14408, maxLength 24. |
| Route object: RIR | 66.207.144.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 66.207.147.0/24 | No ROA covers it. Add a ROA for AS14408, maxLength 24. |
| Route object: RIR | 66.207.147.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 66.207.149.0/24 | No ROA covers it. Add a ROA for AS14408, maxLength 24. |
| Route object: RIR | 66.207.149.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 66.207.153.0/24 | No ROA covers it. Add a ROA for AS14408, maxLength 24. |
| Route object: RIR | 66.207.153.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 66.207.158.0/24 | No ROA covers it. Add a ROA for AS14408, maxLength 24. |
| Route object: RIR | 66.207.158.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS14408 whose prefix no peer sees AS14408 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 66.207.144.0/20 | RADB | No ROA |
| 66.207.145.0/24 | RADB | No ROA |
| 66.207.146.0/24 | RADB | No ROA |
| 66.207.148.0/24 | RADB | No ROA |
| 66.207.150.0/24 | RADB | No ROA |
| 66.207.151.0/24 | RADB | No ROA |
| 66.207.155.0/24 | RADB | No ROA |
| 66.207.156.0/24 | RADB | No ROA |
| 66.207.159.0/24 | RADB | No ROA |
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.