bgpreport

Network · data from 2026-11-12

AS44403 BRISTOL-CITY-COUNCIL Bristol City Council

Registry name: BRISTOL-CITY-COUNCIL Bristol City Council, GB · not in PeeringDB

8IPv4 routes 0.0% RPKI valid · 25.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
8No 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 AS44403, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS44403, 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.
193.35.232.0/22 No ROA Nonecovered by 193.35.232.0/21 672 100% 67
193.35.236.0/22 No ROA Nonecovered by 193.35.232.0/21 672 100% 67
193.35.238.0/24 No ROA Nonecovered by 193.35.232.0/21 672 100% 68
193.35.239.0/24 No ROA Nonecovered by 193.35.232.0/21 671 100% 68
195.246.108.0/24 No ROA Nonecovered by 195.246.108.0/23 671 100% 68
195.246.109.0/24 No ROA Nonecovered by 195.246.108.0/23 671 100% 68
193.35.232.0/21 No ROA RIR databaseRIPE 672 100% 68
195.246.108.0/23 No ROA RIR databaseRIPE 671 100% 68

AS-SET

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

  • ROA: none8
  • Route object: none6
ChangePrefix or setDetailFull-table peers
ROA: none193.35.232.0/22No ROA covers it. Add a ROA for AS44403, maxLength 22.672 of 673
Route object: none193.35.232.0/22No route object for it. A route object for 193.35.232.0/21 with origin AS44403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44403 in the RIR database for the space.672 of 673
ROA: none193.35.236.0/22No ROA covers it. Add a ROA for AS44403, maxLength 22.672 of 673
Route object: none193.35.236.0/22No route object for it. A route object for 193.35.232.0/21 with origin AS44403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44403 in the RIR database for the space.672 of 673
ROA: none193.35.238.0/24No ROA covers it. Add a ROA for AS44403, maxLength 24.672 of 673
Route object: none193.35.238.0/24No route object for it. A route object for 193.35.232.0/21 with origin AS44403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44403 in the RIR database for the space.672 of 673
ROA: none193.35.239.0/24No ROA covers it. Add a ROA for AS44403, maxLength 24.671 of 673
Route object: none193.35.239.0/24No route object for it. A route object for 193.35.232.0/21 with origin AS44403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44403 in the RIR database for the space.671 of 673
ROA: none195.246.108.0/24No ROA covers it. Add a ROA for AS44403, maxLength 24.671 of 673
Route object: none195.246.108.0/24No route object for it. A route object for 195.246.108.0/23 with origin AS44403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44403 in the RIR database for the space.671 of 673
ROA: none195.246.109.0/24No ROA covers it. Add a ROA for AS44403, maxLength 24.671 of 673
Route object: none195.246.109.0/24No route object for it. A route object for 195.246.108.0/23 with origin AS44403 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44403 in the RIR database for the space.671 of 673
ROA: none193.35.232.0/21No ROA covers it. Add a ROA for AS44403, maxLength 21.672 of 673
ROA: none195.246.108.0/23No ROA covers it. Add a ROA for AS44403, maxLength 23.671 of 673

Route objects not announced

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