bgpreport

Network · data from 2026-11-12

AS273757 AS273757 - NEW TELECOM TELECOMUNICACOES

Registry name: AS273757 - NEW TELECOM TELECOMUNICACOES, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273757, 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:8bc4:2008::/47 No ROA Nonecovered by 2804:8bc4:2000::/35 633 100% 67
2804:8bc4:2000::/35 No ROA Other IRR onlyRADB 633 100% 67
209.61.35.0/24 Valid RIR databaseARIN, RADB 672 100% 67

AS-SET

AS273757 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 5 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2804:8bc4:2008::/47No ROA covers it. Add a ROA for AS273757, maxLength 47.633 of 636
Route object: none2804:8bc4:2008::/47No route object for it. A route object for 2804:8bc4:2000::/35 with origin AS273757 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273757 in the RIR database for the space.633 of 636
ROA: none2804:8bc4:2000::/35No ROA covers it. Add a ROA for AS273757, maxLength 35.633 of 636
Route object: RIR2804:8bc4:2000::/35Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

2804:8bc4::/32RADBNo 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.