Network · data from 2026-11-12
AS270313 AS270313 - WN Tellecom
Registry name: AS270313 - WN Tellecom, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270313, 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.
| 177.10.72.0/23 | No ROA | Nonecovered by 177.10.72.0/22 | 2 0%low visibility |
| 177.10.72.0/24 | No ROA | Nonecovered by 177.10.72.0/22 | 2 0%low visibility |
| 177.10.73.0/24 | No ROA | Nonecovered by 177.10.72.0/22 | 2 0%low visibility |
| 177.10.74.0/23 | No ROA | Nonecovered by 177.10.72.0/22 | 2 0%low visibility |
| 177.10.74.0/24 | No ROA | Nonecovered by 177.10.72.0/22 | 2 0%low visibility |
| 177.10.75.0/24 | No ROA | Nonecovered by 177.10.72.0/22 | 2 0%low visibility |
| 177.10.72.0/22 | No ROA | Other IRR onlyRADB, TC | 665 99% |
| 2804:6a1c::/32 | No ROA | Other IRR onlyRADB, TC | 636 100% |
AS-SET
AS270313 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 16 are in fix.csv.
- ROA: none8
- Route object: none6
- Route object: RIR2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 177.10.72.0/23 | No ROA covers it. Add a ROA for AS270313, maxLength 23. |
| Route object: none | 177.10.72.0/23 | No route object for it. A route object for 177.10.72.0/22 with origin AS270313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270313 in the RIR database for the space. |
| ROA: none | 177.10.72.0/24 | No ROA covers it. Add a ROA for AS270313, maxLength 24. |
| Route object: none | 177.10.72.0/24 | No route object for it. A route object for 177.10.72.0/22 with origin AS270313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270313 in the RIR database for the space. |
| ROA: none | 177.10.73.0/24 | No ROA covers it. Add a ROA for AS270313, maxLength 24. |
| Route object: none | 177.10.73.0/24 | No route object for it. A route object for 177.10.72.0/22 with origin AS270313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270313 in the RIR database for the space. |
| ROA: none | 177.10.74.0/23 | No ROA covers it. Add a ROA for AS270313, maxLength 23. |
| Route object: none | 177.10.74.0/23 | No route object for it. A route object for 177.10.72.0/22 with origin AS270313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270313 in the RIR database for the space. |
| ROA: none | 177.10.74.0/24 | No ROA covers it. Add a ROA for AS270313, maxLength 24. |
| Route object: none | 177.10.74.0/24 | No route object for it. A route object for 177.10.72.0/22 with origin AS270313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270313 in the RIR database for the space. |
| ROA: none | 177.10.75.0/24 | No ROA covers it. Add a ROA for AS270313, maxLength 24. |
| Route object: none | 177.10.75.0/24 | No route object for it. A route object for 177.10.72.0/22 with origin AS270313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270313 in the RIR database for the space. |
| ROA: none | 177.10.72.0/22 | No ROA covers it. Add a ROA for AS270313, maxLength 22. |
| Route object: RIR | 177.10.72.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:6a1c::/32 | No ROA covers it. Add a ROA for AS270313, maxLength 32. |
| Route object: RIR | 2804:6a1c::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS270313 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.