Autonomous system
AS35598 INETCOM
Unclassified RIPE NSP
Summary
INETCOM
transit isp russia inetcom
The AS handle INETCOM is operated by INETCOM CARRIER LLC.
What it's used for
- The address space carries infrastructure for INETCOM, with reverse DNS records pointing to
inetcom.ruand netnames includingORG-IC132-RIPEandRU-INETCOM-CARRIER-20200130. - With 41,472 IPv4 addresses announced across 7 prefixes and 1,744 observed neighbours, the high neighbour-to-address ratio indicates a transit or network service provider role rather than a pure access network.
Notable
- Registrants are consistent with the announcer, primarily listing "Network operations center; INETCOM CARRIER LLC", though two prefixes (
195.209.208.0/20and185.231.56.0/24) are registered to "NOC; DTL LLC" with netnamesDTLandRU-DTL-LLC-20201224. - The inventory consists of a mix of larger blocks like
176.99.128.0/17and smaller /24 allocations, reflecting a diverse address estate typical of a regional carrier.
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 6 exchanges in 6 countries, largest first.
| Exchange | Location | Their address |
|---|---|---|
| DE-CIX Frankfurt | Frankfurt, Germany | 2001:7f8::8b0e:0:1 |
| LINX LON1 | London, United Kingdom | 195.66.224.242 |
| AMS-IX Amsterdam | Amsterdam, Netherlands | 80.249.210.207 |
| France-IX Paris | Paris, France | 37.49.238.75 |
| MSK-IX Moscow | Moscow, Russia | 195.208.209.66 |
| Netnod Sundsvall- Gävle | Sundsvall, Sweden | 194.68.128.51 |
Transit providers
26 upstream, 266 downstream and 401 adjacent networks observed; most-used upstreams first.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-10, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 8 prefixes · 41.22K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 9 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS35598- Registry name
- INETCOM
- Registrant
- INETCOM-CARRIER-MNT
- Abuse contact
- abuse131@inetcom.ru
- Registered
- 2005-09-14
- Last changed
- 2025-12-22
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- INETCOM
- Also known as
- INETCOM LLC
- Network type
- NSP
- Scope
- Europe
- Traffic ratio
- Balanced
- Peering policy
- Selective
- IRR as-set
RIPE::AS-ICNET- Present at
- 13 exchanges
- Facilities
- 16 facilities
- Website
- https://www.inetcom.ru
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, 34 with no ROA
- ROAs
- 1 authorising AS35598
- ASPA
- no ASPA record
- IRR
- 85% registered · 29 of 34 announcements
- Route objects
- 44 naming AS35598
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: 431 networks and 1,775 prefixes, as published 2026-10-11. 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