bgpreport

Network · data from 2026-11-12

AS270604 AS270604 - AT3 TECNOLOGIA EIRELI

Registry name: AS270604 - AT3 TECNOLOGIA EIRELI, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270604, 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.
187.0.32.0/23 Valid Nonecovered by 187.0.32.0/22 672 100% 67
187.0.34.0/23 Valid Nonecovered by 187.0.32.0/22 672 100% 67
187.0.32.0/22 Valid Other IRR onlyRADB 672 100% 67
2804:6e8c::/32 Valid Other IRR onlyRADB 633 100% 67
187.0.32.0/24 Valid Other IRR onlyRADB 159 24% 50
187.0.33.0/24 Valid Other IRR onlyRADB 159 24% 50
187.0.34.0/24 Valid Other IRR onlyRADB 159 24% 50
187.0.35.0/24 Valid Other IRR onlyRADB 158 23% 50

AS-SET

AS270604 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 8 are in fix.csv.

  • Route object: none2
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
Route object: none187.0.32.0/23No route object for it. A route object for 187.0.32.0/22 with origin AS270604 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270604 in the RIR database for the space.672 of 673
Route object: none187.0.34.0/23No route object for it. A route object for 187.0.32.0/22 with origin AS270604 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270604 in the RIR database for the space.672 of 673
Route object: RIR187.0.32.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:6e8c::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR187.0.32.0/24Route object only in RADB. Add it in the RIR database for the space.159 of 673
Route object: RIR187.0.33.0/24Route object only in RADB. Add it in the RIR database for the space.159 of 673
Route object: RIR187.0.34.0/24Route object only in RADB. Add it in the RIR database for the space.159 of 673
Route object: RIR187.0.35.0/24Route object only in RADB. Add it in the RIR database for the space.158 of 673

Route objects not announced

Every route object with origin AS270604 is announced.

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.