bgpreport

Network · data from 2026-11-12

AS262962 AS262962 - BRASIL NET EMPREENDIMENTOS LTDA - ME

Registry name: AS262962 - BRASIL NET EMPREENDIMENTOS LTDA - ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262962, 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.
131.255.246.0/24 Invalid: maxLength Nonecovered by 131.255.244.0/22 29 4%low visibility 11
131.255.247.0/24 Invalid: maxLength Nonecovered by 131.255.244.0/22 29 4%low visibility 11
131.255.244.0/22 Valid Other IRR onlyALTDB, RADB 671 100% 67
187.85.56.0/22 Valid Other IRR onlyALTDB, RADB 671 100% 67
187.85.56.0/24 Valid Other IRR onlyRADB 671 100% 67
187.85.57.0/24 Valid Other IRR onlyRADB 671 100% 67
187.85.58.0/24 Valid Other IRR onlyRADB 671 100% 67
187.85.59.0/24 Valid Other IRR onlyRADB 671 100% 67
131.255.244.0/24 Valid Other IRR onlyRADB 669 99% 67
131.255.245.0/24 Valid Other IRR onlyRADB 666 99% 67

AS-SET

AS262962 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: maxLength2
  • Route object: none2
  • Route object: RIR8
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: maxLength131.255.246.0/24ROA 131.255.244.0/22 AS262962 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 131.255.246.0/24.29 of 673
Route object: none131.255.246.0/24No route object for it. A route object for 131.255.244.0/22 with origin AS262962 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262962 in the RIR database for the space.29 of 673
ROA: maxLength131.255.247.0/24ROA 131.255.244.0/22 AS262962 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 131.255.247.0/24.29 of 673
Route object: none131.255.247.0/24No route object for it. A route object for 131.255.244.0/22 with origin AS262962 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262962 in the RIR database for the space.29 of 673
Route object: RIR131.255.244.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.85.56.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.85.56.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.85.57.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.85.58.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.85.59.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR131.255.244.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR131.255.245.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673

Route objects not announced

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

187.85.56.0/23RADBValid
2804:e98::/32ALTDB, RADBNo ROA
2804:e98::/33RADBNo 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.