asn.dev

Autonomous system

AS8629 MCNTT-AS MCNTT Autonomous System

Unclassified APNIC

IPv4 addresses 12.29K 2 prefixes
IPv6 prefixes 0 counted as prefixes, not addresses
Countries 1 mostly RU
Exchanges 1 recorded by PCH
Upstreams 5 0 downstream
Flagged prefixes 0 none

Summary

MC NTT (Moscow Center of New Telecommunication Technologies)

Russia · AI-generated

isp enterprise legacy

MCNTT-AS — Moscow Center of New Telecommunication Technologies (МЦ НТТ), a Moscow telecom operator founded in the mid-1990s and now part of the Rostelecom group, where it trades as Rostelecom Contact Center.

What it's used for

  • Corporate connectivity and hosted services in Moscow. About 12,000 IPv4 addresses in two prefixes, with a dozen BGP neighbours.
  • rDNS is entirely under ntt.ru and mostly generated: cN-M.ntt.ru across both blocks, plus named infrastructure (gw-2, smtpq) and legacy access servers (dialup-NN-as-N.ntt.ru).
  • The RIPE objects show the space carved into assignments for named business customers — a bank, a telecom company, a media firm — alongside the operator's own blocks and one marked as an end-user cloud segment.

Notable

  • ntt.ru is not NTT. The domain belongs to this Moscow operator and has nothing to do with the Japanese carrier. A name- or rDNS-keyword match here gets both the company and the country wrong.
  • The customer assignments are corporate, and there are no dynamic or PPPoE subscriber pools. The dialup- hosts are the operator's own access concentrators, a leftover from the 1990s, not a mass-market subscriber base.

Interesting

  • The company's centre of gravity has moved a long way from its name. Its main business today is outsourced contact-centre operations for government and corporate clients, run out of nineteen Russian cities. The AS and the ntt.ru domain are what remain of the original telecom operator.

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

Full topology · Graph

Internet exchanges

Recorded at 1 exchange in 1 country, largest first.

ExchangeLocationTheir address
MSK-IX MoscowMoscow, Russia195.208.208.112

Transit providers

5 upstream, 0 downstream and 5 adjacent networks observed; most-used upstreams first.

ASNetworkPaths seen
AS42610PJSC Rostelecom62
AS12389PJSC Rostelecom40
AS3216PJSC "Vimpelcom"20
AS24482SG.GS1
AS49673Truenetwork LLC1

Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-22, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.

Address space

Summary

Shape and geography

IPv4 2 prefixes · 12.29K addresses IPv6 0 prefixes

CountryNamePrefixes
RURussian Federation2

Registry

Allocation record

APNIC · via Atlas (registry + RDAP)
Registry
APNIC
Handle
AS8629
Registry name
MCNTT-AS
Registrant
MCNTT-MNT
Abuse contact
paul@ntt.ru
Registered
2002-07-18
Last changed
2017-11-15
Allocation
allocated

Routing security

RPKI and IRR

Full detail
RPKI
50% valid · 1 valid, 1 with no ROA
ROAs
1 authorising AS8629
ASPA
no ASPA record
IRR
50% registered · 1 of 2 announcements
Route objects
18 naming AS8629

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,779 prefixes, as published 2026-10-23. 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

Cross-check