bgpreport

Network · data from 2026-11-12

AS53071 AS53071 - Tecnoasp Tecnologia e Servicos de Comunicacao Ltda

Registry name: AS53071 - Tecnoasp Tecnologia e Servicos de Comunicacao Ltda, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53071, 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:92b8::/34 No ROA Nonecovered by 2804:92b8::/32 634 100% 67
2804:92b8:4000::/34 No ROA Nonecovered by 2804:92b8::/32 634 100% 67
2804:92b8:8000::/34 No ROA Nonecovered by 2804:92b8::/32 634 100% 67
2804:92b8:c000::/34 No ROA Nonecovered by 2804:92b8::/32 634 100% 67

AS-SET

AS53071 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 19 are in fix.csv.

  • ROA: none4
  • Route object: none4
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none2804:92b8::/34No ROA covers it. Add a ROA for AS53071, maxLength 34.634 of 636
Route object: none2804:92b8::/34No route object for it. A route object for 2804:92b8::/32 with origin AS53071 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53071 in the RIR database for the space.634 of 636
ROA: none2804:92b8:4000::/34No ROA covers it. Add a ROA for AS53071, maxLength 34.634 of 636
Route object: none2804:92b8:4000::/34No route object for it. A route object for 2804:92b8::/32 with origin AS53071 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53071 in the RIR database for the space.634 of 636
ROA: none2804:92b8:8000::/34No ROA covers it. Add a ROA for AS53071, maxLength 34.634 of 636
Route object: none2804:92b8:8000::/34No route object for it. A route object for 2804:92b8::/32 with origin AS53071 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53071 in the RIR database for the space.634 of 636
ROA: none2804:92b8:c000::/34No ROA covers it. Add a ROA for AS53071, maxLength 34.634 of 636
Route object: none2804:92b8:c000::/34No route object for it. A route object for 2804:92b8::/32 with origin AS53071 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53071 in the RIR database for the space.634 of 636

Route objects not announced

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

187.84.144.0/20BBOI, NTTCOM, RADBNo ROA
187.84.144.0/21RADBNo ROA
187.84.148.0/24RADBNo ROA
187.84.149.0/24RADBNo ROA
187.84.150.0/24RADBNo ROA
187.84.151.0/24RADBNo ROA
187.84.152.0/23RADBNo ROA
187.84.154.0/23RADBNo ROA
187.84.154.0/24RADBNo ROA
187.84.155.0/24RADBNo ROA
2804:92b8::/32BBOI, NTTCOMNo 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.