bgpreport

Network · data from 2026-11-12

AS265153 AS265153 - HARDONLINE LTDA - EPP

Registry name: AS265153 - HARDONLINE LTDA - EPP, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265153, 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.
170.254.44.0/22 No ROA Other IRR onlyRADB, TC 670 100% 66
143.255.172.0/22 No ROA Other IRR onlyRADB, TC 669 99% 66
143.255.172.0/23 No ROA Other IRR onlyRADB 127 19% 44
170.254.46.0/23 No ROA Other IRR onlyRADB 127 19% 44
143.255.174.0/23 No ROA Other IRR onlyRADB 126 19% 44
170.254.44.0/23 No ROA Other IRR onlyRADB 126 19% 44

AS-SET

AS265153 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 13 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none170.254.44.0/22No ROA covers it. Add a ROA for AS265153, maxLength 22.670 of 673
Route object: RIR170.254.44.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
ROA: none143.255.172.0/22No ROA covers it. Add a ROA for AS265153, maxLength 22.669 of 673
Route object: RIR143.255.172.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none143.255.172.0/23No ROA covers it. Add a ROA for AS265153, maxLength 23.127 of 673
Route object: RIR143.255.172.0/23Route object only in RADB. Add it in the RIR database for the space.127 of 673
ROA: none170.254.46.0/23No ROA covers it. Add a ROA for AS265153, maxLength 23.127 of 673
Route object: RIR170.254.46.0/23Route object only in RADB. Add it in the RIR database for the space.127 of 673
ROA: none143.255.174.0/23No ROA covers it. Add a ROA for AS265153, maxLength 23.126 of 673
Route object: RIR143.255.174.0/23Route object only in RADB. Add it in the RIR database for the space.126 of 673
ROA: none170.254.44.0/23No ROA covers it. Add a ROA for AS265153, maxLength 23.126 of 673
Route object: RIR170.254.44.0/23Route object only in RADB. Add it in the RIR database for the space.126 of 673

Route objects not announced

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

2804:2b70::/32RADB, TCNo 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.