bgpreport

Network · data from 2026-11-12

AS60426 WightFibre

Registry name: WIGHTFIBRE WightFibre Limited, GB · PeeringDB

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

Announced routes

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

86.63.0.0/19 No ROA Nonecovered by 86.63.0.0/18 673 100% 67
86.63.32.0/19 No ROA Nonecovered by 86.63.0.0/18 673 100% 67
109.234.176.0/22 No ROA Nonecovered by 109.234.176.0/21 673 100% 67
109.234.180.0/22 No ROA Nonecovered by 109.234.176.0/21 673 100% 67
185.17.164.0/23 No ROA Nonecovered by 185.17.164.0/22 673 100% 67
185.17.166.0/23 No ROA Nonecovered by 185.17.164.0/22 673 100% 67
86.63.0.0/18 No ROA RIR databaseRIPE 668 99% 67
109.234.176.0/21 No ROA RIR databaseRIPE 668 99% 67
185.17.164.0/22 No ROA RIR databaseRIPE 666 99% 67
2a00:8b47::/32 No ROA RIR databaseRIPE 635 100% 67
2a00:8b40::/29 No ROA RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS60426: AS-WIGHTFIBRE. 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 (AS60426 isn't in the set, or no route object for AS60426 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 objectsAS60426 in itNot covered
AS-WIGHTFIBRE RIPE 219 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 17 are in fix.csv.

  • ROA: none11
  • Route object: none6
ChangePrefix or setDetailFull-table peers
ROA: none86.63.0.0/19No ROA covers it. Add a ROA for AS60426, maxLength 19.673 of 673
Route object: none86.63.0.0/19No route object for it. A route object for 86.63.0.0/18 with origin AS60426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60426 in the RIR database for the space.673 of 673
ROA: none86.63.32.0/19No ROA covers it. Add a ROA for AS60426, maxLength 19.673 of 673
Route object: none86.63.32.0/19No route object for it. A route object for 86.63.0.0/18 with origin AS60426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60426 in the RIR database for the space.673 of 673
ROA: none109.234.176.0/22No ROA covers it. Add a ROA for AS60426, maxLength 22.673 of 673
Route object: none109.234.176.0/22No route object for it. A route object for 109.234.176.0/21 with origin AS60426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60426 in the RIR database for the space.673 of 673
ROA: none109.234.180.0/22No ROA covers it. Add a ROA for AS60426, maxLength 22.673 of 673
Route object: none109.234.180.0/22No route object for it. A route object for 109.234.176.0/21 with origin AS60426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60426 in the RIR database for the space.673 of 673
ROA: none185.17.164.0/23No ROA covers it. Add a ROA for AS60426, maxLength 23.673 of 673
Route object: none185.17.164.0/23No route object for it. A route object for 185.17.164.0/22 with origin AS60426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60426 in the RIR database for the space.673 of 673
ROA: none185.17.166.0/23No ROA covers it. Add a ROA for AS60426, maxLength 23.673 of 673
Route object: none185.17.166.0/23No route object for it. A route object for 185.17.164.0/22 with origin AS60426 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60426 in the RIR database for the space.673 of 673
ROA: none86.63.0.0/18No ROA covers it. Add a ROA for AS60426, maxLength 18.668 of 673
ROA: none109.234.176.0/21No ROA covers it. Add a ROA for AS60426, maxLength 21.668 of 673
ROA: none185.17.164.0/22No ROA covers it. Add a ROA for AS60426, maxLength 22.666 of 673
ROA: none2a00:8b47::/32No ROA covers it. Add a ROA for AS60426, maxLength 32.635 of 636
ROA: none2a00:8b40::/29No ROA covers it. Add a ROA for AS60426, maxLength 29.634 of 636

Route objects not announced

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