asn.dev

Autonomous system

AS47528 RU-PITER-IX-VKZ Piter-IX Co. Ltd.

Unclassified RIPE Route Server

IPv4 addresses 256 1 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

Piter-IX Vladikavkaz

Russian Federation · AI-generated

ix route-server russia

RU-PITER-IX-VDV is operated by Piter-IX Co. Ltd.

What it's used for

  • The space carries routing infrastructure for the Piter-IX exchange, specifically for the Vladikavkaz location, as indicated by the AS handle and PeeringDB classification.
  • The AS announces a single IPv4 prefix, 31.184.237.0/24, comprising 256 addresses, with 0 IPv6 prefixes.
  • With only 1 observed neighbour, the network functions as a dedicated route server or peering point rather than a transit provider or access network.

Notable

  • The RDAP registrant for the announced prefix is TT; PINDC Support and NOC Teams with netname TRANSROUTE, which differs from the AS holder RU-PITER-IX-VKZ Piter-IX Co. Ltd., suggesting the address space may be leased or managed by a separate technical team within the organization.
  • The address inventory consists of a single /24 block, typical for a specific route server or exchange point infrastructure rather than a large-scale ISP.

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
AS44050Petersburg Internet Network ltd.66

Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-11-15, 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 1 prefixes · 256 addresses IPv6 0 prefixes

CountryNamePrefixes
RURussian Federation1

Registry

Allocation record

RIPE · via Atlas (registry + RDAP)
Registry
RIPE
Handle
AS47528
Registry name
RU-PITER-IX-VKZ
Registrant
MNT-PINSUPPORT
Abuse contact
abuse@piter-ix.ru
Registered
2018-07-10
Last changed
2026-05-06
Allocation
allocated

Declared

PeeringDB profile

self-reported
Name
PITER-IX Vladikavkaz Route Servers
Network type
Route Server
Scope
Europe
Traffic ratio
Not Disclosed
Peering policy
Open
IRR as-set
AS47528:AS-PITER-IX-VKZ
Present at
1 exchanges
Website
https://piter-ix.ru/

PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.

Routing security

RPKI and IRR

Full detail
RPKI
100% valid · 1 valid, 0 with no ROA
ROAs
1 authorising AS47528
ASPA
no ASPA record
IRR
100% registered · 1 of 1 announcements
Route objects
2 naming AS47528

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: 454 networks and 1,849 prefixes, as published 2026-11-14. 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