bgpreport

Network · data from 2026-11-12

AS28924 INTEGRITY Informatics

Registry name: INTEGRITY-HU-AS INTEGRITY Informatics Ltd., HU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28924, 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.
91.220.29.0/24 No ROA RIR databaseRIPE 673 100% 66
2a01:7d80:2000::/36 No ROA RIR databaseRIPE 635 100% 67
193.178.119.0/24 Valid RIR databaseRIPE 673 100% 66
195.90.114.0/24 Valid RIR databaseRIPE 673 100% 66
212.52.160.0/19 Valid RIR databaseRIPE 673 100% 66
212.52.164.0/24 Valid RIR databaseRIPE 673 100% 66
212.52.165.0/24 Valid RIR databaseRIPE 673 100% 66
212.52.166.0/24 Valid RIR databaseRIPE 673 100% 66
212.52.167.0/24 Valid RIR databaseRIPE 673 100% 66
212.52.180.0/24 Valid RIR databaseRIPE 673 100% 66
212.52.182.0/24 Valid RIR databaseRIPE 673 100% 66
212.52.184.0/24 Valid RIR databaseRIPE 673 100% 66
213.181.220.0/24 Valid RIR databaseRIPE 673 100% 66
2a01:7d80::/36 Valid RIR databaseRIPE 635 100% 67
2a01:7d80:251::/48 Valid RIR databaseRIPE 635 100% 67
2a01:7d80:252::/48 Valid RIR databaseRIPE 635 100% 67
2a01:7d80:1000::/36 Valid RIR databaseRIPE 635 100% 67
2a01:7d80:3000::/36 Valid RIR databaseRIPE 635 100% 67
2a01:7d80:4000::/36 Valid RIR databaseRIPE 635 100% 67
2a01:7d80:5000::/36 Valid RIR databaseRIPE 635 100% 67
2a01:7d80:6000::/36 Valid RIR databaseRIPE 635 100% 67
2a01:7d80:7000::/36 Valid RIR databaseRIPE 635 100% 67
2a01:7d80:8000::/36 Valid RIR databaseRIPE 635 100% 67
2a01:7d80:9000::/36 Valid RIR databaseRIPE 635 100% 67
212.52.186.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
212.52.191.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS28924'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 38 are in fix.csv.

  • ROA: none2
  • Route object: not announced36
ChangePrefix or setDetailFull-table peers
ROA: none91.220.29.0/24No ROA covers it. Add a ROA for AS28924, maxLength 24.673 of 673
ROA: none2a01:7d80:2000::/36No ROA covers it. Add a ROA for AS28924, maxLength 36.635 of 636

Route objects not announced

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

195.56.44.0/24RIPEValid
195.56.147.0/24RIPEValid
195.56.148.0/23RIPEInvalid: origin
195.90.98.0/23RIPENo ROA
195.90.99.0/24RIPEValid
195.90.114.0/23RIPEValid
195.90.115.0/24RIPEInvalid: maxLength
212.52.160.0/22RIPEValid
212.52.160.0/24RIPEValid
212.52.161.0/24RIPEValid
212.52.162.0/24RIPEValid
212.52.163.0/24RIPEValid
212.52.168.0/22RIPEValid
212.52.168.0/24RIPEValid
212.52.169.0/24RIPEValid
212.52.170.0/24RIPEValid
212.52.171.0/24RIPEValid
212.52.172.0/24RIPEValid
212.52.173.0/24RIPEValid
212.52.174.0/24RIPEValid
212.52.175.0/24RIPEValid
212.52.176.0/24RIPEValid
212.52.177.0/24RIPEValid
212.52.178.0/24RIPEValid
212.52.179.0/24RIPEValid
212.52.181.0/24RIPEValid
212.52.183.0/24RIPEValid
212.52.185.0/24RIPEValid
212.52.187.0/24RIPEValid
212.52.188.0/24RIPEValid
212.52.189.0/24RIPEValid
212.52.190.0/23RIPEValid
212.52.190.0/24RIPEValid
2a01:7d80::/38RIPEInvalid: maxLength
2a01:7d80:999::/48RIPEValid
2a01:7d80:1000::/38RIPEValid

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.