asn.dev

Autonomous system

AS48612 RTC-ORENBURG-AS MTS Orenburg

Unclassified RIPE

IPv4 addresses 7.17K 12 prefixes
IPv6 prefixes 0 counted as prefixes, not addresses
Countries 1 mostly RU
Exchanges 0 recorded by PCH
Upstreams 1 1 downstream
Flagged prefixes 0 none

Summary

MTS Orenburg

Russian Federation · AI-generated

mobile residential access russia

RTC-ORENBURG-AS is operated by MTS PJSC.

What it's used for

  • The address space carries mobile and fixed access traffic, evidenced by netnames such as RTC-ORENBURG-NET, CMST-ORENBURG-20130115, and RU-MTU-20080422.
  • The AS announces 7168 IPv4 addresses across 12 prefixes with only 2 observed neighbours, a ratio characteristic of an access network rather than a transit provider.
  • Traffic from this AS consists of subscriber eyeballs and mobile data sessions for MTS customers in the Orenburg region and surrounding areas.

Notable

  • Registrants consistently identify MTS PJSC or its operational units, including MTS backbone NOC and MTU Abuse-c Bender, aligning with the announcer.
  • Some prefixes, such as 31.29.182.0/23 and 31.29.181.0/24, list Comstar Volga Arzamas as a registrant, indicating historical or regional operational segmentation within the MTS estate.
  • The inventory is composed of a mix of /22, /23, and /24 blocks, with no IPv6 prefixes currently announced.

This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.

Interconnection

Peering at a glance

Full topology · Graph

Internet exchanges

No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.

Transit providers

1 upstream, 1 downstream and 2 adjacent networks observed; most-used upstreams first.

ASNetworkPaths seen
AS8359MTS PJSC1,669

Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-13, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.

Address space

Summary

Shape and geography

IPv4 12 prefixes · 7.17K addresses IPv6 0 prefixes

CountryNamePrefixes
RURussian Federation12

Registry

Allocation record

RIPE · via Atlas (registry + RDAP)
Registry
RIPE
Handle
AS48612
Registry name
RTC-ORENBURG-AS
Registrant
MTU-NOC
Abuse contact
abuse@mtu.ru
Registered
2008-12-17
Last changed
2018-08-07
Allocation
allocated

Routing security

RPKI and IRR

Full detail
RPKI
6% valid · 2 valid, 27 with no ROA 2 RPKI-invalid
ROAs
2 authorising AS48612
ASPA
no ASPA record
IRR
97% registered · 30 of 31 announcements
Route objects
29 naming AS48612

Reputation

Classification and threat

Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.

Spamhaus DROP

Not on ASN-DROP The network as a whole is not listed.

No DROP prefixes None of its announced space is on the DROP prefix list.

Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 436 networks and 1,771 prefixes, as published 2026-10-13. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.

FBI IC3

No IC3 indicators Nothing from the FBI IC3 feed.

IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.

Elsewhere

Cross-check