bgpreport

Network · data from 2026-11-12

AS39550 KPMG-UK-LLP-AS KPMG LLP

Registry name: KPMG-UK-LLP-AS KPMG LLP, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS39550, 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.
158.180.128.0/19 No ROA RIR databaseRIPE 673 100% 67
158.179.64.0/19 No ROA RIR databaseRIPE 667 99% 67
158.179.96.0/19 No ROA RIR databaseRIPE 667 99% 67
158.180.192.0/19 No ROA RIR databaseRIPE 667 99% 67

AS-SET

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

  • ROA: none4
ChangePrefix or setDetailFull-table peers
ROA: none158.180.128.0/19No ROA covers it. Add a ROA for AS39550, maxLength 19.673 of 673
ROA: none158.179.64.0/19No ROA covers it. Add a ROA for AS39550, maxLength 19.667 of 673
ROA: none158.179.96.0/19No ROA covers it. Add a ROA for AS39550, maxLength 19.667 of 673
ROA: none158.180.192.0/19No ROA covers it. Add a ROA for AS39550, maxLength 19.667 of 673

Route objects not announced

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