Autonomous system
AS207133 RUCOMTECH-AS
Unclassified RIPE
Summary
RUCOMTECH LLC
residential isp broadband russia
The AS handle RUCOMTECH-AS is held by RUCOMTECH LLC.
What it's used for
- The address space carries residential broadband traffic, evidenced by reverse DNS entries such as
broadband-185.160.217.255-rucom.techandbroadband-185.250.48.128-rucom.tech. - The network announces 1792 IPv4 addresses across 3 prefixes and 2 IPv6 prefixes, while maintaining 18 observed neighbours; this ratio of address space to peering partners indicates an access network providing last-mile connectivity.
- Traffic from this AS consists of subscriber eyeballs accessing the internet via the operator's broadband infrastructure.
Notable
- Registrants for the announced prefixes are consistent with the AS holder, listing
RUCOMTECH LLCandAbuse-C Rolefor netnamesRU-RUCOMTECH-20160726andRU-RUCOMTECH-PUB. - The inventory is composed of three distinct IPv4 blocks:
185.160.216.0/22,185.250.48.0/23, and185.250.50.0/24, alongside two IPv6 prefixes.
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 Moscow | Moscow, Russia | 195.208.209.67 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-31, 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 · 1.79K addresses IPv6 2 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 5 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS207133- Registry name
- RUCOMTECH-AS
- Registrant
- RUCOMTECH LLC
- Abuse contact
- noc1@rucom.tech
- Registered
- 2016-08-24
- Last changed
- 2024-05-06
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- RUCOMTECH
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
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
- 0% valid · 0 valid, 4 with no ROA
- ROAs
- 0 authorising AS207133
- ASPA
- no ASPA record
- IRR
- 100% registered · 4 of 4 announcements
- Route objects
- 4 naming AS207133
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: 447 networks and 1,845 prefixes, as published 2026-10-31. 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