5.227.0.0/18 no ROA
Announced by AS8580 MTS PJSC.
Origin
| Origin AS | RPKI | Peers seeing it | Sample path | First seen | Last seen |
|---|---|---|---|---|---|
| AS8580 MTS PJSC | no ROA | 42 | 333383598580 | 2026-09-18 | 2026-10-09 |
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.227.0.0/16
- RIR
- RIPENCC
- Country
- 🇷🇺 RU
- Status
- allocated
- Allocated
- 2012-09-07
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 5.227.0.0/17 v4 | AS8359 MTS PJSC | no ROA | 42 | 33338359 | 2026-09-18 |
More specific routes
10 announced prefixes inside this one
| Prefix | Origin | RPKI | Peers | First seen |
|---|---|---|---|---|
| 5.227.0.0/21 v4 | AS8580 MTS PJSC | no ROA | 42 | 2026-09-18 |
| 5.227.16.0/23 v4 | AS8580 MTS PJSC | no ROA | 41 | 2026-09-18 |
| 5.227.24.0/22 v4 | AS8580 MTS PJSC | no ROA | 41 | 2026-09-18 |
| 5.227.40.0/22 v4 | AS8580 MTS PJSC | no ROA | 41 | 2026-09-18 |
| 5.227.44.0/24 v4 | AS8580 MTS PJSC | no ROA | 41 | 2026-09-18 |
| 5.227.45.0/24 v4 | AS8580 MTS PJSC | no ROA | 41 | 2026-09-18 |
| 5.227.46.0/24 v4 | AS8580 MTS PJSC | no ROA | 41 | 2026-09-18 |
| 5.227.47.0/24 v4 | AS8580 MTS PJSC | no ROA | 41 | 2026-09-18 |
| 5.227.52.0/23 v4 | AS8580 MTS PJSC | no ROA | 41 | 2026-09-18 |
| 5.227.54.0/23 v4 | AS8580 MTS PJSC | no ROA | 41 | 2026-09-18 |