bgpreport

Network · data from 2026-11-12

AS262820 Ola Telecomunicações Ltda

Registry name: AS262820 - OnLine Assis Telecomunicacoes Ltda-EPP, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262820, 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.
186.251.0.0/23 Valid Nonecovered by 186.251.0.0/22 203 30% 54
186.251.0.0/24 Valid Nonecovered by 186.251.0.0/22 203 30% 54
186.251.1.0/24 Valid Nonecovered by 186.251.0.0/22 203 30% 54
186.251.2.0/24 Valid Nonecovered by 186.251.0.0/22 203 30% 54
186.251.3.0/24 Valid Nonecovered by 186.251.0.0/22 203 30% 54
186.251.4.0/24 Valid Nonecovered by 186.251.4.0/22 203 30% 54
186.251.5.0/24 Valid Nonecovered by 186.251.4.0/22 203 30% 54
186.251.7.0/24 Valid Nonecovered by 186.251.4.0/22 203 30% 54
186.251.6.0/24 Valid Nonecovered by 186.251.4.0/22 202 30% 54
186.251.0.0/21 Valid Other IRR onlyRADB 667 99% 66
186.251.4.0/22 Valid Other IRR onlyRADB 667 99% 66
138.117.120.0/22 Valid Other IRR onlyRADB 666 99% 66
186.251.0.0/22 Valid Other IRR onlyRADB 666 99% 66
2804:288::/32 Valid Other IRR onlyRADB 628 99% 67

AS-SET

AS262820'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 15 are in fix.csv.

  • Route object: none9
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none186.251.0.0/23No route object for it. A route object for 186.251.0.0/22 with origin AS262820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262820 in the RIR database for the space.203 of 673
Route object: none186.251.0.0/24No route object for it. A route object for 186.251.0.0/22 with origin AS262820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262820 in the RIR database for the space.203 of 673
Route object: none186.251.1.0/24No route object for it. A route object for 186.251.0.0/22 with origin AS262820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262820 in the RIR database for the space.203 of 673
Route object: none186.251.2.0/24No route object for it. A route object for 186.251.0.0/22 with origin AS262820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262820 in the RIR database for the space.203 of 673
Route object: none186.251.3.0/24No route object for it. A route object for 186.251.0.0/22 with origin AS262820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262820 in the RIR database for the space.203 of 673
Route object: none186.251.4.0/24No route object for it. A route object for 186.251.4.0/22 with origin AS262820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262820 in the RIR database for the space.203 of 673
Route object: none186.251.5.0/24No route object for it. A route object for 186.251.4.0/22 with origin AS262820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262820 in the RIR database for the space.203 of 673
Route object: none186.251.7.0/24No route object for it. A route object for 186.251.4.0/22 with origin AS262820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262820 in the RIR database for the space.203 of 673
Route object: none186.251.6.0/24No route object for it. A route object for 186.251.4.0/22 with origin AS262820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262820 in the RIR database for the space.202 of 673
Route object: RIR186.251.0.0/21Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR186.251.4.0/22Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR138.117.120.0/22Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR186.251.0.0/22Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:288::/32Route object only in RADB. Add it in the RIR database for the space.628 of 636

Route objects not announced

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

45.173.232.0/23RADBNo 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.