Routing security
AS48612 RTC-ORENBURG-AS MTS Orenburg
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS48612 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 62.118.96.0/24 | RPKI invalid · length | IRR covering | 7 |
| 62.118.97.0/24 | RPKI invalid · length | IRR covering | 7 |
| 31.29.147.0/24 | No ROA | No IRR | 50 |
| 5.227.122.0/24 | No ROA | IRR | 50 |
| 5.227.123.0/24 | No ROA | IRR | 50 |
| 31.29.181.0/24 | No ROA | IRR | 38 |
| 31.29.182.0/23 | No ROA | IRR | 50 |
| 31.29.188.0/24 | No ROA | IRR | 50 |
| 31.29.212.0/23 | No ROA | IRR | 50 |
| 31.29.212.0/24 | No ROA | IRR | 50 |
| 31.29.213.0/24 | No ROA | IRR | 50 |
| 31.29.214.0/24 | No ROA | IRR | 50 |
| 31.29.215.0/24 | No ROA | IRR | 50 |
| 91.185.72.0/23 | No ROA | IRR covering | 50 |
| 91.185.72.0/24 | No ROA | IRR covering | 50 |
| 91.185.73.0/24 | No ROA | IRR covering | 50 |
| 91.185.74.0/24 | No ROA | IRR covering | 50 |
| 91.185.75.0/24 | No ROA | IRR covering | 50 |
| 91.211.124.0/23 | No ROA | IRR | 50 |
| 91.211.124.0/24 | No ROA | IRR | 50 |
| 91.211.125.0/24 | No ROA | IRR | 50 |
| 91.211.126.0/24 | No ROA | IRR | 50 |
| 91.211.127.0/24 | No ROA | IRR | 50 |
| 92.246.204.0/24 | No ROA | IRR | 50 |
| 92.246.205.0/24 | No ROA | IRR | 50 |
| 92.246.206.0/24 | No ROA | IRR | 50 |
| 92.246.207.0/24 | No ROA | IRR | 50 |
| 92.246.220.0/24 | No ROA | IRR | 50 |
| 92.246.221.0/24 | No ROA | IRR | 50 |
| 62.118.96.0/23 | RPKI valid | IRR | 50 |
| 85.140.126.0/24 | RPKI valid | IRR | 50 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS48612 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 62.118.96.0/23 | /23 | RIPENCC |
| 85.140.126.0/24 | /24 | RIPENCC |
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.
IRR
Registered route objects
Route objects naming AS48612 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.
| Prefix | Source | Description | Maintainer | Changed | Routing |
|---|---|---|---|---|---|
| 5.227.122.0/23 | RIPE | MTS Orenburg branch | AS8580-MNT | 2014-12-16 | Not announced |
| 31.29.214.0/23 | RIPE | MTS Orenburg branch | MNT-RTC-ORENBURG | 2014-12-16 | Not announced |
| 91.185.72.0/22 | RIPE | MTS-ORENBURG-21 | MTU-NOC | 2021-09-01 | Not announced |
| 91.211.126.0/23 | RIPE | Regional Technical Center CJSC | MNT-RTC-ORENBURG | 2011-09-23 | Not announced |
| 92.246.204.0/22 | RIPE | Regional Technical Center CJSC | MNT-RTC-ORENBURG | 2010-12-13 | Not announced |
| 109.95.163.0/24 | RIPE | MTS Orenburg branch | AS8580-MNT | 2014-06-09 | Not announced |
| 5.227.122.0/24 | RIPE | MTS Orenburg branch | AS8580-MNT | 2014-12-16 | Announced |
| 5.227.123.0/24 | RIPE | MTS Orenburg branch | AS8580-MNT | 2014-12-16 | Announced |
| 31.29.181.0/24 | RIPE | PJSC "MTS" Orsk | MTU-NOC | 2025-10-13 | Announced |
| 31.29.182.0/23 | RIPE | PJSC "MTS" Orenburg | MTU-NOC | 2025-10-13 | Announced |
| 31.29.188.0/24 | RIPE | PJSC "MTS" Buzuluk | MTU-NOC | 2025-10-13 | Announced |
| 31.29.212.0/23 | RIPE | Orenburg TsuS of Privolzhsky branch of CJS Komstar-Regiony | MNT-RTC-ORENBURG | 2013-01-22 | Announced |
| 31.29.212.0/24 | RIPE | Orenburg TsuS of Privolzhsky branch of ZAO ?Komstar- Regiony? | MNT-RTC-ORENBURG | 2013-01-22 | Announced |
| 31.29.213.0/24 | RIPE | Orenburg TsuS of Privolzhsky branch of CJS Komstar-Regiony | MNT-RTC-ORENBURG | 2013-01-22 | Announced |
| 31.29.214.0/24 | RIPE | Orenburg TsuS of Privolzhsky branch of CJS Komstar-Regiony | MNT-RTC-ORENBURG | 2013-01-22 | Announced |
| 31.29.215.0/24 | RIPE | Orenburg TsuS of Privolzhsky branch of CJS Komstar-Regiony | MNT-RTC-ORENBURG | 2013-01-22 | Announced |
| 62.118.96.0/23 | RIPE | PJSC Mobile TeleSystems Orenburg branch | MTU-NOC | 2024-10-21 | Announced |
| 85.140.126.0/24 | RIPE | MTS Orenburg | MTU-NOC | 2018-08-07 | Announced |
| 91.211.124.0/23 | RIPE | Regional Technical Center CJSC | MNT-RTC-ORENBURG | 2011-09-23 | Announced |
| 91.211.124.0/24 | RIPE | Regional Technical Center CJSC | MNT-RTC-ORENBURG | 2009-02-12 | Announced |
| 91.211.125.0/24 | RIPE | Regional Technical Center CJSC | MNT-RTC-ORENBURG | 2022-07-06 | Announced |
| 91.211.126.0/24 | RIPE | Regional Technical Center CJSC | MNT-RTC-ORENBURG | 2009-02-12 | Announced |
| 91.211.127.0/24 | RIPE | Regional Technical Center CJSC | MNT-RTC-ORENBURG | 2009-02-12 | Announced |
| 92.246.204.0/24 | RIPE | Regional Technical Center CJSC | MNT-RTC-ORENBURG | 2010-10-22 | Announced |
| 92.246.205.0/24 | RIPE | Regional Technical Center CJSC | MNT-RTC-ORENBURG | 2010-10-22 | Announced |
| 92.246.206.0/24 | RIPE | Regional Technical Center CJSC | MNT-RTC-ORENBURG | 2010-10-22 | Announced |
| 92.246.207.0/24 | RIPE | Regional Technical Center CJSC | MNT-RTC-ORENBURG | 2010-10-22 | Announced |
| 92.246.220.0/24 | RIPE | Regional Technical Center CJSC | MNT-RTC-ORENBURG | 2010-10-22 | Announced |
| 92.246.221.0/24 | RIPE | Regional Technical Center CJSC | MNT-RTC-ORENBURG | 2010-10-22 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS48612 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-MTS-ORENBURG | RIPE | Lists AS48612 as a direct member |
AS-MTU | RIPE | Lists AS48612 as a direct member |
AS-MTU2 | RIPE | Lists AS48612 as a direct member |
AS-ROSTELECOM | RIPE | Lists AS48612 as a direct member |
AS-RTC-ORENBURG | RIPE | Lists AS48612 as a direct member |
AS-SUTTK | RIPE | Lists AS48612 as a direct member |
AS-VOLGATELECOM-CUSTOMERS | RIPE | Lists AS48612 as a direct member |
RPKI from rpki-client, validated 2026-10-14 12:07 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-14. Cross-check on bgp.he.net.