Network · data from 2026-11-12
AS267776 OPTIWISP
Registry name: AS267776 - OPTIWISP SPA, CL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267776, 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.
| 143.202.12.0/23 | Valid | Other IRR onlyRADB | 110 16% |
| 143.202.12.0/24 | Valid | Other IRR onlyRADB | 110 16% |
| 143.202.13.0/24 | Valid | Other IRR onlyRADB | 110 16% |
| 143.202.14.0/24 | Valid | Other IRR onlyRADB | 110 16% |
| 143.202.15.0/24 | Valid | Other IRR onlyRADB | 110 16% |
| 45.171.220.0/24 | Valid | Other IRR onlyRADB | 109 16% |
| 45.171.221.0/24 | Valid | Other IRR onlyRADB | 109 16% |
| 45.171.222.0/24 | Valid | Other IRR onlyRADB | 109 16% |
| 45.171.223.0/24 | Valid | Other IRR onlyRADB | 109 16% |
| 45.171.220.0/22 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 143.202.12.0/22 | Valid | RIR databaseLACNIC, RADB | 668 99% |
| 2803:e7a0::/32 | Valid | RIR databaseLACNIC | 630 99% |
AS-SET
PeeringDB's irr_as_set for AS267776: AS267776:AS-ALL. 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 (AS267776 isn't in the set, or no route object for AS267776 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 | AS267776 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS267776:AS-ALL | In no IRR database read today. | |||||
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 14 are in fix.csv.
- Route object: RIR9
- AS-SET: not found1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 143.202.12.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 143.202.12.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 143.202.13.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 143.202.14.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 143.202.15.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.171.220.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.171.221.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.171.222.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.171.223.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: not found | AS267776:AS-ALL | PeeringDB names AS267776:AS-ALL; no IRR database read has it. |
Route objects not announced
Route objects with origin AS267776 whose prefix no peer sees AS267776 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.171.220.0/23 | RADB | Valid |
| 45.171.222.0/23 | RADB | Valid |
| 143.202.14.0/23 | RADB | Valid |
| 2803:8e40::/32 | LACNIC | 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.