Network · data from 2026-11-12
AS29611 Elite Limited
Registry name: ELITE-AS Elite Limited, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS29611, 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.
| 45.89.56.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 45.157.84.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.2.216.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.2.216.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.2.217.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.2.218.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.2.219.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.43.184.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.43.184.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.43.185.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.43.186.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.43.187.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.73.184.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.73.184.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.73.185.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.73.186.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.73.187.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.119.52.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.119.52.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.119.53.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.119.54.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.119.55.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.68.240.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 217.68.240.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.68.241.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.68.242.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.68.243.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.68.244.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.68.245.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.68.246.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.68.247.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.68.248.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.68.249.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.68.250.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.68.251.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.68.252.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.68.253.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.68.254.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.68.255.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.69.32.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 217.69.32.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.69.33.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.69.34.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.69.35.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.69.36.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.69.37.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.69.38.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.69.39.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.69.40.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.69.41.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.69.42.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.69.43.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.69.44.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.69.45.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.69.46.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.69.47.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.89.56.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.89.57.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.89.58.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.89.59.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.157.84.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.157.85.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.157.86.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.157.87.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a00:c20::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a03:2d20::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a04:95c0::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a06:8940::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a0e:c1c0::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a0f:5280::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS29611: RIPE::AS-ELITE RIPE::AS-ELITE-V6. 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 (AS29611 isn't in the set, or no route object for AS29611 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 | AS29611 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-ELITE | RIPE | 8 | 3 | Yes | 0 |
| RIPE::AS-ELITE-V6 | RIPE | 3 | 1 | Yes | 0 |
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS29611 is announced.
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.