bgpreport

Network · data from 2026-11-12

AS198432 IPCORE-AS Ipcore Datacenters S.L

Registry name: IPCORE-AS Ipcore Datacenters S.L, ES · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS198432, 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.2.88.0/24 No ROA Nonecovered by 5.2.88.0/21 669 99% 66
5.2.89.0/24 No ROA RIR databaseRIPE 669 99% 66
5.2.90.0/24 No ROA RIR databaseRIPE 669 99% 66
5.2.91.0/24 No ROA RIR databaseRIPE 669 99% 66
5.2.95.0/24 No ROA RIR databaseRIPE 669 99% 66
185.75.179.0/24 No ROA RIR databaseRIPE 669 99% 66
2a00:e9c0::/32 Valid None 631 99% 67
185.164.184.0/24 Valid RIR databaseRIPE 669 99% 66

AS-SET

AS198432 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 14 are in fix.csv.

  • ROA: none6
  • Route object: none2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none5.2.88.0/24No ROA covers it. Add a ROA for AS198432, maxLength 24.669 of 673
Route object: none5.2.88.0/24No route object for it. A route object for 5.2.88.0/21 with origin AS198432 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198432 in the RIR database for the space.669 of 673
ROA: none5.2.89.0/24No ROA covers it. Add a ROA for AS198432, maxLength 24.669 of 673
ROA: none5.2.90.0/24No ROA covers it. Add a ROA for AS198432, maxLength 24.669 of 673
ROA: none5.2.91.0/24No ROA covers it. Add a ROA for AS198432, maxLength 24.669 of 673
ROA: none5.2.95.0/24No ROA covers it. Add a ROA for AS198432, maxLength 24.669 of 673
ROA: none185.75.179.0/24No ROA covers it. Add a ROA for AS198432, maxLength 24.669 of 673
Route object: none2a00:e9c0::/32No route object for it. Add a route object with origin AS198432 in the RIR database for the space.631 of 636

Route objects not announced

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

5.2.88.0/21RIPENo ROA
5.2.92.0/24RIPENo ROA
5.2.93.0/24RIPENo ROA
5.2.94.0/24RIPENo ROA
185.18.198.0/24RIPEValid
185.18.199.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.