Autonomous system
AS13257 POLARCOM-AS Murmansk
Unclassified RIPE
Summary
Polarcom / Vimpelcom
isp telecom business
Five brand names for one network, spread across the holder field, the handle, the netnames and the DNS.
What it's used for
- A regional access network in Murmansk. 14,336 addresses across three IPv4 prefixes, one observed BGP neighbour, and no IPv6 announced.
Notable
- The registry holder is a national mobile operator; the AS handle is
POLARCOM-AS Murmansk. - All three netnames use a fourth name:
RU-SOVINTEL-20000427,RU-SOVINTEL-20070502andRU-SOVINTEL-20100416. - Sampled names are
hsrp-int.mtf.ruand77-245-203-254.polarnet.ru, two more domains again. - One observed neighbour against 14,336 addresses.
Interesting
- Every layer of this record preserves a different era's name. The registry knows the current parent, the AS handle keeps the regional operator, the netnames keep the company that received the allocations, and the DNS keeps two more. None of them was wrong when it was written, and nothing ever goes back to reconcile them.
- The eight-digit netname dates run from 2000 to 2010 under a brand that the parent company no longer uses, so the label outlived the business it named by at least the length of that span.
- One of the two published names is a router interface serving a redundancy protocol rather than a customer address. Somebody named the machine for its job, and that name is now the only public description of that address.
- A single neighbour for a network this size means the archive sees one way in and out.
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 |
|---|---|---|
| AS3216 | PJSC "Vimpelcom" | 531 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-11, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 3 prefixes · 14.34K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| RU | Russian Federation | 3 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS13257- Registry name
- POLARCOM-AS
- Registrant
- PJSC "Vimpelcom"
- Abuse contact
- abuse-b2b@beeline.ru
- Registered
- 2002-06-06
- Last changed
- 2017-02-09
- Allocation
- allocated
Routing security
RPKI and IRR
- RPKI
- 0% valid · 0 valid, 9 with no ROA
- ROAs
- 0 authorising AS13257
- ASPA
- no ASPA record
- IRR
- 100% registered · 9 of 9 announcements
- Route objects
- 19 naming AS13257
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,768 prefixes, as published 2026-10-12. 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