Network · data from 2026-11-12
AS55424 Instatelecom
Registry name: INSTATELECOM-AS-AP - Instatelecom Limited, AF · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS55424, 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.
| 175.106.49.0/24 | No ROA | Other origin onlycovered by 175.106.48.0/21 | 673 100% |
| 175.106.50.0/24 | No ROA | Other origin onlycovered by 175.106.48.0/21 | 673 100% |
| 175.106.42.0/24 | No ROA | RIR databaseAPNIC, RADB | 673 100% |
| 175.106.53.0/24 | No ROA | RIR databaseAPNIC | 673 100% |
| 175.106.36.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 175.106.37.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 175.106.38.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 175.106.39.0/24 | No ROA | RIR databaseAPNIC | 672 100% |
| 175.106.44.0/24 | No ROA | RIR databaseAPNIC, RADB | 672 100% |
| 175.106.45.0/24 | No ROA | RIR databaseAPNIC, RADB | 672 100% |
| 175.106.46.0/24 | No ROA | RIR databaseAPNIC, RADB | 672 100% |
| 175.106.47.0/24 | No ROA | RIR databaseAPNIC, RADB | 672 100% |
| 103.17.60.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 117.104.224.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 117.104.228.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 163.47.160.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 175.106.32.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 175.106.33.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 175.106.34.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 175.106.35.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 175.106.40.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 175.106.41.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 175.106.57.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 175.106.58.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 175.106.59.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 175.106.60.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 175.106.61.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 175.106.62.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 175.106.63.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 185.178.144.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 185.178.145.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 185.178.146.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 185.178.147.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 175.106.48.0/24 | Valid | RIR databaseAPNIC | 672 100% |
AS-SET
AS55424'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 47 are in fix.csv.
- ROA: none12
- Route object: none2
- Route object: not announced33
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 175.106.49.0/24 | No ROA covers it. Add a ROA for AS55424, maxLength 24. |
| Route object: none | 175.106.49.0/24 | Route objects for it name AS9229. A route object for 175.106.48.0/21 with origin AS55424 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55424 in the RIR database for the space. |
| ROA: none | 175.106.50.0/24 | No ROA covers it. Add a ROA for AS55424, maxLength 24. |
| Route object: none | 175.106.50.0/24 | Route objects for it name AS55330. A route object for 175.106.48.0/21 with origin AS55424 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55424 in the RIR database for the space. |
| ROA: none | 175.106.42.0/24 | No ROA covers it. Add a ROA for AS55424, maxLength 24. |
| ROA: none | 175.106.53.0/24 | No ROA covers it. Add a ROA for AS55424, maxLength 24. |
| ROA: none | 175.106.36.0/24 | No ROA covers it. Add a ROA for AS55424, maxLength 24. |
| ROA: none | 175.106.37.0/24 | No ROA covers it. Add a ROA for AS55424, maxLength 24. |
| ROA: none | 175.106.38.0/24 | No ROA covers it. Add a ROA for AS55424, maxLength 24. |
| ROA: none | 175.106.39.0/24 | No ROA covers it. Add a ROA for AS55424, maxLength 24. |
| ROA: none | 175.106.44.0/24 | No ROA covers it. Add a ROA for AS55424, maxLength 24. |
| ROA: none | 175.106.45.0/24 | No ROA covers it. Add a ROA for AS55424, maxLength 24. |
| ROA: none | 175.106.46.0/24 | No ROA covers it. Add a ROA for AS55424, maxLength 24. |
| ROA: none | 175.106.47.0/24 | No ROA covers it. Add a ROA for AS55424, maxLength 24. |
Route objects not announced
Route objects with origin AS55424 whose prefix no peer sees AS55424 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.17.60.0/23 | APNIC | Valid |
| 103.17.60.0/24 | APNIC | Valid |
| 103.17.61.0/24 | APNIC | Valid |
| 103.17.62.0/23 | APNIC | Valid |
| 103.17.62.0/24 | APNIC | Valid |
| 103.17.63.0/24 | APNIC | Valid |
| 117.104.224.0/21 | APNIC | Valid |
| 117.104.224.0/23 | APNIC | Valid |
| 117.104.224.0/24 | APNIC | Valid |
| 117.104.225.0/24 | APNIC | Valid |
| 117.104.226.0/23 | APNIC | Valid |
| 117.104.226.0/24 | APNIC | Valid |
| 117.104.227.0/24 | APNIC | Valid |
| 117.104.228.0/23 | APNIC | Valid |
| 117.104.228.0/24 | APNIC | Valid |
| 117.104.229.0/24 | APNIC | Valid |
| 117.104.230.0/23 | APNIC | Valid |
| 117.104.230.0/24 | APNIC | Valid |
| 117.104.231.0/24 | APNIC | Valid |
| 163.47.160.0/24 | APNIC | Valid |
| 163.47.161.0/24 | APNIC | Valid |
| 163.47.162.0/24 | APNIC | Valid |
| 163.47.163.0/24 | APNIC | Valid |
| 175.106.32.0/22 | APNIC, RADB | Valid |
| 175.106.36.0/22 | APNIC | No ROA |
| 175.106.40.0/23 | APNIC, RADB | Valid |
| 175.106.43.0/24 | APNIC | No ROA |
| 175.106.44.0/22 | APNIC, RADB | No ROA |
| 175.106.48.0/21 | RADB | No ROA |
| 221.120.234.0/24 | APNIC, RADB | Valid |
| 2400:3080::/32 | APNIC, RADB | Valid |
| 2400:3080::/45 | APNIC | Valid |
| 2400:3080:8::/45 | APNIC | 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.