Network · data from 2026-11-12
AS401375 NYECOM-NET - Nyecom Teleservices
Registry name: NYECOM-NET - Nyecom Teleservices, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS401375, 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.129.40.0/22 | No ROA | RIR databaseARIN | 671 100% |
AS-SET
AS401375 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 5 are in fix.csv.
- ROA: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 66.129.40.0/22 | No ROA covers it. Add a ROA for AS401375, maxLength 22. |
Route objects not announced
Route objects with origin AS401375 whose prefix no peer sees AS401375 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 66.129.40.0/24 | ARIN | No ROA |
| 66.129.41.0/24 | ARIN | No ROA |
| 66.129.42.0/24 | ARIN | No ROA |
| 66.129.43.0/24 | ARIN | 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.