Network · data from 2026-11-12
AS51263 County Broadband Ltd
Registry name: COUNTYBB County Broadband Ltd, GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS51263, 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.164.180.0/24 | Invalid: maxLength | Nonecovered by 185.164.180.0/22 | 43 6%low visibility |
| 185.25.56.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 178.251.176.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.251.177.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.251.178.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.251.179.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.251.180.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.251.181.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.251.182.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.251.183.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 62.56.176.0/20 | Valid | RIR databaseRIPE | 671 100% |
| 136.148.152.0/21 | Valid | RIR databaseRIPE | 671 100% |
| 168.86.192.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 185.164.180.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 213.244.200.0/21 | Valid | RIR databaseRIPE | 671 100% |
| 2a0b:4c00::/29 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS51263: AS-CBB. 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 (AS51263 isn't in the set, or no route object for AS51263 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 | AS51263 in it | Not covered |
|---|---|---|---|---|---|
| AS-CBB | RIPE | 1 | 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 4 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 185.164.180.0/24 | ROA 185.164.180.0/22 AS51263 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 185.164.180.0/24. |
| Route object: none | 185.164.180.0/24 | No route object for it. A route object for 185.164.180.0/22 with origin AS51263 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51263 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS51263 whose prefix no peer sees AS51263 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 178.251.176.0/21 | RIPE | Valid |
| 2a03:e240::/32 | 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.