bgpreport

Network · data from 2026-11-12

AS210712 GRAPESC-ISP ISP Alliance a.s.

Registry name: GRAPESC-ISP ISP Alliance a.s., CZ · not in PeeringDB

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

Announced routes

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

109.235.0.0/21 Valid RIR databaseRIPE 671 100% 67
185.40.80.0/22 Valid RIR databaseRIPE 671 100% 67
91.192.32.0/22 Valid RIR databaseRIPE 669 99% 67
93.91.144.0/20 Valid RIR databaseRIPE 669 99% 67
185.94.4.0/22 Valid RIR databaseRIPE 669 99% 67
213.109.172.0/22 Valid RIR databaseRIPE 669 99% 67
217.75.208.0/20 Valid RIR databaseRIPE 669 99% 67
2a02:17a0::/30 Valid RIR databaseRIPE 634 100% 69

AS-SET

AS210712 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 50 are in fix.csv.

  • Route object: not announced50

Route objects not announced

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

5.39.200.0/22RIPEValid
46.29.224.0/21RIPEValid
46.29.228.0/24RIPEValid
46.29.229.0/24RIPEValid
46.29.230.0/24RIPEValid
46.29.231.0/24RIPEValid
78.111.112.0/20RIPEValid
78.111.112.0/24RIPEValid
78.111.113.0/24RIPEValid
78.111.114.0/24RIPEValid
78.111.115.0/24RIPEValid
78.111.116.0/24RIPEValid
78.111.117.0/24RIPEValid
91.192.32.0/24RIPEValid
91.192.33.0/24RIPEValid
91.192.34.0/24RIPEValid
91.192.35.0/24RIPEValid
93.91.144.0/24RIPEValid
93.91.145.0/24RIPEValid
93.91.146.0/24RIPEValid
93.91.147.0/24RIPEValid
93.91.148.0/24RIPEValid
93.91.149.0/24RIPEValid
93.91.150.0/24RIPEValid
93.91.151.0/24RIPEValid
93.91.152.0/24RIPEValid
93.91.153.0/24RIPEValid
93.91.154.0/24RIPEValid
93.91.155.0/24RIPEValid
185.15.108.0/22RIPEValid
185.94.4.0/24RIPEValid
185.94.5.0/24RIPEValid
185.94.6.0/24RIPEValid
185.94.7.0/24RIPEValid
213.109.172.0/24RIPEValid
213.109.173.0/24RIPEValid
213.109.174.0/24RIPEValid
213.109.175.0/24RIPEValid
217.75.208.0/24RIPEValid
217.75.209.0/24RIPEValid
217.75.211.0/24RIPEValid
217.75.212.0/24RIPEValid
217.75.213.0/24RIPEValid
217.75.214.0/24RIPEValid
217.75.215.0/24RIPEValid
217.75.216.0/24RIPEValid
217.75.219.0/24RIPEValid
217.75.220.0/24RIPEValid
217.75.221.0/24RIPEValid
2a09:fc00::/29RIPEInvalid: origin

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.