bgpreport

Network · data from 2026-11-12

AS270353 Tyna Host - Datacenter no Brasil

Registry name: AS270353 - Tyna Host - Datacenter no Brasil, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270353, 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.
200.9.154.0/23 No ROA Other IRR onlyALTDB, RADB, TC 672 100% 66
200.9.154.0/24 No ROA Other IRR onlyALTDB, RADB 667 99% 67
200.9.155.0/24 No ROA Other IRR onlyALTDB, RADB 667 99% 67
2804:6ab0::/32 No ROA Other IRR onlyRADB, TC 635 100% 67
191.96.224.0/24 Valid Nonecovered by 191.96.224.0/23 668 99% 67
191.96.225.0/24 Valid Other origin onlycovered by 191.96.224.0/23 668 99% 67
102.165.46.0/24 Valid Other IRR onlyRADB 669 99% 67
191.96.78.0/23 Valid Other IRR onlyRADB 669 99% 67
191.96.224.0/23 Valid RIR databaseRADB, RIPE 672 100% 66
191.96.78.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
191.96.79.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
191.101.131.0/24 Valid RIR databaseRADB, RIPE 669 99% 67

AS-SET

AS270353's PeeringDB record names no 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 14 are in fix.csv.

  • ROA: none4
  • Route object: none2
  • Route object: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none200.9.154.0/23No ROA covers it. Add a ROA for AS270353, maxLength 23.672 of 673
Route object: RIR200.9.154.0/23Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none200.9.154.0/24No ROA covers it. Add a ROA for AS270353, maxLength 24.667 of 673
Route object: RIR200.9.154.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.667 of 673
ROA: none200.9.155.0/24No ROA covers it. Add a ROA for AS270353, maxLength 24.667 of 673
Route object: RIR200.9.155.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.667 of 673
ROA: none2804:6ab0::/32No ROA covers it. Add a ROA for AS270353, maxLength 32.635 of 636
Route object: RIR2804:6ab0::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: none191.96.224.0/24No route object for it. A route object for 191.96.224.0/23 with origin AS270353 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270353 in the RIR database for the space.668 of 673
Route object: none191.96.225.0/24Route objects for it name AS60068. A route object for 191.96.224.0/23 with origin AS270353 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270353 in the RIR database for the space.668 of 673
Route object: RIR102.165.46.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR191.96.78.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

191.101.128.0/22RADBNo ROA
209.14.130.0/23RADBNo 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.