bgpreport

Network · data from 2026-11-12

AS266422 AS266422 - Atus Servicos e Comercio de Produtos de Informatic

Registry name: AS266422 - Atus Servicos e Comercio de Produtos de Informatic, BR · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
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
3Route objects not announced registered with origin AS266422, seen from no peer

Announced routes

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

170.81.206.0/24 No ROA Nonecovered by 170.81.204.0/22 669 99% 67
170.81.207.0/24 No ROA Nonecovered by 170.81.204.0/22 669 99% 67
170.81.204.0/24 No ROA Nonecovered by 170.81.204.0/22 666 99% 67
170.81.205.0/24 No ROA Nonecovered by 170.81.204.0/22 666 99% 67

AS-SET

AS266422 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 11 are in fix.csv.

  • ROA: none4
  • Route object: none4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none170.81.206.0/24No ROA covers it. Add a ROA for AS266422, maxLength 24.669 of 673
Route object: none170.81.206.0/24No route object for it. A route object for 170.81.204.0/22 with origin AS266422 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266422 in the RIR database for the space.669 of 673
ROA: none170.81.207.0/24No ROA covers it. Add a ROA for AS266422, maxLength 24.669 of 673
Route object: none170.81.207.0/24No route object for it. A route object for 170.81.204.0/22 with origin AS266422 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266422 in the RIR database for the space.669 of 673
ROA: none170.81.204.0/24No ROA covers it. Add a ROA for AS266422, maxLength 24.666 of 673
Route object: none170.81.204.0/24No route object for it. A route object for 170.81.204.0/22 with origin AS266422 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266422 in the RIR database for the space.666 of 673
ROA: none170.81.205.0/24No ROA covers it. Add a ROA for AS266422, maxLength 24.666 of 673
Route object: none170.81.205.0/24No route object for it. A route object for 170.81.204.0/22 with origin AS266422 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266422 in the RIR database for the space.666 of 673

Route objects not announced

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

170.81.204.0/22RADBNo ROA
2801:80:1280::/48RADBNo ROA
2804:3794::/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.