bgpreport

Network · data from 2026-11-12

AS265467 AS265467 - LOCALL TELECOM LTDA. - ME

Registry name: AS265467 - LOCALL TELECOM LTDA. - ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265467, 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.74.97.0/24 No ROA None 671 100% 67
168.196.232.0/24 No ROA Nonecovered by 168.196.232.0/23 666 99% 67
168.196.233.0/24 No ROA Nonecovered by 168.196.232.0/23 666 99% 67
168.196.234.0/24 Valid Nonecovered by 168.196.234.0/23 671 100% 67
168.196.235.0/24 Valid Nonecovered by 168.196.234.0/23 671 100% 67
168.196.234.0/23 Valid Other IRR onlyTC 671 100% 67
2804:3498::/32 Valid Other IRR onlyRADB, TC 634 100% 67

AS-SET

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

  • ROA: none3
  • Route object: none5
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none177.74.97.0/24No ROA covers it. Add a ROA for AS265467, maxLength 24.671 of 673
Route object: none177.74.97.0/24No route object for it. Add a route object with origin AS265467 in the RIR database for the space.671 of 673
ROA: none168.196.232.0/24No ROA covers it. Add a ROA for AS265467, maxLength 24.666 of 673
Route object: none168.196.232.0/24No route object for it. A route object for 168.196.232.0/23 with origin AS265467 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265467 in the RIR database for the space.666 of 673
ROA: none168.196.233.0/24No ROA covers it. Add a ROA for AS265467, maxLength 24.666 of 673
Route object: none168.196.233.0/24No route object for it. A route object for 168.196.232.0/23 with origin AS265467 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265467 in the RIR database for the space.666 of 673
Route object: none168.196.234.0/24No route object for it. A route object for 168.196.234.0/23 with origin AS265467 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265467 in the RIR database for the space.671 of 673
Route object: none168.196.235.0/24No route object for it. A route object for 168.196.234.0/23 with origin AS265467 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265467 in the RIR database for the space.671 of 673
Route object: RIR168.196.234.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:3498::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

168.196.232.0/22RADB, TCNo ROA
168.196.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.