5.166.160.0/19 no ROA
Announced by AS12768 JSC "ER-Telecom Holding".
Origin
| Origin AS | RPKI | Peers seeing it | Sample path | First seen | Last seen |
|---|---|---|---|---|---|
| AS12768 JSC "ER-Telecom Holding" | no ROA | 41 | 3454957304904912768 | 2026-09-18 | 2026-09-25 |
RPKI
No ROA covers this prefix
No ROA covers this prefix, so origin validation returns "unknown". That is not a fault; most of the table is still unsigned.
Registry
Who this address space is delegated to, regardless of whether it is routed
- Delegated block
- 5.164.0.0/14
- RIR
- RIPENCC
- Country
- 🇷🇺 RU
- Status
- allocated
- Allocated
- 2012-07-25
Less specific routes
Announced prefixes that contain this one
Nothing less specific is announced.
More specific routes
8 announced prefixes inside this one
| Prefix | Origin | RPKI | Peers | First seen |
|---|---|---|---|---|
| 5.166.160.0/22 v4 | AS12768 JSC "ER-Telecom Holding" | no ROA | 41 | 2026-09-18 |
| 5.166.164.0/22 v4 | AS12768 JSC "ER-Telecom Holding" | no ROA | 41 | 2026-09-18 |
| 5.166.168.0/22 v4 | AS12768 JSC "ER-Telecom Holding" | no ROA | 41 | 2026-09-18 |
| 5.166.172.0/22 v4 | AS12768 JSC "ER-Telecom Holding" | no ROA | 41 | 2026-09-18 |
| 5.166.176.0/22 v4 | AS12768 JSC "ER-Telecom Holding" | no ROA | 41 | 2026-09-18 |
| 5.166.180.0/22 v4 | AS12768 JSC "ER-Telecom Holding" | no ROA | 41 | 2026-09-18 |
| 5.166.184.0/22 v4 | AS12768 JSC "ER-Telecom Holding" | no ROA | 41 | 2026-09-18 |
| 5.166.188.0/22 v4 | AS12768 JSC "ER-Telecom Holding" | no ROA | 41 | 2026-09-18 |