Autonomous system
AS198669 KNET-AS www: knet-tele.com support: tech@knet-tele.com
Unclassified RIPE NSP
Summary
KNET TELECOM
isp regional russia telecom
KNET-AS is operated by KNET TELECOM Ltd.
What it's used for
- The address space carries subscriber traffic, evidenced by reverse DNS entries such as
128-86-195-91.knet-tele.comand netnamesRU-KNET-TELECOMandORG-KNET9-RIPE. - The network announces 1280 IPv4 addresses across 3 prefixes and maintains 2 observed neighbours, a ratio consistent with a regional access provider rather than a transit hub.
- As a telecommunications company established in 2002, the traffic consists of residential and business subscriber eyeballs within its regional scope.
Notable
- Registrants for all announced prefixes are consistent with the announcer, listing
KNET TELECOM LtdorKNET TELECOM LTD.. - The operator is also known as YALTASTAR according to peering records.
- The inventory consists of three distinct IPv4 blocks: 91.195.86.0/23, 91.238.74.0/23, and 91.220.124.0/24.
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-29, 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.28K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 3 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS198669- Registry name
- KNET-AS
- Registrant
- KNETTELECOM-MNT
- Abuse contact
- admin@knet-tele.com
- Registered
- 2012-04-10
- Last changed
- 2026-04-07
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- KNET TELECOM Ltd.
- Also known as
- YALTASTAR
- Network type
- NSP
- Scope
- Regional
- Traffic ratio
- Mostly Inbound
- Peering policy
- Open
- IRR as-set
AS-KNET- Present at
- 1 exchanges
- Website
- http://knet-tele.com
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, 3 with no ROA
- ROAs
- 0 authorising AS198669
- ASPA
- no ASPA record
- IRR
- 100% registered · 3 of 3 announcements
- Route objects
- 3 naming AS198669
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: 448 networks and 1,849 prefixes, as published 2026-10-29. 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