bgpreport

Network · data from 2026-11-12

AS262521 pgf telecomunicacoes

Registry name: AS262521 - pgf telecomunicacoes ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262521, 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.108.84.0/23 No ROA Other IRR onlyTC 672 100% 66
131.108.87.0/24 No ROA Other IRR onlyTC 672 100% 66
177.67.144.0/22 No ROA Other IRR onlyRADB, TC 672 100% 66
177.67.145.0/24 No ROA Other IRR onlyTC 672 100% 66
131.108.86.0/24 No ROA Other IRR onlyTC 671 100% 66
177.67.144.0/24 No ROA Other IRR onlyTC 669 99% 67
2804:1d6c::/32 No ROA Other IRR onlyRADB 633 100% 69

AS-SET

AS262521'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 22 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none131.108.84.0/23No ROA covers it. Add a ROA for AS262521, maxLength 23.672 of 673
Route object: RIR131.108.84.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none131.108.87.0/24No ROA covers it. Add a ROA for AS262521, maxLength 24.672 of 673
Route object: RIR131.108.87.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none177.67.144.0/22No ROA covers it. Add a ROA for AS262521, maxLength 22.672 of 673
Route object: RIR177.67.144.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none177.67.145.0/24No ROA covers it. Add a ROA for AS262521, maxLength 24.672 of 673
Route object: RIR177.67.145.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none131.108.86.0/24No ROA covers it. Add a ROA for AS262521, maxLength 24.671 of 673
Route object: RIR131.108.86.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none177.67.144.0/24No ROA covers it. Add a ROA for AS262521, maxLength 24.669 of 673
Route object: RIR177.67.144.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:1d6c::/32No ROA covers it. Add a ROA for AS262521, maxLength 32.633 of 636
Route object: RIR2804:1d6c::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

131.108.84.0/22RADB, TCNo ROA
131.108.84.0/24TCNo ROA
131.108.85.0/24TCNo ROA
131.108.86.0/23TCNo ROA
177.67.144.0/23TCNo ROA
177.67.146.0/23TCNo ROA
177.67.146.0/24TCNo ROA
177.67.147.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.