bgpreport

Network · data from 2026-11-12

AS197991 HISPASAT

Registry name: HISPASAT Hispasat S.A, ES · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS197991, 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.
5.144.144.0/22 Valid Nonecovered by 5.144.144.0/21 670 100% 67
5.144.148.0/22 Valid Nonecovered by 5.144.144.0/21 670 100% 67
149.126.32.0/21 Valid Nonecovered by 149.126.32.0/20 670 100% 67
149.126.40.0/21 Valid Nonecovered by 149.126.32.0/20 670 100% 67
45.170.132.0/24 Valid RIR databaseLACNIC 673 100% 67
89.150.60.0/24 Valid RIR databaseRIPE 673 100% 67
178.132.60.0/22 Valid RIR databaseRIPE 673 100% 67
185.239.56.0/24 Valid RIR databaseRIPE 673 100% 67
185.239.57.0/24 Valid RIR databaseRIPE 673 100% 67
185.239.58.0/24 Valid RIR databaseRIPE 673 100% 67
5.144.144.0/21 Valid RIR databaseRIPE 672 100% 67
149.126.32.0/20 Valid RIR databaseRIPE 672 100% 67
200.112.204.0/23 Valid RIR databaseLACNIC 672 100% 67
45.170.133.0/24 Valid RIR databaseLACNIC 670 100% 67
2a0c:4b80::/34 Valid RIR databaseRIPE 634 100% 67
2a0d:a5c0::/36 Valid RIR databaseRIPE 634 100% 67

AS-SET

AS197991'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 9 are in fix.csv.

  • Route object: none4
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none5.144.144.0/22No route object for it. A route object for 5.144.144.0/21 with origin AS197991 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197991 in the RIR database for the space.670 of 673
Route object: none5.144.148.0/22No route object for it. A route object for 5.144.144.0/21 with origin AS197991 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197991 in the RIR database for the space.670 of 673
Route object: none149.126.32.0/21No route object for it. A route object for 149.126.32.0/20 with origin AS197991 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197991 in the RIR database for the space.670 of 673
Route object: none149.126.40.0/21No route object for it. A route object for 149.126.32.0/20 with origin AS197991 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197991 in the RIR database for the space.670 of 673

Route objects not announced

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

178.132.56.0/21RIPENo ROA
178.132.59.0/24RIPEValid
185.239.56.0/22RIPEValid
185.239.59.0/24RIPEValid
2a0d:a5c0:1000::/36RIPEValid

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.