Autonomous system
AS211134 AS-INTERSYS
Unclassified RIPE
Summary
Intersys Ltd
telecom isp russia
AS-INTERSYS is held by Intersys Ltd.
What it's used for
- The address space carries residential and business connectivity, evidenced by the
union-telreverse DNS entries and theRU-SEVEREN-20180405netname associated with JSC "Severen-Telecom". - The AS announces 1536 IPv4 addresses across 3 prefixes and maintains 15 observed neighbours, a ratio consistent with a regional access or transit provider rather than a large-scale backbone.
- Traffic from this AS consists of subscriber eyeballs and local business connections within the Russian Federation, supported by the
union-teldomain references in the reverse DNS sample.
Notable
- Registrants include JSC "Severen-Telecom" for the largest block and
Union-tel.rusupport staff for theIntersysnetname, indicating a multi-entity operational structure or leased space arrangements. - The inventory consists of three distinct IPv4 prefixes, with the largest being a /22 block and two /24 blocks, all located in the Russian Federation.
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
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-25, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 2 prefixes · 512 addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 2 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS211134- Registry name
- AS-Intersys
- Registrant
- Intersys Ltd
- Abuse contact
- abuse@inter-sys.ru
- Registered
- 2021-06-21
- Last changed
- 2025-07-08
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Intersys
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
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
- 33% valid · 1 valid, 1 with no ROA 1 RPKI-invalid
- ROAs
- 1 authorising AS211134
- ASPA
- no ASPA record
- IRR
- 67% registered · 2 of 3 announcements 1 other origin
- Route objects
- 2 naming AS211134
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: 443 networks and 1,779 prefixes, as published 2026-10-24. 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