Network · data from 2026-11-12
AS43872 Optinet U.K.
Registry name: OPTINET Optinet U.K. Limited, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS43872, 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.
| 89.222.62.0/23 | Valid | Nonecovered by 89.222.48.0/20 | 673 100% |
| 84.38.246.0/24 | Valid | None | 672 100% |
| 89.222.48.0/21 | Valid | Nonecovered by 89.222.48.0/20 | 672 100% |
| 89.222.56.0/22 | Valid | Nonecovered by 89.222.48.0/20 | 672 100% |
| 89.222.60.0/23 | Valid | Nonecovered by 89.222.48.0/20 | 672 100% |
| 92.118.111.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.247.103.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.253.252.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 176.101.169.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.183.20.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.187.61.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.253.176.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 193.105.189.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.247.94.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.247.101.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.247.165.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.234.28.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.198.183.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.136.108.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 91.201.105.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 2a0b:180::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a10:c740::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a10:c7c0::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a10:c8c0::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a10:c9c0::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a10:cac0::/29 | Valid | RIR databaseRIPE | 632 99% |
| 2a0d:1e80::/29 | Valid | RIR databaseRIPE | 604 95% |
AS-SET
AS43872's PeeringDB record names no 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 6 are in fix.csv.
- Route object: none5
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 89.222.62.0/23 | No route object for it. A route object for 89.222.48.0/20 with origin AS43872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43872 in the RIR database for the space. |
| Route object: none | 84.38.246.0/24 | No route object for it. Add a route object with origin AS43872 in the RIR database for the space. |
| Route object: none | 89.222.48.0/21 | No route object for it. A route object for 89.222.48.0/20 with origin AS43872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43872 in the RIR database for the space. |
| Route object: none | 89.222.56.0/22 | No route object for it. A route object for 89.222.48.0/20 with origin AS43872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43872 in the RIR database for the space. |
| Route object: none | 89.222.60.0/23 | No route object for it. A route object for 89.222.48.0/20 with origin AS43872 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43872 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS43872 whose prefix no peer sees AS43872 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.222.48.0/20 | RIPE | 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.