202.164.56.0/21 - Quadrant Televentures Limited (AS17917)
CIDR
202.164.56.0/21
IP Version
IPv4
Addresses
2K
Mask
/21 (255.255.248.0)
Country
🇮🇳 India
City
Jalandhar
RIR
APNIC
Status
announced
Allocated
-
Announced BGP Routes
1 of 1 routeRPKI:
IRR:
Swipe sideways to see all columns →
| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| 202.164.56.0/21 | AS17917 QTLTELECOM-AS-AP - Quadrant Televentures Limited | Valid | APNIC | 2026-10-12 |
Related Announcements
1 less-specific, 7 more-specific announcements| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| 202.164.48.0/20 | AS17917 QTLTELECOM-AS-AP - Quadrant Televentures Limited | Valid | - | 2026-10-12 |
| 202.164.56.0/24 | AS17917 QTLTELECOM-AS-AP - Quadrant Televentures Limited | Valid | - | 2026-10-12 |
| 202.164.57.0/24 | AS17917 QTLTELECOM-AS-AP - Quadrant Televentures Limited | Valid | - | 2026-10-12 |
| 202.164.59.0/24 | AS17917 QTLTELECOM-AS-AP - Quadrant Televentures Limited | Valid | - | 2026-10-12 |
| 202.164.60.0/24 | AS17917 QTLTELECOM-AS-AP - Quadrant Televentures Limited | Valid | - | 2026-10-12 |
| 202.164.61.0/24 | AS17917 QTLTELECOM-AS-AP - Quadrant Televentures Limited | Valid | - | 2026-10-12 |
| 202.164.62.0/24 | AS17917 QTLTELECOM-AS-AP - Quadrant Televentures Limited | Valid | - | 2026-10-12 |
| 202.164.63.0/24 | AS17917 QTLTELECOM-AS-AP - Quadrant Televentures Limited | Valid | - | 2026-10-12 |
RPKI ROAs
| Prefix | Origin | Max Length | Trust Anchor |
|---|---|---|---|
| 202.164.48.0/20 | AS17917 | /24 | apnic |
IRR Route Objects
| Origin | Registry | Maintainer | Modified |
|---|---|---|---|
| AS17917 | APNIC | MAINT-IN-IRINN | 2026-01-08 |
More Specific Prefixes
| Prefix | AS | Country | Status |
|---|---|---|---|
| 202.164.56.0/28 | 🇮🇳IN | assigned | |
| 202.164.56.16/28 | 🇮🇳IN | assigned | |
| 202.164.56.32/28 | 🇮🇳IN | assigned | |
| 202.164.56.48/28 | 🇮🇳IN | assigned | |
| 202.164.56.64/28 | 🇮🇳IN | assigned | |
| 202.164.56.80/28 | 🇮🇳IN | assigned | |
| 202.164.56.96/28 | 🇮🇳IN | assigned | |
| 202.164.56.112/28 | 🇮🇳IN | assigned | |
| 202.164.56.128/28 | 🇮🇳IN | assigned | |
| 202.164.56.144/28 | 🇮🇳IN | assigned | |
| 202.164.56.160/29 | 🇮🇳IN | assigned | |
| 202.164.56.168/29 | 🇮🇳IN | assigned | |
| 202.164.56.176/28 | 🇮🇳IN | assigned | |
| 202.164.56.192/28 | 🇮🇳IN | assigned | |
| 202.164.56.208/28 | 🇮🇳IN | assigned | |
| 202.164.56.224/27 | 🇮🇳IN | assigned | |
| 202.164.57.0/29 | 🇮🇳IN | assigned | |
| 202.164.57.8/29 | 🇮🇳IN | assigned | |
| 202.164.57.16/29 | 🇮🇳IN | assigned | |
| 202.164.57.24/29 | 🇮🇳IN | assigned | |
| 202.164.57.32/29 | 🇮🇳IN | assigned | |
| 202.164.57.40/29 | 🇮🇳IN | assigned | |
| 202.164.57.48/28 | 🇮🇳IN | assigned | |
| 202.164.57.64/29 | 🇮🇳IN | assigned | |
| 202.164.57.72/29 | 🇮🇳IN | assigned | |
| 202.164.57.80/29 | 🇮🇳IN | assigned | |
| 202.164.57.88/29 | 🇮🇳IN | assigned | |
| 202.164.57.96/29 | 🇮🇳IN | assigned | |
| 202.164.57.104/29 | 🇮🇳IN | assigned | |
| 202.164.57.112/29 | 🇮🇳IN | assigned | |
| 202.164.57.120/29 | 🇮🇳IN | assigned | |
| 202.164.57.128/29 | 🇮🇳IN | assigned | |
| 202.164.57.136/29 | 🇮🇳IN | assigned | |
| 202.164.57.144/29 | 🇮🇳IN | assigned | |
| 202.164.57.152/29 | 🇮🇳IN | assigned | |
| 202.164.57.160/29 | 🇮🇳IN | assigned | |
| 202.164.57.168/29 | 🇮🇳IN | assigned | |
| 202.164.57.176/29 | 🇮🇳IN | assigned | |
| 202.164.57.184/29 | 🇮🇳IN | assigned | |
| 202.164.57.192/28 | 🇮🇳IN | assigned | |
| 202.164.57.208/28 | 🇮🇳IN | assigned | |
| 202.164.57.224/29 | 🇮🇳IN | assigned | |
| 202.164.57.232/29 | 🇮🇳IN | assigned | |
| 202.164.57.240/29 | 🇮🇳IN | assigned | |
| 202.164.57.248/29 | 🇮🇳IN | assigned | |
| 202.164.58.0/24 | 🇮🇳IN | assigned | |
| 202.164.59.0/25 | 🇮🇳IN | assigned | |
| 202.164.59.128/26 | 🇮🇳IN | assigned | |
| 202.164.59.192/27 | 🇮🇳IN | assigned | |
| 202.164.59.224/27 | 🇮🇳IN | assigned | |
| 202.164.60.0/26 | 🇮🇳IN | assigned | |
| 202.164.60.64/28 | 🇮🇳IN | assigned | |
| 202.164.60.80/28 | 🇮🇳IN | assigned | |
| 202.164.60.96/29 | 🇮🇳IN | assigned | |
| 202.164.60.104/29 | 🇮🇳IN | assigned | |
| 202.164.60.112/29 | 🇮🇳IN | assigned | |
| 202.164.60.120/29 | 🇮🇳IN | assigned | |
| 202.164.60.128/28 | 🇮🇳IN | assigned | |
| 202.164.60.144/29 | 🇮🇳IN | assigned | |
| 202.164.60.152/29 | 🇮🇳IN | assigned | |
| 202.164.60.160/29 | 🇮🇳IN | assigned | |
| 202.164.60.168/29 | 🇮🇳IN | assigned | |
| 202.164.60.176/29 | 🇮🇳IN | assigned | |
| 202.164.60.184/29 | 🇮🇳IN | assigned | |
| 202.164.60.192/27 | 🇮🇳IN | assigned | |
| 202.164.60.224/27 | 🇮🇳IN | assigned | |
| 202.164.62.0/28 | 🇮🇳IN | assigned | |
| 202.164.62.16/28 | 🇮🇳IN | assigned | |
| 202.164.62.32/28 | 🇮🇳IN | assigned | |
| 202.164.62.48/28 | 🇮🇳IN | assigned | |
| 202.164.62.64/26 | 🇮🇳IN | assigned | |
| 202.164.62.128/28 | 🇮🇳IN | assigned | |
| 202.164.62.144/28 | 🇮🇳IN | assigned | |
| 202.164.62.160/28 | 🇮🇳IN | assigned | |
| 202.164.62.176/28 | 🇮🇳IN | assigned | |
| 202.164.62.192/28 | 🇮🇳IN | assigned | |
| 202.164.62.208/29 | 🇮🇳IN | assigned | |
| 202.164.62.216/29 | 🇮🇳IN | assigned | |
| 202.164.62.224/28 | 🇮🇳IN | assigned | |
| 202.164.62.240/28 | 🇮🇳IN | assigned | |
| 202.164.63.0/28 | 🇮🇳IN | assigned | |
| 202.164.63.16/28 | 🇮🇳IN | assigned | |
| 202.164.63.32/27 | 🇮🇳IN | assigned | |
| 202.164.63.64/28 | 🇮🇳IN | assigned | |
| 202.164.63.80/28 | 🇮🇳IN | assigned | |
| 202.164.63.96/28 | 🇮🇳IN | assigned | |
| 202.164.63.112/28 | 🇮🇳IN | assigned | |
| 202.164.63.128/25 | 🇮🇳IN | assigned |
Related Prefixes
Geolocation
Learn more
- RPKI and ROAs explainedWhat RPKI valid, invalid and no ROA mean
- RPKI validatorCheck ROA coverage for any prefix or ASN
- What is BGP?How prefixes are announced and routed
- More-specific prefixesGlossary: covering and more-specific routes
- IPv4 transfers in the APNIC regionWho bought and sold address space recently
API
Open https://api.ipctl.io/v1/prefix/202.164.56.0/21Returns prefix allocation, BGP routes, and more-specific subnets.
curl -s "https://api.ipctl.io/v1/prefix/202.164.56.0/21" | jq
External Links