Autonomous system
AS9177 ORG-RTL21-RIPE RTA Telecom Ltd.
Unclassified RIPE NSP
Summary
RTA Telecom Ltd.
isp legacy
MZRTA-AS is held by RTA Telecom Ltd., a regional ISP serving the town of Mezhdurechensk in Russia's Kemerovo region.
What it's used for
The AS announces three IPv4 prefixes (~10,240 addresses) with 8 observed neighbours and two upstreams. Registry objects name the space MZRTA.subscribers / mezhdurechensk network, indicating end-user access rather than backbone or datacentre space. No PTRs were returned on the addresses sampled, so the split between residential and small-business subscribers can't be pinned down from rDNS alone.
Notable
- RIPE-registered, first seen in BGP in 2000; a small-town access provider by footprint.
- The modest address count paired with a handful of neighbours fits a local eyeball ISP buying transit and peering regionally.
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
Internet exchanges
Recorded at 1 exchange in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| MSK-IX Novosibirsk | Novosibirsk, Russia | 193.232.87.84 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-11-02, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 3 prefixes · 10.24K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 3 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS9177- Registry name
- MZRTA-AS
- Registrant
- RTA Telecom Ltd.
- Abuse contact
- support@mzrta.ru
- Registered
- 2008-09-15
- Last changed
- 2026-04-07
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Mezhdurechensk factory of radio equipment repair, Ltd
- Network type
- NSP
- Scope
- Regional
- Traffic ratio
- Balanced
- Peering policy
- Open
- IRR as-set
AS9177
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 100% valid · 3 valid, 0 with no ROA
- ROAs
- 3 authorising AS9177
- ASPA
- no ASPA record
- IRR
- 100% registered · 3 of 3 announcements
- Route objects
- 3 naming AS9177
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: 449 networks and 1,846 prefixes, as published 2026-11-03. 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