asn.dev

Autonomous system

AS8580 SANDY MTS Nizhniy Novgorod, Russia

Unclassified RIPE

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

Summary

MTS (Nizhny Novgorod, ex-Sandy)

Russia · AI-generated

isp broadband residential legacy

SANDY is one of MTS PJSC's regional fixed-line networks, serving Nizhny Novgorod. The handle preserves Sandy, the local ISP the network grew out of, which passed through Komstar-Regiony before MTS absorbed Komstar in 2011.

What it's used for

  • Regional fixed broadband and associated services in the Nizhny Novgorod area: roughly 45k IPv4 addresses across ~20 prefixes, mostly in 5.227.0.0/16 plus older 194.190.x and 62.220.x blocks.
  • Home-user pools plus carrier-grade NAT for dynamic subscribers; a single observed upstream, so the AS sits behind MTS's own backbone rather than buying transit.

Notable

  • Reverse DNS on the older blocks confirms eyeball use: dynamic home pools named NNN-NN-NNN-NN-dyn.hn.nnov.stream.ru and NAT gateways stream-nat-01 (stream.ru is the local access brand). Most-specific inetnums read MTS-FX-NN-NET, ISP-MTS-Volga and "Mobile TeleSystems PJSC, Nizhny Novgorod region" — an MTS fixed-access assignment, not the mobile core.
  • The newer 5.227.0.0/16 space returned few PTRs when sampled, but the lineage and the resolving older blocks both point to consumer broadband.

Interesting

  • MTS is far better known as a mobile operator, but this AS is fixed-line. MTS's mobile network is numbered elsewhere, so an address here should not be read as a cellular one.

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

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.

ASNetworkPaths seen
AS8359MTS PJSC1,146

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

Shape and geography

IPv4 17 prefixes · 41.22K addresses IPv6 0 prefixes

CountryNamePrefixes
RURussian Federation17

Registry

Allocation record

RIPE · via Atlas (registry + RDAP)
Registry
RIPE
Handle
AS8580
Registry name
SANDY
Registrant
AS8580-MNT
Abuse contact
abuse@mtu.ru
Registered
1970-01-01
Last changed
2022-01-14
Allocation
allocated

Routing security

RPKI and IRR

Full detail
RPKI
0% valid · 0 valid, 20 with no ROA
ROAs
0 authorising AS8580
ASPA
no ASPA record
IRR
100% registered · 20 of 20 announcements
Route objects
13 naming AS8580

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

Cross-check