bgpreport

Network · data from 2026-11-12

AS28846 ITV PLC

Registry name: ASCARLTONTV ITV Services Limited, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28846, 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.
194.36.70.0/24 No ROA Nonecovered by 194.36.70.0/23 673 100% 67
193.34.252.0/22 No ROA RIR databaseRIPE 673 100% 67
193.35.8.0/24 No ROA RIR databaseRIPE 673 100% 67
193.35.9.0/24 No ROA RIR databaseRIPE 673 100% 67
193.35.11.0/24 No ROA RIR databaseRIPE 673 100% 67
194.62.10.0/24 No ROA RIR databaseRIPE 673 100% 67
194.62.11.0/24 No ROA RIR databaseRIPE 673 100% 67
194.62.70.0/23 No ROA RIR databaseRIPE 673 100% 67
193.34.251.0/24 No ROA RIR databaseRIPE 671 100% 67
193.35.10.0/24 No ROA RIR databaseRIPE 671 100% 67
193.35.12.0/24 No ROA RIR databaseRIPE 671 100% 67
193.35.13.0/24 No ROA RIR databaseRIPE 671 100% 67
194.62.68.0/24 No ROA RIR databaseRIPE 671 100% 67
194.62.69.0/24 No ROA RIR databaseRIPE 671 100% 67

AS-SET

AS28846's PeeringDB record names no 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 21 are in fix.csv.

  • ROA: none14
  • Route object: none1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none194.36.70.0/24No ROA covers it. Add a ROA for AS28846, maxLength 24.673 of 673
Route object: none194.36.70.0/24No route object for it. A route object for 194.36.70.0/23 with origin AS28846 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28846 in the RIR database for the space.673 of 673
ROA: none193.34.252.0/22No ROA covers it. Add a ROA for AS28846, maxLength 22.673 of 673
ROA: none193.35.8.0/24No ROA covers it. Add a ROA for AS28846, maxLength 24.673 of 673
ROA: none193.35.9.0/24No ROA covers it. Add a ROA for AS28846, maxLength 24.673 of 673
ROA: none193.35.11.0/24No ROA covers it. Add a ROA for AS28846, maxLength 24.673 of 673
ROA: none194.62.10.0/24No ROA covers it. Add a ROA for AS28846, maxLength 24.673 of 673
ROA: none194.62.11.0/24No ROA covers it. Add a ROA for AS28846, maxLength 24.673 of 673
ROA: none194.62.70.0/23No ROA covers it. Add a ROA for AS28846, maxLength 23.673 of 673
ROA: none193.34.251.0/24No ROA covers it. Add a ROA for AS28846, maxLength 24.671 of 673
ROA: none193.35.10.0/24No ROA covers it. Add a ROA for AS28846, maxLength 24.671 of 673
ROA: none193.35.12.0/24No ROA covers it. Add a ROA for AS28846, maxLength 24.671 of 673
ROA: none193.35.13.0/24No ROA covers it. Add a ROA for AS28846, maxLength 24.671 of 673
ROA: none194.62.68.0/24No ROA covers it. Add a ROA for AS28846, maxLength 24.671 of 673
ROA: none194.62.69.0/24No ROA covers it. Add a ROA for AS28846, maxLength 24.671 of 673

Route objects not announced

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

193.34.248.0/22RIPENo ROA
193.35.12.0/23RIPENo ROA
194.36.66.0/24RIPENo ROA
194.36.67.0/24RIPENo ROA
194.36.69.0/24RIPENo ROA
194.36.70.0/23RIPENo 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.