Autonomous system
AS12688 BAIKALTRANSTELECOM Irkutsk, Russia
Unclassified RIPE
Summary
TransTeleCom Baikal
isp telecom
35,840 addresses in Irkutsk, allocated in five separate applications across two years, reached through one neighbour.
What it's used for
- Regional access for a branch of a Russian national carrier. 35,840 addresses in seven IPv4 prefixes, one observed BGP neighbour, and no IPv6 announced.
Notable
- Five blocks carry dated netnames from the same holder:
RU-TRANSTELECOM-20110322,20110627,20111124,20120125and20120914, with20121214on a sixth. 141.105.48.0/21is netnameRU-BTTK, registered to SibTransTelecom through a contact namedGIS KTTK Sibir.- The technical contact on the rest is
TTC NOC. - Eighteen sampled addresses were queried and none returned a name.
Interesting
- Six allocations in twenty-one months is the rhythm of a network that grew steadily and asked for more space each time it ran out. Registries stopped handing out large blocks well before 2011, so an operator needing 35,840 addresses had to collect them a
/19at a time and announce each one separately, which is why the routing table shows seven entries where one would have done a decade earlier. - A single observed neighbour against that much address space marks this as a branch rather than an independent operator. Everything reaches the rest of the Internet through the parent company, and the branch exists in routing terms only because someone wanted its region administratively separate.
BTTKandKTTKdiffer by one letter and name two different regional subsidiaries of the same group. Corporate acronyms make poor identifiers, and the registry preserves every variant anyone ever filed.
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, 0 downstream and 1 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS15774 | Limited Liability Company "TTK-Svyaz" | 413 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-10, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 7 prefixes · 35.84K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 7 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS12688- Registry name
- BAIKALTRANSTELECOM
- Registrant
- Joint Stock Company TransTeleCom
- Abuse contact
- abuse@ttk.ru
- Registered
- 2011-03-23
- Last changed
- 2025-01-13
- Allocation
- allocated
Routing security
RPKI and IRR
- RPKI
- 100% valid · 7 valid, 0 with no ROA
- ROAs
- 8 authorising AS12688
- ASPA
- no ASPA record
- IRR
- 100% registered · 7 of 7 announcements
- Route objects
- 19 naming AS12688
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,775 prefixes, as published 2026-10-11. 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