bgpreport

Network · data from 2026-11-12

AS265298 AS265298 - GR TELECOMUNICACOES LTDA ME

Registry name: AS265298 - GR TELECOMUNICACOES LTDA ME, BR · not in PeeringDB

7IPv4 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
8No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS265298, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS265298, 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.

168.90.248.0/22 No ROA Other IRR onlyALTDB, RADB, TC 663 99% 67
168.90.248.0/23 No ROA Other IRR onlyTC 663 99% 67
168.90.250.0/23 No ROA Other IRR onlyTC 663 99% 67
168.90.248.0/24 No ROA Other IRR onlyTC 662 98% 67
168.90.249.0/24 No ROA Other IRR onlyTC 661 98% 67
168.90.250.0/24 No ROA Other IRR onlyRADB, TC 661 98% 67
168.90.251.0/24 No ROA Other IRR onlyTC 661 98% 67
2804:2db4::/32 No ROA Other IRR onlyALTDB, RADB, TC 628 99% 67

AS-SET

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

  • ROA: none8
  • Route object: RIR8
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none168.90.248.0/22No ROA covers it. Add a ROA for AS265298, maxLength 22.663 of 673
Route object: RIR168.90.248.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.663 of 673
ROA: none168.90.248.0/23No ROA covers it. Add a ROA for AS265298, maxLength 23.663 of 673
Route object: RIR168.90.248.0/23Route object only in TC. Add it in the RIR database for the space.663 of 673
ROA: none168.90.250.0/23No ROA covers it. Add a ROA for AS265298, maxLength 23.663 of 673
Route object: RIR168.90.250.0/23Route object only in TC. Add it in the RIR database for the space.663 of 673
ROA: none168.90.248.0/24No ROA covers it. Add a ROA for AS265298, maxLength 24.662 of 673
Route object: RIR168.90.248.0/24Route object only in TC. Add it in the RIR database for the space.662 of 673
ROA: none168.90.249.0/24No ROA covers it. Add a ROA for AS265298, maxLength 24.661 of 673
Route object: RIR168.90.249.0/24Route object only in TC. Add it in the RIR database for the space.661 of 673
ROA: none168.90.250.0/24No ROA covers it. Add a ROA for AS265298, maxLength 24.661 of 673
Route object: RIR168.90.250.0/24Route object only in RADB, TC. Add it in the RIR database for the space.661 of 673
ROA: none168.90.251.0/24No ROA covers it. Add a ROA for AS265298, maxLength 24.661 of 673
Route object: RIR168.90.251.0/24Route object only in TC. Add it in the RIR database for the space.661 of 673
ROA: none2804:2db4::/32No ROA covers it. Add a ROA for AS265298, maxLength 32.628 of 636
Route object: RIR2804:2db4::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.628 of 636

Route objects not announced

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

2804:2db4::/33TCNo ROA
2804:2db4::/34TCNo ROA
2804:2db4:4000::/34TCNo ROA
2804:2db4:8000::/33TCNo ROA
2804:2db4:8000::/34TCNo ROA
2804:2db4:c000::/34TCNo 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.