bgpreport

Network · data from 2026-11-12

AS60976 POL Parsan Lin Co. PJS

Registry name: POL Parsan Lin Co. PJS, IR · not in PeeringDB

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

Announced routes

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

31.214.248.0/24 Valid RIR databaseRIPE 671 100% 67
31.214.249.0/24 Valid RIR databaseRIPE 671 100% 67
31.214.250.0/24 Valid RIR databaseRIPE 671 100% 67
31.214.251.0/24 Valid RIR databaseRIPE 671 100% 67
31.214.255.0/24 Valid RIR databaseRIPE 671 100% 67
95.156.236.0/24 Valid RIR databaseRIPE 671 100% 67
95.156.237.0/24 Valid RIR databaseRIPE 671 100% 67
95.156.252.0/24 Valid RIR databaseRIPE 671 100% 67
95.156.253.0/24 Valid RIR databaseRIPE 671 100% 67
95.156.254.0/24 Valid RIR databaseRIPE 671 100% 67
95.156.255.0/24 Valid RIR databaseRIPE 671 100% 67
109.230.200.0/24 Valid RIR databaseRIPE 671 100% 67
109.230.205.0/24 Valid RIR databaseRIPE 671 100% 67
109.230.207.0/24 Valid RIR databaseRIPE 671 100% 67
109.230.221.0/24 Valid RIR databaseRIPE 671 100% 67
109.230.223.0/24 Valid RIR databaseRIPE 671 100% 67
109.230.242.0/24 Valid RIR databaseRIPE 671 100% 67
185.10.71.0/24 Valid RIR databaseRIPE 671 100% 67
185.13.228.0/24 Valid RIR databaseRIPE 671 100% 67
185.13.229.0/24 Valid RIR databaseRIPE 671 100% 67
185.13.230.0/24 Valid RIR databaseRIPE 671 100% 67
185.13.231.0/24 Valid RIR databaseRIPE 671 100% 67
37.10.66.0/24 Valid RIR databaseRIPE 670 100% 67
37.10.67.0/24 Valid RIR databaseRIPE 670 100% 67
37.10.109.0/24 Valid RIR databaseRIPE 670 100% 67
37.228.136.0/24 Valid RIR databaseRIPE 670 100% 67
37.228.137.0/24 Valid RIR databaseRIPE 670 100% 67
37.228.138.0/24 Valid RIR databaseRIPE 670 100% 67
37.228.139.0/24 Valid RIR databaseRIPE 670 100% 67
31.214.168.0/21 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS60976 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 43 are in fix.csv.

  • Route object: not announced43

Route objects not announced

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

31.214.168.0/24RIPEValid
31.214.169.0/24RIPEValid
31.214.170.0/24RIPEValid
31.214.171.0/24RIPEValid
31.214.172.0/24RIPEValid
31.214.173.0/24RIPEValid
31.214.174.0/24RIPEValid
31.214.175.0/24RIPEValid
31.214.248.0/21RIPEValid
31.214.252.0/24RIPEValid
31.214.253.0/24RIPEValid
31.214.254.0/24RIPEValid
37.10.64.0/24RIPEValid
37.10.65.0/24RIPEValid
37.228.136.0/22RIPEValid
81.12.25.0/24RIPEValid
82.99.215.0/24RIPEValid
82.99.216.0/24RIPEValid
82.99.217.0/24RIPEValid
82.99.218.0/24RIPEValid
82.99.219.0/24RIPEValid
82.99.238.0/24RIPEValid
82.99.242.0/24RIPEValid
82.99.243.0/24RIPEValid
82.99.244.0/24RIPEValid
91.232.73.0/24RIPEInvalid: origin
95.156.252.0/22RIPEValid
109.230.204.0/22RIPEValid
109.230.204.0/24RIPEValid
109.230.206.0/24RIPEValid
109.230.251.0/24RIPEValid
134.255.200.0/21RIPEValid
134.255.200.0/24RIPEValid
134.255.201.0/24RIPEValid
134.255.202.0/24RIPEValid
134.255.203.0/24RIPEValid
134.255.204.0/24RIPEValid
134.255.205.0/24RIPEValid
134.255.206.0/24RIPEValid
134.255.207.0/24RIPEValid
185.13.228.0/22RIPEValid
185.222.122.0/24RIPEValid
185.222.123.0/24RIPEValid

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.