bgpreport

Network · data from 2026-11-12

AS41896 SHETTEL-AS Shetland Islands Council

Registry name: SHETTEL-AS Shetland Islands Council, GB · not in PeeringDB

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

Announced routes

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

37.208.87.0/24 No ROA Other origin onlycovered by 37.208.84.0/22 397 59% 66
37.208.80.0/22 No ROA RIR databaseRIPE 673 100% 67
37.208.84.0/22 No ROA RIR databaseRIPE 673 100% 67
37.235.40.0/24 No ROA RIR databaseRIPE 672 100% 67
37.235.41.0/24 No ROA RIR databaseRIPE 672 100% 67
37.235.42.0/24 No ROA RIR databaseRIPE 672 100% 67
37.235.44.0/24 No ROA RIR databaseRIPE 672 100% 67
37.235.45.0/24 No ROA RIR databaseRIPE 672 100% 67
37.235.46.0/24 No ROA RIR databaseRIPE 306 45% 64
37.235.47.0/24 No ROA RIR databaseRIPE 306 45% 64

AS-SET

AS41896 isn't in PeeringDB, where networks name their AS-SET.

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

  • ROA: none10
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none37.208.87.0/24No ROA covers it. Add a ROA for AS41896, maxLength 24.397 of 673
Route object: none37.208.87.0/24Route objects for it name AS211438. A route object for 37.208.84.0/22 with origin AS41896 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41896 in the RIR database for the space.397 of 673
ROA: none37.208.80.0/22No ROA covers it. Add a ROA for AS41896, maxLength 22.673 of 673
ROA: none37.208.84.0/22No ROA covers it. Add a ROA for AS41896, maxLength 22.673 of 673
ROA: none37.235.40.0/24No ROA covers it. Add a ROA for AS41896, maxLength 24.672 of 673
ROA: none37.235.41.0/24No ROA covers it. Add a ROA for AS41896, maxLength 24.672 of 673
ROA: none37.235.42.0/24No ROA covers it. Add a ROA for AS41896, maxLength 24.672 of 673
ROA: none37.235.44.0/24No ROA covers it. Add a ROA for AS41896, maxLength 24.672 of 673
ROA: none37.235.45.0/24No ROA covers it. Add a ROA for AS41896, maxLength 24.672 of 673
ROA: none37.235.46.0/24No ROA covers it. Add a ROA for AS41896, maxLength 24.306 of 673
ROA: none37.235.47.0/24No ROA covers it. Add a ROA for AS41896, maxLength 24.306 of 673

Route objects not announced

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

37.208.80.0/21RIPENo 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.