bgpreport

Network · data from 2026-11-12

AS205771 OCTAPLUS

Registry name: OCTAPLUSUK OCTAPLUS NETWORKS LTD, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS205771, 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.
154.49.72.0/22 No ROA None 2 0%low visibility 2
154.56.240.0/21 No ROA None 2 0%low visibility 2
154.62.140.0/22 No ROA None 2 0%low visibility 2
154.56.232.0/22 No ROA Other IRR onlyRADB 668 99% 67
85.8.196.0/24 Valid RIR databaseRIPE 670 100% 67
89.21.65.0/24 Valid RIR databaseRIPE 670 100% 67
128.127.149.0/24 Valid RIR databaseRIPE 668 99% 67
128.127.150.0/24 Valid RIR databaseRIPE 668 99% 67
191.101.24.0/24 Valid RIR databaseRADB, RIPE 668 99% 67
2a13:740::/32 Valid RIR databaseRIPE 635 100% 69
2a13:741::/32 Valid RIR databaseRIPE 635 100% 69
2a13:742::/32 Valid RIR databaseRIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS205771: AS-OCTAPLUSUK. 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 (AS205771 isn't in the set, or no route object for AS205771 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 objectsAS205771 in itNot covered
AS-OCTAPLUSUK RIPE 119 Yes 3

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 8 are in fix.csv.

  • ROA: none4
  • Route object: none3
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none154.49.72.0/22No ROA covers it. Add a ROA for AS205771, maxLength 22.2 of 673
Route object: none154.49.72.0/22No route object for it. Add a route object with origin AS205771 in the RIR database for the space.2 of 673
ROA: none154.56.240.0/21No ROA covers it. Add a ROA for AS205771, maxLength 21.2 of 673
Route object: none154.56.240.0/21No route object for it. Add a route object with origin AS205771 in the RIR database for the space.2 of 673
ROA: none154.62.140.0/22No ROA covers it. Add a ROA for AS205771, maxLength 22.2 of 673
Route object: none154.62.140.0/22No route object for it. Add a route object with origin AS205771 in the RIR database for the space.2 of 673
ROA: none154.56.232.0/22No ROA covers it. Add a ROA for AS205771, maxLength 22.668 of 673
Route object: RIR154.56.232.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

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