Network · data from 2026-11-12
AS270256 VILDONET TELECOM
Registry name: AS270256 - VILDONET TELECOM, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270256, 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.108.172.0/23 | No ROA | Other IRR onlyTC | 670 100% |
| 200.108.172.0/24 | No ROA | Other IRR onlyRADB, TC | 670 100% |
| 200.108.173.0/24 | No ROA | Other IRR onlyRADB, TC | 670 100% |
| 200.108.174.0/23 | No ROA | Other IRR onlyRADB, TC | 665 99% |
| 200.108.174.0/24 | No ROA | Other IRR onlyRADB, TC | 665 99% |
| 200.108.175.0/24 | No ROA | Other IRR onlyRADB, TC | 665 99% |
| 2804:6938:8000::/33 | No ROA | Other IRR onlyTC | 631 99% |
| 2804:6938:8000::/34 | No ROA | Other IRR onlyTC | 631 99% |
| 2804:6938:c000::/34 | No ROA | Other IRR onlyTC | 631 99% |
AS-SET
AS270256'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 23 are in fix.csv.
- ROA: none9
- Route object: RIR9
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 200.108.172.0/23 | No ROA covers it. Add a ROA for AS270256, maxLength 23. |
| Route object: RIR | 200.108.172.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 200.108.172.0/24 | No ROA covers it. Add a ROA for AS270256, maxLength 24. |
| Route object: RIR | 200.108.172.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 200.108.173.0/24 | No ROA covers it. Add a ROA for AS270256, maxLength 24. |
| Route object: RIR | 200.108.173.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 200.108.174.0/23 | No ROA covers it. Add a ROA for AS270256, maxLength 23. |
| Route object: RIR | 200.108.174.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 200.108.174.0/24 | No ROA covers it. Add a ROA for AS270256, maxLength 24. |
| Route object: RIR | 200.108.174.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 200.108.175.0/24 | No ROA covers it. Add a ROA for AS270256, maxLength 24. |
| Route object: RIR | 200.108.175.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:6938:8000::/33 | No ROA covers it. Add a ROA for AS270256, maxLength 33. |
| Route object: RIR | 2804:6938:8000::/33 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 2804:6938:8000::/34 | No ROA covers it. Add a ROA for AS270256, maxLength 34. |
| Route object: RIR | 2804:6938:8000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 2804:6938:c000::/34 | No ROA covers it. Add a ROA for AS270256, maxLength 34. |
| Route object: RIR | 2804:6938:c000::/34 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS270256 whose prefix no peer sees AS270256 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 200.108.172.0/22 | ALTDB, RADB, TC | No ROA |
| 2804:6938::/32 | ALTDB, RADB, TC | No ROA |
| 2804:6938::/33 | TC | No ROA |
| 2804:6938::/34 | TC | No ROA |
| 2804:6938:4000::/34 | TC | No 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.