Network · data from 2026-11-12
AS7271 LOOKAS - FIBERNETICS CORPORATION
Registry name: LOOKAS - FIBERNETICS CORPORATION, CA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS7271, 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.
| 74.205.212.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
AS-SET
AS7271 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 24 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced22
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 74.205.212.0/24 | No ROA covers it. Add a ROA for AS7271, maxLength 24. |
| Route object: RIR | 74.205.212.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS7271 whose prefix no peer sees AS7271 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 69.57.0.0/20 | RADB | No ROA |
| 192.80.57.0/24 | RADB | No ROA |
| 198.168.225.0/24 | RADB | No ROA |
| 199.60.228.0/23 | RADB | No ROA |
| 199.60.228.0/24 | RADB | No ROA |
| 199.60.229.0/24 | RADB | No ROA |
| 199.166.254.0/24 | RADB | No ROA |
| 199.233.183.0/24 | RADB | No ROA |
| 199.233.184.0/24 | RADB | No ROA |
| 204.174.254.0/24 | RADB | No ROA |
| 205.189.68.0/24 | RADB | No ROA |
| 205.189.76.0/24 | RADB | No ROA |
| 205.205.255.0/24 | RADB | No ROA |
| 205.233.198.0/24 | RADB | No ROA |
| 207.139.102.0/24 | RADB | No ROA |
| 207.139.171.0/24 | RADB | No ROA |
| 209.47.75.0/24 | RADB | No ROA |
| 209.205.5.0/24 | RADB | No ROA |
| 209.212.32.0/19 | RADB | No ROA |
| 216.66.128.0/19 | RADB | No ROA |
| 216.66.160.0/20 | RADB | No ROA |
| 216.66.192.0/20 | 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.