Autonomous system
AS15640 FPIC-AS
Unclassified RIPE
Summary
MTS
isp telecom mobile business
Half the reverse names write the address with dots, turning it into four extra DNS labels.
What it's used for
- A regional broadband network inside a national operator. Eighty-eight IPv4 prefixes and one IPv6
/32announced from the Russian Federation, sixty-seven thousand addresses, across three observed BGP neighbours.
Notable
- Two naming schemes run side by side under one domain. Some names join two octets with a hyphen; the rest write all four octets separated by dots, which makes each octet its own label in the name.
- A third scheme appears on two addresses, using a different opening word from the rest.
- Every name carries a city label, so the whole sample is placed in one place regardless of scheme.
- Most netnames use the country code, a three-letter predecessor brand and a date, one of them from the first years of the registry; two blocks instead carry a customer-style name with a number.
- Eighty-eight routes leave through three neighbours.
- Eighteen addresses were queried for reverse DNS and twelve returned a name.
Interesting
- Writing an address with dots inside a hostname is legal and quietly awkward. Tools that count labels or match on the domain see a different shape from the hyphenated names in the same zone.
- Eighty-eight routes for sixty-seven thousand addresses means the space arrived in small pieces over many years, and none of it has been consolidated since.
- The naming says these are residential subscribers. That is more than most operators publish, and it makes the whole customer footprint of one city measurable from outside.
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 4 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS8359 | MTS PJSC | 6,645 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-13, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 88 prefixes · 67.07K addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 89 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS15640- Registry name
- FPIC-AS
- Registrant
- MTU-NOC
- Abuse contact
- abuse@mtu.ru
- Registered
- 1970-01-01
- Last changed
- 2022-02-17
- Allocation
- allocated
Routing security
RPKI and IRR
- RPKI
- 0.9% valid · 1 valid, 114 with no ROA
- ROAs
- 1 authorising AS15640
- ASPA
- no ASPA record
- IRR
- 100% registered · 115 of 115 announcements
- Route objects
- 23 naming AS15640
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: 436 networks and 1,771 prefixes, as published 2026-10-13. 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