Autonomous system
AS51219 K2_INT
Unclassified RIPE
Summary
K2 Cloud
cloud hosting enterprise russia
The AS handle K2_INT is held by K2 Integration JSC, operating as K2 Cloud.
What it's used for
- The address space carries cloud infrastructure, evidenced by reverse DNS entries such as
c2-5-35-74-0.elastic.k2.cloudandc2-91-184-234-0.elastic.k2.cloud. - The network announces 18,176 IPv4 addresses across 22 prefixes and 1 IPv6 prefix, with 35 observed neighbours, indicating a hosting or cloud provider role rather than a transit or access network.
- Traffic from this AS consists of cloud service endpoints and elastic compute resources for K2 Cloud's customers.
Notable
- Registrants for the majority of prefixes are "Network Operation Centre; K2 Integration JSC; Abuse-C Role", consistent with the announcer.
- Two prefixes (5.8.180.0/23 and 81.23.10.0/23) list "CROC DC operations group; MegaFon PJSC - Internet Service Network Operation Center" as registrants, suggesting leased or historically allocated space.
- One prefix (93.189.226.0/23) is registered to "Mikhail Tonkonog" under netname
RU-IPMAGNAT-20120810, which does not align with the primary K2 Integration registrant. - The inventory is finely subdivided into /21, /22, /23, and /24 blocks, typical of an internal corporate or cloud estate.
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.
Transit providers
12 upstream, 1 downstream and 20 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-14, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 21 prefixes · 18.18K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 22 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS51219- Registry name
- K2_INT
- Registrant
- lir-ru-k2integration-1-MNT
- Abuse contact
- info@k2int.ru
- Registered
- 2010-06-24
- Last changed
- 2025-03-12
- Allocation
- allocated
Routing security
RPKI and IRR
- RPKI
- 16% valid · 8 valid, 42 with no ROA
- ROAs
- 9 authorising AS51219
- ASPA
- no ASPA record
- IRR
- 100% registered · 50 of 50 announcements
- Route objects
- 53 naming AS51219
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: 442 networks and 1,773 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