bgpreport

Network · data from 2026-11-12

AS43599 North West Electronics

Registry name: NWEWN-AS Broadband N.I. Ltd., GB · PeeringDB

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

Announced routes

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

78.155.248.0/24 No ROA Nonecovered by 78.155.224.0/19 673 100% 67
78.155.249.0/24 No ROA Nonecovered by 78.155.224.0/19 673 100% 67
78.155.253.0/24 No ROA Nonecovered by 78.155.224.0/19 673 100% 67
78.155.254.0/24 No ROA Nonecovered by 78.155.224.0/19 673 100% 67
5.172.48.0/20 No ROA RIR databaseRIPE 670 100% 67
37.153.72.0/21 No ROA RIR databaseRIPE 670 100% 67
78.155.224.0/19 No ROA RIR databaseRIPE 670 100% 67

AS-SET

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

  • ROA: none7
  • Route object: none4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none78.155.248.0/24No ROA covers it. Add a ROA for AS43599, maxLength 24.673 of 673
Route object: none78.155.248.0/24No route object for it. A route object for 78.155.224.0/19 with origin AS43599 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43599 in the RIR database for the space.673 of 673
ROA: none78.155.249.0/24No ROA covers it. Add a ROA for AS43599, maxLength 24.673 of 673
Route object: none78.155.249.0/24No route object for it. A route object for 78.155.224.0/19 with origin AS43599 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43599 in the RIR database for the space.673 of 673
ROA: none78.155.253.0/24No ROA covers it. Add a ROA for AS43599, maxLength 24.673 of 673
Route object: none78.155.253.0/24No route object for it. A route object for 78.155.224.0/19 with origin AS43599 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43599 in the RIR database for the space.673 of 673
ROA: none78.155.254.0/24No ROA covers it. Add a ROA for AS43599, maxLength 24.673 of 673
Route object: none78.155.254.0/24No route object for it. A route object for 78.155.224.0/19 with origin AS43599 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43599 in the RIR database for the space.673 of 673
ROA: none5.172.48.0/20No ROA covers it. Add a ROA for AS43599, maxLength 20.670 of 673
ROA: none37.153.72.0/21No ROA covers it. Add a ROA for AS43599, maxLength 21.670 of 673
ROA: none78.155.224.0/19No ROA covers it. Add a ROA for AS43599, maxLength 19.670 of 673

Route objects not announced

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

2a02:1340::/32RIPENo 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.