Autonomous system
AS203493 YACOLO-AS
Hosting RIPE Content
Summary
Yacolo
hosting business russia
The AS handle YACOLO-AS is held by Yacolo.
What it's used for
- The address space carries customer endpoints, evidenced by reverse DNS entries such as
109-248-206-128.customers.yadc.ruand netnames likeYACOLO-COM. - The network announces 1536 IPv4 addresses across 5 prefixes and 6 IPv6 prefixes, with 11 observed neighbours, indicating a small-scale hosting or business access provider rather than a transit carrier.
- Traffic from this AS consists of web and API endpoints for Yacolo's customers, consistent with its role as a content and hosting provider.
Notable
- Registrants for the largest prefixes (
109.248.206.0/23,46.8.251.0/24,194.226.42.0/24) are listed as Egor Timoshenko with the netnameYACOLO-COM, aligning with the AS holder. - Two prefixes (
89.37.193.0/24,194.87.209.0/24) show the netnameInterLIR-Customerwith registrantPonaehali moscow, suggesting leased or historically allocated space from InterLIR. - The inventory is finely subdivided into small /24 blocks and a single /23, typical of a small hosting operation managing individual customer allocations.
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 5 prefixes · 1.54K addresses IPv6 6 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 11 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS203493- Registry name
- YACOLO-AS
- Registrant
- MNT-NETART
- Abuse contact
- abuse@yacolo.com
- Registered
- 2015-12-30
- Last changed
- 2025-01-09
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Yacolo
- Network type
- Content
- Scope
- Not Disclosed
- Traffic ratio
- Mostly Outbound
- Peering policy
- Selective
- IRR as-set
AS-YACOLO- Present at
- 1 exchanges
- Website
- https://yacolo.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
- 64% valid · 7 valid, 4 with no ROA
- ROAs
- 7 authorising AS203493
- ASPA
- no ASPA record
- IRR
- 100% registered · 11 of 11 announcements
- Route objects
- 11 naming AS203493
Reputation
Classification and threat
Hosting Datacenter or cloud provider. Addresses are servers, not people.
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