Network · data from 2026-11-12
AS199775 Connexin Limited
Registry name: Connexin-Limited Connexin Limited, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS199775, 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.
| 185.168.132.0/23 | Valid | Nonecovered by 185.168.132.0/22 | 672 100% |
| 185.168.134.0/24 | Valid | Nonecovered by 185.168.132.0/22 | 672 100% |
| 185.168.135.0/24 | Valid | Nonecovered by 185.168.132.0/22 | 672 100% |
| 194.126.152.0/24 | Valid | Nonecovered by 194.126.152.0/22 | 672 100% |
| 185.42.2.0/23 | Valid | Nonecovered by 185.42.0.0/22 | 671 100% |
| 185.182.52.0/23 | Valid | Nonecovered by 185.182.52.0/22 | 671 100% |
| 185.182.54.0/23 | Valid | Nonecovered by 185.182.52.0/22 | 671 100% |
| 185.42.0.0/23 | Valid | Nonecovered by 185.42.0.0/22 | 668 99% |
| 185.242.218.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.94.32.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.6.152.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.65.164.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.95.108.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.208.240.0/22 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS199775: AS-CONNEXIN. 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 (AS199775 isn't in the set, or no route object for AS199775 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 | AS199775 in it | Not covered |
|---|---|---|---|---|---|
| AS-CONNEXIN | RIPE | 3 | 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 13 are in fix.csv.
- Route object: none8
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.168.132.0/23 | No route object for it. A route object for 185.168.132.0/22 with origin AS199775 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199775 in the RIR database for the space. |
| Route object: none | 185.168.134.0/24 | No route object for it. A route object for 185.168.132.0/22 with origin AS199775 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199775 in the RIR database for the space. |
| Route object: none | 185.168.135.0/24 | No route object for it. A route object for 185.168.132.0/22 with origin AS199775 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199775 in the RIR database for the space. |
| Route object: none | 194.126.152.0/24 | No route object for it. A route object for 194.126.152.0/22 with origin AS199775 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199775 in the RIR database for the space. |
| Route object: none | 185.42.2.0/23 | No route object for it. A route object for 185.42.0.0/22 with origin AS199775 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199775 in the RIR database for the space. |
| Route object: none | 185.182.52.0/23 | No route object for it. A route object for 185.182.52.0/22 with origin AS199775 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199775 in the RIR database for the space. |
| Route object: none | 185.182.54.0/23 | No route object for it. A route object for 185.182.52.0/22 with origin AS199775 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199775 in the RIR database for the space. |
| Route object: none | 185.42.0.0/23 | No route object for it. A route object for 185.42.0.0/22 with origin AS199775 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199775 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS199775 whose prefix no peer sees AS199775 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.36.192.0/21 | RIPE | Valid |
| 185.42.0.0/22 | RIPE | Valid |
| 185.168.132.0/22 | RIPE | Valid |
| 185.182.52.0/22 | RIPE | Valid |
| 194.126.152.0/22 | RIPE | 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.