bgpreport

Network · data from 2026-11-12

AS271265 AS271265 - TUDO ON TELECOMUNICACOES

Registry name: AS271265 - TUDO ON TELECOMUNICACOES, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271265, 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.
2804:78c8::/32 No ROA Other IRR onlyALTDB, RADB, TC 633 100% 67
170.233.200.0/22 Valid Other IRR onlyALTDB, RADB, TC 669 99% 66
170.233.201.0/24 Valid Other IRR onlyRADB, TC 664 99% 67
170.233.202.0/23 Valid Other IRR onlyRADB 664 99% 67
170.233.200.0/23 Valid Other IRR onlyRADB 663 99% 67
2804:78c8:e000::/42 Valid Other IRR onlyRADB 633 100% 67
2804:78c8:2000::/36 Valid Other IRR onlyRADB 630 99% 67
2804:78c8:3000::/36 Valid Other IRR onlyRADB 630 99% 67

AS-SET

AS271265 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 10 are in fix.csv.

  • ROA: none1
  • Route object: RIR8
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2804:78c8::/32No ROA covers it. Add a ROA for AS271265, maxLength 32.633 of 636
Route object: RIR2804:78c8::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR170.233.200.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR170.233.201.0/24Route object only in RADB, TC. Add it in the RIR database for the space.664 of 673
Route object: RIR170.233.202.0/23Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR170.233.200.0/23Route object only in RADB. Add it in the RIR database for the space.663 of 673
Route object: RIR2804:78c8:e000::/42Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:78c8:2000::/36Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:78c8:3000::/36Route object only in RADB. Add it in the RIR database for the space.630 of 636

Route objects not announced

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

2804:78c8:c000::/35RADBNo 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.