Network · data from 2026-11-12
AS133237 Apex Netcom India
Registry name: APEXNETCOMM-AS-IN - Apex Netcom India Pvt. Ltd., IN · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS133237, 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.
| 144.48.168.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 144.48.170.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 144.48.171.0/24 | Valid | Other IRR onlyRADB | 672 100% |
AS-SET
AS133237'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 19 are in fix.csv.
- Route object: RIR3
- Route object: not announced16
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 144.48.168.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 144.48.170.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 144.48.171.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS133237 whose prefix no peer sees AS133237 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.110.12.0/22 | APNIC | Valid |
| 103.110.12.0/23 | APNIC | Valid |
| 103.110.12.0/24 | APNIC | Valid |
| 103.110.13.0/24 | APNIC | Valid |
| 103.110.14.0/23 | APNIC | Valid |
| 103.110.14.0/24 | APNIC | Valid |
| 103.110.15.0/24 | APNIC | Valid |
| 103.170.242.0/23 | APNIC | Valid |
| 103.170.242.0/24 | APNIC | Valid |
| 103.170.243.0/24 | APNIC | Valid |
| 103.228.140.0/24 | APNIC | Valid |
| 103.228.141.0/24 | APNIC | Valid |
| 103.228.142.0/24 | APNIC | Valid |
| 103.228.143.0/24 | APNIC | Valid |
| 144.48.168.0/22 | APNIC | Valid |
| 144.48.169.0/24 | 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.