bgpreport

Network · data from 2026-11-12

AS47784 INSTINF Entidade de Servicos Partilhados da Administracao Publica, I.P.

Registry name: INSTINF Entidade de Servicos Partilhados da Administracao Publica, I.P., PT · not in PeeringDB

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

Announced routes

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

185.32.36.0/23 No ROA Nonecovered by 185.32.36.0/22 668 99% 68
2a04:53c0:80::/48 No ROA Nonecovered by 2a04:53c0::/29 634 100% 68
2a04:53c0:82::/48 No ROA Nonecovered by 2a04:53c0::/29 634 100% 68
2a04:53c0:83::/48 No ROA Nonecovered by 2a04:53c0::/29 634 100% 68
2a04:53c0:85::/48 No ROA Nonecovered by 2a04:53c0::/29 634 100% 68
192.112.45.0/24 No ROA RIR databaseRIPE 668 99% 68
194.110.76.0/24 No ROA RIR databaseRIPE 668 99% 68

AS-SET

AS47784 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 15 are in fix.csv.

  • ROA: none7
  • Route object: none5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none185.32.36.0/23No ROA covers it. Add a ROA for AS47784, maxLength 23.668 of 673
Route object: none185.32.36.0/23No route object for it. A route object for 185.32.36.0/22 with origin AS47784 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47784 in the RIR database for the space.668 of 673
ROA: none2a04:53c0:80::/48No ROA covers it. Add a ROA for AS47784, maxLength 48.634 of 636
Route object: none2a04:53c0:80::/48No route object for it. A route object for 2a04:53c0::/29 with origin AS47784 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47784 in the RIR database for the space.634 of 636
ROA: none2a04:53c0:82::/48No ROA covers it. Add a ROA for AS47784, maxLength 48.634 of 636
Route object: none2a04:53c0:82::/48No route object for it. A route object for 2a04:53c0::/29 with origin AS47784 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47784 in the RIR database for the space.634 of 636
ROA: none2a04:53c0:83::/48No ROA covers it. Add a ROA for AS47784, maxLength 48.634 of 636
Route object: none2a04:53c0:83::/48No route object for it. A route object for 2a04:53c0::/29 with origin AS47784 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47784 in the RIR database for the space.634 of 636
ROA: none2a04:53c0:85::/48No ROA covers it. Add a ROA for AS47784, maxLength 48.634 of 636
Route object: none2a04:53c0:85::/48No route object for it. A route object for 2a04:53c0::/29 with origin AS47784 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47784 in the RIR database for the space.634 of 636
ROA: none192.112.45.0/24No ROA covers it. Add a ROA for AS47784, maxLength 24.668 of 673
ROA: none194.110.76.0/24No ROA covers it. Add a ROA for AS47784, maxLength 24.668 of 673

Route objects not announced

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

185.32.36.0/22RIPENo ROA
2a04:53c0::/29RIPENo ROA
2a04:53c0::/44RIPENo ROA

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.