bgpreport

Network · data from 2026-11-12

AS64111 AS64111 - INFORMATICA BLUEHOSTING LIMITADA

Registry name: AS64111 - INFORMATICA BLUEHOSTING LIMITADA, CL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS64111, 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.
2c0f:fd58::10/128 Invalid: origin None 2 0%low visibility 1
2c0f:fd58::11/128 Invalid: origin None 2 0%low visibility 1
45.236.128.0/22 No ROA Other IRR onlyRADB 673 100% 66
45.236.128.0/23 No ROA Other IRR onlyRADB 109 16% 41
45.236.130.0/23 No ROA Other IRR onlyRADB 109 16% 41

AS-SET

AS64111 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: origin2
  • ROA: none3
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin2c0f:fd58::10/128ROAs covering it name AS11845, not AS64111. If AS64111 should announce it, add a ROA for AS64111.2 of 636
Route object: none2c0f:fd58::10/128No route object for it. Add a route object with origin AS64111 in the RIR database for the space.2 of 636
ROA: origin2c0f:fd58::11/128ROAs covering it name AS11845, not AS64111. If AS64111 should announce it, add a ROA for AS64111.2 of 636
Route object: none2c0f:fd58::11/128No route object for it. Add a route object with origin AS64111 in the RIR database for the space.2 of 636
ROA: none45.236.128.0/22No ROA covers it. Add a ROA for AS64111, maxLength 22.673 of 673
Route object: RIR45.236.128.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none45.236.128.0/23No ROA covers it. Add a ROA for AS64111, maxLength 23.109 of 673
Route object: RIR45.236.128.0/23Route object only in RADB. Add it in the RIR database for the space.109 of 673
ROA: none45.236.130.0/23No ROA covers it. Add a ROA for AS64111, maxLength 23.109 of 673
Route object: RIR45.236.130.0/23Route object only in RADB. Add it in the RIR database for the space.109 of 673

Route objects not announced

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

45.236.128.0/24RADBNo ROA
45.236.129.0/24RADBNo ROA
45.236.130.0/24RADBNo ROA
45.236.131.0/24RADBNo ROA
2803:64a0::/32RADBNo 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.