Autonomous system
AS13118 ASN-YARTELECOM PJSC Rostelecom. Yaroslavl branch
Unclassified RIPE
Summary
Yartelecom
isp telecom business
Twenty-eight announcements averaging under 400 addresses each, with hosts named after a planet.
What it's used for
- The Yaroslavl regional network of a Russian national operator. 11,008 addresses across 28 IPv4 prefixes, three observed BGP neighbours, and no IPv6 announced.
Notable
- Twenty-eight prefixes for 11,008 addresses, most of them
/23s and/24s. - Netnames alternate between
MACROREGIONAL_CENTERandRU-RTK, dated20000906,20080502and20090126. - Two of 18 sampled addresses returned names:
saturn.yaroslavl.ruandmaxim2.yaroslavl.ru. - One prefix could not be looked up in the registry; the fetch failed.
Interesting
- Twenty-eight separate announcements for eleven thousand addresses is close to the worst ratio in this range. Each one occupies a slot in every routing table on the internet, and the pieces are not adjacent, so they cannot be merged. This is what a regional network looks like after two decades of taking whatever blocks were free.
- The two hostnames that answered are individually chosen: a planet and a personal name with a number after it. Hand-named machines are the mark of a network built before automation, and they survive in the zone long after the convention stopped scaling.
MACROREGIONAL_CENTERappears here and on another regional arm of the same parent elsewhere in this range, so the label is the group's internal tier name reused verbatim across the country.
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
1 upstream, 2 downstream and 3 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS12389 | PJSC Rostelecom | 2,542 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-11, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 28 prefixes · 11.01K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 28 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS13118- Registry name
- ASN-YARTELECOM
- Registrant
- PJSC Rostelecom
- Abuse contact
- abuse@rt.ru
- Registered
- 2002-02-06
- Last changed
- 2025-04-15
- Allocation
- allocated
Routing security
RPKI and IRR
- RPKI
- 100% valid · 41 valid, 0 with no ROA
- ROAs
- 37 authorising AS13118
- ASPA
- no ASPA record
- IRR
- 100% registered · 41 of 41 announcements
- Route objects
- 99 naming AS13118
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,768 prefixes, as published 2026-10-12. 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