bgpreport

Network · data from 2026-11-12

AS62313 PANEM

Registry name: PROACT-AS Proact IT UK Limited, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS62313, 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.
149.5.94.0/24 No ROA None 673 100% 67
185.39.244.0/24 No ROA RIR databaseRADB, RIPE 673 100% 66
185.39.246.0/24 No ROA RIR databaseRADB, RIPE 673 100% 66
185.39.247.0/24 No ROA RIR databaseRADB, RIPE 673 100% 66
192.165.7.0/24 No ROA RIR databaseRIPE 673 100% 67
213.32.225.0/24 No ROA RIR databaseRADB, RIPE 673 100% 66
213.32.226.0/24 No ROA RIR databaseRADB, RIPE 673 100% 66
213.32.229.0/24 No ROA RIR databaseRADB, RIPE 673 100% 66
91.209.240.0/24 Valid RIR databaseRIPE 673 100% 66
91.233.35.0/24 Valid RIR databaseRIPE 673 100% 66
185.63.128.0/22 Valid RIR databaseRIPE 673 100% 66
185.141.200.0/22 Valid RIR databaseRIPE 673 100% 66
185.168.0.0/22 Valid RIR databaseRADB, RIPE 673 100% 66
193.22.141.0/24 Valid RIR databaseRIPE 673 100% 67
193.188.248.0/24 Valid RIR databaseRIPE 673 100% 67
194.150.190.0/23 Valid RIR databaseRIPE 673 100% 66
212.46.51.0/24 Valid RIR databaseRIPE 673 100% 67
213.32.224.0/24 Valid RIR databaseRIPE 673 100% 67
213.32.228.0/24 Valid RIR databaseRIPE 673 100% 66
213.32.230.0/24 Valid RIR databaseRIPE 673 100% 67
213.32.231.0/24 Valid RIR databaseRIPE 673 100% 66
194.9.4.0/23 Valid RIR databaseRIPE 671 100% 66
2a07:3640::/29 Valid RIR databaseRIPE 571 90% 68
185.143.156.0/22 Valid RIR databaseRIPE 446 66% 67

AS-SET

AS62313'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 23 are in fix.csv.

  • ROA: none8
  • Route object: none1
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none149.5.94.0/24No ROA covers it. Add a ROA for AS62313, maxLength 24.673 of 673
Route object: none149.5.94.0/24No route object for it. Add a route object with origin AS62313 in the RIR database for the space.673 of 673
ROA: none185.39.244.0/24No ROA covers it. Add a ROA for AS62313, maxLength 24.673 of 673
ROA: none185.39.246.0/24No ROA covers it. Add a ROA for AS62313, maxLength 24.673 of 673
ROA: none185.39.247.0/24No ROA covers it. Add a ROA for AS62313, maxLength 24.673 of 673
ROA: none192.165.7.0/24No ROA covers it. Add a ROA for AS62313, maxLength 24.673 of 673
ROA: none213.32.225.0/24No ROA covers it. Add a ROA for AS62313, maxLength 24.673 of 673
ROA: none213.32.226.0/24No ROA covers it. Add a ROA for AS62313, maxLength 24.673 of 673
ROA: none213.32.229.0/24No ROA covers it. Add a ROA for AS62313, maxLength 24.673 of 673

Route objects not announced

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

69.25.188.0/24RADBNo ROA
185.39.244.0/22RADB, RIPENo ROA
185.39.244.0/23RIPENo ROA
185.39.245.0/24RADB, RIPENo ROA
185.39.246.0/23RIPENo ROA
185.188.204.0/22RIPEValid
213.32.224.0/21RIPENo ROA
213.32.224.0/22RIPENo ROA
213.32.224.0/23RIPENo ROA
213.32.226.0/23RIPENo ROA
213.32.227.0/24RIPENo ROA
213.32.228.0/22RIPENo ROA
213.32.228.0/23RIPENo ROA
213.32.230.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.