Network · data from 2026-11-12
AS13357 Irati Telecomunicações Ltda.
Registry name: AS13357 - Ampernet Telecomunicacoes Ltda, BR · PeeringDB
12IPv4 routes
100.0% RPKI valid · 25.0% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
9 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS13357, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS13357, 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.192.96.0/23 | Valid | Nonecovered by 200.192.96.0/22 | 128 19% |
| 200.192.96.0/24 | Valid | Nonecovered by 200.192.96.0/22 | 128 19% |
| 200.192.100.0/23 | Valid | Nonecovered by 200.192.100.0/22 | 128 19% |
| 200.192.97.0/24 | Valid | Nonecovered by 200.192.96.0/22 | 127 19% |
| 200.192.98.0/23 | Valid | Nonecovered by 200.192.96.0/22 | 127 19% |
| 200.192.98.0/24 | Valid | Nonecovered by 200.192.96.0/22 | 127 19% |
| 200.192.101.0/24 | Valid | Nonecovered by 200.192.100.0/22 | 127 19% |
| 200.192.102.0/23 | Valid | Nonecovered by 200.192.100.0/22 | 127 19% |
| 200.192.103.0/24 | Valid | Nonecovered by 200.192.100.0/22 | 127 19% |
| 200.192.96.0/21 | Valid | Other IRR onlyRADB | 671 100% |
| 200.192.96.0/22 | Valid | Other IRR onlyRADB | 670 100% |
| 200.192.100.0/22 | Valid | Other IRR onlyRADB | 670 100% |
| 2804:7acc::/32 | Valid | Other IRR onlyRADB | 634 100% |
AS-SET
AS13357'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 13 are in fix.csv.
- Route object: none9
- Route object: RIR4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 200.192.96.0/23 | No route object for it. A route object for 200.192.96.0/22 with origin AS13357 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13357 in the RIR database for the space. |
| Route object: none | 200.192.96.0/24 | No route object for it. A route object for 200.192.96.0/22 with origin AS13357 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13357 in the RIR database for the space. |
| Route object: none | 200.192.100.0/23 | No route object for it. A route object for 200.192.100.0/22 with origin AS13357 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13357 in the RIR database for the space. |
| Route object: none | 200.192.97.0/24 | No route object for it. A route object for 200.192.96.0/22 with origin AS13357 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13357 in the RIR database for the space. |
| Route object: none | 200.192.98.0/23 | No route object for it. A route object for 200.192.96.0/22 with origin AS13357 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13357 in the RIR database for the space. |
| Route object: none | 200.192.98.0/24 | No route object for it. A route object for 200.192.96.0/22 with origin AS13357 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13357 in the RIR database for the space. |
| Route object: none | 200.192.101.0/24 | No route object for it. A route object for 200.192.100.0/22 with origin AS13357 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13357 in the RIR database for the space. |
| Route object: none | 200.192.102.0/23 | No route object for it. A route object for 200.192.100.0/22 with origin AS13357 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13357 in the RIR database for the space. |
| Route object: none | 200.192.103.0/24 | No route object for it. A route object for 200.192.100.0/22 with origin AS13357 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13357 in the RIR database for the space. |
| Route object: RIR | 200.192.96.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.192.96.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.192.100.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:7acc::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS13357 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.