176.123.168.0/21 - BGP Prefix
IPv4RIPE NCCassigned RPKI Valid
CIDR
176.123.168.0/21
IP Version
IPv4
Addresses
2K
Mask
/21 (255.255.248.0)
Country
🇷🇺 Russia
City
Moscow
RIR
RIPE NCC
Status
assigned
Allocated
2012-07-30
Announced BGP Routes
0 of 0 routesRPKI:
IRR:
Swipe sideways to see all columns →
| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| This prefix is not announced as a whole. Parts of it are announced as more-specific prefixes, see below. | ||||
More-Specific Announcements
4 more-specific announcements| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| 176.123.168.0/23 | AS29182 RU-JSCIOT JSC IOT | Valid | - | 2026-10-12 |
| 176.123.170.0/23 | AS29182 RU-JSCIOT JSC IOT | Valid | - | 2026-10-12 |
| 176.123.172.0/23 | AS29182 RU-JSCIOT JSC IOT | Valid | - | 2026-10-12 |
| 176.123.174.0/23 | AS29182 RU-JSCIOT JSC IOT | Valid | - | 2026-10-12 |
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 RIPE NCC regionWho bought and sold address space recently
API
Open https://api.ipctl.io/v1/prefix/176.123.168.0/21Returns prefix allocation, BGP routes, and more-specific subnets.
curl -s "https://api.ipctl.io/v1/prefix/176.123.168.0/21" | jq
External Links