Network · data from 2026-11-12
AS154024 FLEXEERE IT SOLUTIONS
Registry name: FLEXEERE-IN - FLEXEERE IT SOLUTIONS PVT LTD, IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS154024, 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.
| 160.25.225.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 160.25.224.0/23 | No ROA | None | 39 6%low visibility |
| 103.73.8.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 103.109.116.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 103.109.118.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 103.148.118.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 130.117.181.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 103.124.208.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.124.209.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 138.252.170.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 138.252.171.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 160.191.10.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 160.191.11.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 163.227.88.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.71.184.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.15.156.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 2001:df2:36c0::/48 | Valid | RIR databaseAPNIC | 636 100% |
| 2401:8ea0::/32 | Valid | RIR databaseAPNIC | 636 100% |
| 2001:df7:3840::/48 | Valid | RIR databaseAPNIC | 1 0%low visibility |
AS-SET
AS154024'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 24 are in fix.csv.
- ROA: origin1
- ROA: none6
- Route object: none2
- Route object: RIR5
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 160.25.225.0/24 | ROAs covering it name AS152702, not AS154024. If AS154024 should announce it, add a ROA for AS154024. |
| Route object: none | 160.25.225.0/24 | Route objects for it name AS152702. Add a route object with origin AS154024 in the RIR database for the space. |
| ROA: none | 160.25.224.0/23 | No ROA covers it. Add a ROA for AS154024, maxLength 23. |
| Route object: none | 160.25.224.0/23 | No route object for it. Add a route object with origin AS154024 in the RIR database for the space. |
| ROA: none | 103.73.8.0/23 | No ROA covers it. Add a ROA for AS154024, maxLength 23. |
| Route object: RIR | 103.73.8.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.109.116.0/23 | No ROA covers it. Add a ROA for AS154024, maxLength 23. |
| Route object: RIR | 103.109.116.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.109.118.0/23 | No ROA covers it. Add a ROA for AS154024, maxLength 23. |
| Route object: RIR | 103.109.118.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.148.118.0/24 | No ROA covers it. Add a ROA for AS154024, maxLength 24. |
| Route object: RIR | 103.148.118.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 130.117.181.0/24 | No ROA covers it. Add a ROA for AS154024, maxLength 24. |
| Route object: RIR | 130.117.181.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS154024 whose prefix no peer sees AS154024 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.15.156.0/23 | APNIC | Valid |
| 103.15.157.0/24 | APNIC | Valid |
| 103.124.208.0/23 | APNIC | Valid |
| 138.252.170.0/23 | APNIC | Valid |
| 151.158.170.0/24 | APNIC | Valid |
| 160.191.10.0/23 | APNIC | Valid |
| 163.227.88.0/23 | APNIC | Valid |
| 163.227.89.0/24 | APNIC | Valid |
| 202.71.184.0/23 | APNIC | Valid |
| 202.71.185.0/24 | 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.