bgpreport

Network · data from 2026-11-12

AS51551 Capita Networking Solutions (Updata)

Registry name: CAPITA-AS Capita Business Services Ltd, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS51551, 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.

46.183.192.0/21 No ROA RIR databaseRIPE 673 100% 67
82.203.64.0/18 No ROA RIR databaseRIPE 673 100% 67
185.26.16.0/22 No ROA RIR databaseRIPE 673 100% 67
195.190.22.0/24 No ROA RIR databaseRIPE 671 100% 67

AS-SET

PeeringDB's irr_as_set for AS51551: RIPE::AS-UPDATA. 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 (AS51551 isn't in the set, or no route object for AS51551 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 objectsAS51551 in itNot covered
RIPE::AS-UPDATA RIPE 11141 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 10 are in fix.csv.

  • ROA: none4
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none46.183.192.0/21No ROA covers it. Add a ROA for AS51551, maxLength 21.673 of 673
ROA: none82.203.64.0/18No ROA covers it. Add a ROA for AS51551, maxLength 18.673 of 673
ROA: none185.26.16.0/22No ROA covers it. Add a ROA for AS51551, maxLength 22.673 of 673
ROA: none195.190.22.0/24No ROA covers it. Add a ROA for AS51551, maxLength 24.671 of 673

Route objects not announced

Route objects with origin AS51551 whose prefix no peer sees AS51551 announce. Many are kept on purpose (backup routes, space announced only in some places).

46.16.0.0/21RIPENo ROA
82.203.32.0/19RIPENo ROA
185.137.192.0/22RIPENo ROA
185.137.196.0/22RIPENo ROA
2a02:4340::/32RIPENo ROA
2a03:a5e0::/32RIPENo 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.