Network · data from 2026-11-12
AS12167 LightWave Networks - Dallas
Registry name: LIGHTWAVE-DALLAS - LightWave Networks, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS12167, 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.
| 104.232.33.0/24 | Valid | Nonecovered by 104.232.32.0/23 | 669 99% |
| 2606:b600:104::/48 | Valid | Nonecovered by 2606:b600:104::/47 | 635 100% |
| 2606:b600:110::/48 | Valid | Nonecovered by 2606:b600:110::/47 | 631 99% |
| 104.232.32.0/24 | Valid | Other IRR onlyNTTCOM | 669 99% |
| 69.166.96.0/24 | Valid | RIR databaseARIN | 672 100% |
| 107.161.146.0/24 | Valid | RIR databaseARIN | 672 100% |
| 107.161.144.0/23 | Valid | RIR databaseARIN | 671 100% |
| 2607:740:85::/48 | Valid | RIR databaseARIN | 635 100% |
| 2607:6b80:5d::/48 | Valid | RIR databaseARIN | 3 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS12167: AS-LWN-DALLAS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS12167 isn't in the set, or no route object for AS12167 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS12167 in it | Not covered |
|---|---|---|---|---|---|
| AS-LWN-DALLAS | ARIN | 2 | 1 | Yes | 0 |
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 15 are in fix.csv.
- Route object: none3
- Route object: RIR1
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 104.232.33.0/24 | No route object for it. A route object for 104.232.32.0/23 with origin AS12167 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12167 in the RIR database for the space. |
| Route object: none | 2606:b600:104::/48 | No route object for it. A route object for 2606:b600:104::/47 with origin AS12167 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12167 in the RIR database for the space. |
| Route object: none | 2606:b600:110::/48 | No route object for it. A route object for 2606:b600:110::/47 with origin AS12167 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12167 in the RIR database for the space. |
| Route object: RIR | 104.232.32.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS12167 whose prefix no peer sees AS12167 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 69.166.96.0/21 | RADB | No ROA |
| 104.232.32.0/22 | RADB | Valid |
| 104.232.32.0/23 | ARIN | Valid |
| 107.161.144.0/22 | RADB | No ROA |
| 107.161.147.0/24 | ARIN | Valid |
| 173.237.200.0/24 | ARIN | No ROA |
| 204.107.104.0/24 | RADB | No ROA |
| 2001:470:5d5::/48 | ARIN | Valid |
| 2606:b600:104::/47 | ARIN | Valid |
| 2606:b600:109::/48 | ARIN | Valid |
| 2606:b600:110::/47 | 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.