bgpreport

Network · data from 2026-11-12

AS18547 AS18547 - PICTURE INFORMATICA EIRELI

Registry name: AS18547 - PICTURE INFORMATICA EIRELI, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18547, 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.
200.229.128.0/21 No ROA None 671 100% 67
200.229.132.0/22 No ROA None 671 100% 67
200.229.128.0/22 No ROA None 670 100% 67
2804:ac::/34 No ROA None 636 100% 67
2804:ac:4000::/34 No ROA None 636 100% 67
2804:ac:8000::/34 No ROA None 636 100% 67
2804:ac:c000::/34 No ROA None 636 100% 67
2804:ac::/32 No ROA None 635 100% 67

AS-SET

AS18547 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 16 are in fix.csv.

  • ROA: none8
  • Route object: none8
ChangePrefix or setDetailFull-table peers
ROA: none200.229.128.0/21No ROA covers it. Add a ROA for AS18547, maxLength 21.671 of 673
Route object: none200.229.128.0/21No route object for it. Add a route object with origin AS18547 in the RIR database for the space.671 of 673
ROA: none200.229.132.0/22No ROA covers it. Add a ROA for AS18547, maxLength 22.671 of 673
Route object: none200.229.132.0/22No route object for it. Add a route object with origin AS18547 in the RIR database for the space.671 of 673
ROA: none200.229.128.0/22No ROA covers it. Add a ROA for AS18547, maxLength 22.670 of 673
Route object: none200.229.128.0/22No route object for it. Add a route object with origin AS18547 in the RIR database for the space.670 of 673
ROA: none2804:ac::/34No ROA covers it. Add a ROA for AS18547, maxLength 34.636 of 636
Route object: none2804:ac::/34No route object for it. Add a route object with origin AS18547 in the RIR database for the space.636 of 636
ROA: none2804:ac:4000::/34No ROA covers it. Add a ROA for AS18547, maxLength 34.636 of 636
Route object: none2804:ac:4000::/34No route object for it. Add a route object with origin AS18547 in the RIR database for the space.636 of 636
ROA: none2804:ac:8000::/34No ROA covers it. Add a ROA for AS18547, maxLength 34.636 of 636
Route object: none2804:ac:8000::/34No route object for it. Add a route object with origin AS18547 in the RIR database for the space.636 of 636
ROA: none2804:ac:c000::/34No ROA covers it. Add a ROA for AS18547, maxLength 34.636 of 636
Route object: none2804:ac:c000::/34No route object for it. Add a route object with origin AS18547 in the RIR database for the space.636 of 636
ROA: none2804:ac::/32No ROA covers it. Add a ROA for AS18547, maxLength 32.635 of 636
Route object: none2804:ac::/32No route object for it. Add a route object with origin AS18547 in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS18547 is announced.

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.