bgpreport

Network · data from 2026-11-12

AS273451 BRANDAONET SERVICOS E TELECOMUNICACOES LDTA

Registry name: AS273451 - BRANDAONET SERVICOS DE TELECOMUNICACOES LDTA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273451, 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.
2804:8ed8::/33 No ROA Nonecovered by 2804:8ed8::/32 336 53% 65
2804:8ed8:8000::/33 No ROA Nonecovered by 2804:8ed8::/32 336 53% 65
191.253.56.0/22 No ROA Other IRR onlyTC 669 99% 67
2804:8ed8::/32 No ROA Other IRR onlyTC 633 100% 67
191.253.56.0/23 No ROA Other IRR onlyTC 136 20% 45
191.253.58.0/23 No ROA Other IRR onlyTC 136 20% 45

AS-SET

AS273451's PeeringDB record names no 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: none6
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2804:8ed8::/33No ROA covers it. Add a ROA for AS273451, maxLength 33.336 of 636
Route object: none2804:8ed8::/33No route object for it. A route object for 2804:8ed8::/32 with origin AS273451 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273451 in the RIR database for the space.336 of 636
ROA: none2804:8ed8:8000::/33No ROA covers it. Add a ROA for AS273451, maxLength 33.336 of 636
Route object: none2804:8ed8:8000::/33No route object for it. A route object for 2804:8ed8::/32 with origin AS273451 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273451 in the RIR database for the space.336 of 636
ROA: none191.253.56.0/22No ROA covers it. Add a ROA for AS273451, maxLength 22.669 of 673
Route object: RIR191.253.56.0/22Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:8ed8::/32No ROA covers it. Add a ROA for AS273451, maxLength 32.633 of 636
Route object: RIR2804:8ed8::/32Route object only in TC. Add it in the RIR database for the space.633 of 636
ROA: none191.253.56.0/23No ROA covers it. Add a ROA for AS273451, maxLength 23.136 of 673
Route object: RIR191.253.56.0/23Route object only in TC. Add it in the RIR database for the space.136 of 673
ROA: none191.253.58.0/23No ROA covers it. Add a ROA for AS273451, maxLength 23.136 of 673
Route object: RIR191.253.58.0/23Route object only in TC. Add it in the RIR database for the space.136 of 673

Route objects not announced

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

191.253.56.0/24TCNo ROA
191.253.57.0/24TCNo ROA
191.253.58.0/24TCNo ROA
191.253.59.0/24TCNo 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.