bgpreport

Network · data from 2026-11-12

AS201126 CDW UK

Registry name: CDW-UK-AS CDW Ltd, GB · PeeringDB

12IPv4 routes 0.0% RPKI valid · 91.7% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
12No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS201126, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS201126, 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.176.242.0/23 No ROA None 673 100% 67
91.240.17.0/24 No ROA RIR databaseRIPE 673 100% 67
153.92.43.0/24 No ROA RIR databaseRIPE 673 100% 67
153.92.44.0/24 No ROA RIR databaseRIPE 673 100% 67
153.92.45.0/24 No ROA RIR databaseRIPE 673 100% 67
153.92.46.0/24 No ROA RIR databaseRIPE 673 100% 67
157.97.128.0/22 No ROA RIR databaseRIPE 673 100% 67
185.74.25.0/24 No ROA RIR databaseRIPE 673 100% 67
185.74.26.0/24 No ROA RIR databaseRIPE 673 100% 67
185.74.27.0/24 No ROA RIR databaseRIPE 673 100% 67
188.116.54.0/24 No ROA RIR databaseRIPE 673 100% 67
194.105.149.0/24 No ROA RIR databaseRIPE 673 100% 67

AS-SET

PeeringDB's irr_as_set for AS201126: AS201126. 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 (AS201126 isn't in the set, or no route object for AS201126 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.

NameDatabaseASNsSets Route objectsAS201126 in itNot covered
AS201126 A single AS number, not a set: AS201126 (this network), 11 route objects.

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.

  • ROA: none12
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none185.176.242.0/23No ROA covers it. Add a ROA for AS201126, maxLength 23.673 of 673
Route object: none185.176.242.0/23No route object for it. Add a route object with origin AS201126 in the RIR database for the space.673 of 673
ROA: none91.240.17.0/24No ROA covers it. Add a ROA for AS201126, maxLength 24.673 of 673
ROA: none153.92.43.0/24No ROA covers it. Add a ROA for AS201126, maxLength 24.673 of 673
ROA: none153.92.44.0/24No ROA covers it. Add a ROA for AS201126, maxLength 24.673 of 673
ROA: none153.92.45.0/24No ROA covers it. Add a ROA for AS201126, maxLength 24.673 of 673
ROA: none153.92.46.0/24No ROA covers it. Add a ROA for AS201126, maxLength 24.673 of 673
ROA: none157.97.128.0/22No ROA covers it. Add a ROA for AS201126, maxLength 22.673 of 673
ROA: none185.74.25.0/24No ROA covers it. Add a ROA for AS201126, maxLength 24.673 of 673
ROA: none185.74.26.0/24No ROA covers it. Add a ROA for AS201126, maxLength 24.673 of 673
ROA: none185.74.27.0/24No ROA covers it. Add a ROA for AS201126, maxLength 24.673 of 673
ROA: none188.116.54.0/24No ROA covers it. Add a ROA for AS201126, maxLength 24.673 of 673
ROA: none194.105.149.0/24No ROA covers it. Add a ROA for AS201126, maxLength 24.673 of 673

Route objects not announced

Every route object with origin AS201126 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.