bgpreport

Network · data from 2026-11-12

AS262457 Hello Brazil Telecomunicacoes

Registry name: AS262457 - HELLO BRAZIL REPRESENTACAO DE COMERCIO DE EQUIPAM, BR · PeeringDB

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

Announced routes

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

177.53.33.0/24 No ROA Nonecovered by 177.53.32.0/22 203 30% 54
177.53.34.0/24 No ROA Nonecovered by 177.53.32.0/22 203 30% 54
177.53.35.0/24 No ROA Nonecovered by 177.53.32.0/22 203 30% 54
177.53.36.0/24 No ROA Nonecovered by 177.53.36.0/22 203 30% 54
177.53.37.0/24 No ROA Nonecovered by 177.53.36.0/22 203 30% 54
177.53.38.0/24 No ROA Nonecovered by 177.53.36.0/22 202 30% 54
177.53.39.0/24 No ROA Nonecovered by 177.53.36.0/22 202 30% 54
177.53.32.0/21 No ROA Other IRR onlyRADB, TC 671 100% 67
177.53.32.0/22 No ROA Other IRR onlyRADB 671 100% 67
177.53.36.0/22 No ROA Other IRR onlyRADB 671 100% 67
2804:4a8::/32 No ROA Other IRR onlyRADB, TC 355 56% 65
177.53.32.0/24 No ROA Other IRR onlyRADB 203 30% 54

AS-SET

PeeringDB's irr_as_set for AS262457: AS262457. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS262457 isn't in the set, or no route object for AS262457 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS262457 in itNot covered
AS262457 A single AS number, not a set: AS262457 (this network), 5 route objects.

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

  • ROA: none12
  • Route object: none7
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none177.53.33.0/24No ROA covers it. Add a ROA for AS262457, maxLength 24.203 of 673
Route object: none177.53.33.0/24No route object for it. A route object for 177.53.32.0/22 with origin AS262457 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262457 in the RIR database for the space.203 of 673
ROA: none177.53.34.0/24No ROA covers it. Add a ROA for AS262457, maxLength 24.203 of 673
Route object: none177.53.34.0/24No route object for it. A route object for 177.53.32.0/22 with origin AS262457 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262457 in the RIR database for the space.203 of 673
ROA: none177.53.35.0/24No ROA covers it. Add a ROA for AS262457, maxLength 24.203 of 673
Route object: none177.53.35.0/24No route object for it. A route object for 177.53.32.0/22 with origin AS262457 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262457 in the RIR database for the space.203 of 673
ROA: none177.53.36.0/24No ROA covers it. Add a ROA for AS262457, maxLength 24.203 of 673
Route object: none177.53.36.0/24No route object for it. A route object for 177.53.36.0/22 with origin AS262457 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262457 in the RIR database for the space.203 of 673
ROA: none177.53.37.0/24No ROA covers it. Add a ROA for AS262457, maxLength 24.203 of 673
Route object: none177.53.37.0/24No route object for it. A route object for 177.53.36.0/22 with origin AS262457 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262457 in the RIR database for the space.203 of 673
ROA: none177.53.38.0/24No ROA covers it. Add a ROA for AS262457, maxLength 24.202 of 673
Route object: none177.53.38.0/24No route object for it. A route object for 177.53.36.0/22 with origin AS262457 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262457 in the RIR database for the space.202 of 673
ROA: none177.53.39.0/24No ROA covers it. Add a ROA for AS262457, maxLength 24.202 of 673
Route object: none177.53.39.0/24No route object for it. A route object for 177.53.36.0/22 with origin AS262457 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262457 in the RIR database for the space.202 of 673
ROA: none177.53.32.0/21No ROA covers it. Add a ROA for AS262457, maxLength 21.671 of 673
Route object: RIR177.53.32.0/21Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none177.53.32.0/22No ROA covers it. Add a ROA for AS262457, maxLength 22.671 of 673
Route object: RIR177.53.32.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none177.53.36.0/22No ROA covers it. Add a ROA for AS262457, maxLength 22.671 of 673
Route object: RIR177.53.36.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:4a8::/32No ROA covers it. Add a ROA for AS262457, maxLength 32.355 of 636
Route object: RIR2804:4a8::/32Route object only in RADB, TC. Add it in the RIR database for the space.355 of 636
ROA: none177.53.32.0/24No ROA covers it. Add a ROA for AS262457, maxLength 24.203 of 673
Route object: RIR177.53.32.0/24Route object only in RADB. Add it in the RIR database for the space.203 of 673

Route objects not announced

Every route object with origin AS262457 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.