Network · data from 2026-11-12
AS56017 VITI-AS-PF - VITI
Registry name: VITI-AS-PF - VITI, PF · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS56017, 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.
| 38.51.136.0/24 | Valid | Nonecovered by 38.51.136.0/22 | 671 100% |
| 38.51.137.0/24 | Valid | Nonecovered by 38.51.136.0/22 | 671 100% |
| 38.51.138.0/24 | Valid | Nonecovered by 38.51.136.0/22 | 671 100% |
| 38.51.139.0/24 | Valid | Nonecovered by 38.51.136.0/22 | 671 100% |
| 38.51.136.0/22 | Valid | RIR databaseARIN, RADB | 671 100% |
| 43.249.176.0/22 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 43.249.176.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 43.249.177.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 43.249.178.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 43.249.179.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.4.72.0/22 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.4.72.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.4.73.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.4.74.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 103.4.75.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 113.197.68.0/22 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 113.197.68.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 113.197.69.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 113.197.70.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 113.197.71.0/24 | Valid | RIR databaseAPNIC | 671 100% |
AS-SET
AS56017 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 10 are in fix.csv.
- Route object: none4
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 38.51.136.0/24 | No route object for it. A route object for 38.51.136.0/22 with origin AS56017 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56017 in the RIR database for the space. |
| Route object: none | 38.51.137.0/24 | No route object for it. A route object for 38.51.136.0/22 with origin AS56017 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56017 in the RIR database for the space. |
| Route object: none | 38.51.138.0/24 | No route object for it. A route object for 38.51.136.0/22 with origin AS56017 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56017 in the RIR database for the space. |
| Route object: none | 38.51.139.0/24 | No route object for it. A route object for 38.51.136.0/22 with origin AS56017 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56017 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS56017 whose prefix no peer sees AS56017 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 43.249.176.0/23 | APNIC | Valid |
| 43.249.178.0/23 | APNIC | Valid |
| 103.4.72.0/23 | APNIC, RADB | Valid |
| 103.4.74.0/23 | APNIC, RADB | Valid |
| 113.197.68.0/23 | APNIC, RADB | Valid |
| 113.197.70.0/23 | APNIC, RADB | Valid |
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.