Autonomous system
AS31531 JUPITER-AS
Unclassified RIPE
Summary
Jupiter
residential isp ukraine dynamic
JUPITER-AS is operated by TOV Point, a Ukrainian internet service provider.
What it's used for
- The address space carries dynamic residential traffic, evidenced by reverse DNS entries such as
dynamic.jupiter.ru.netanddynamic-190.berdyansk.net. - The AS announces 1536 IPv4 addresses across 4 prefixes and maintains 2 observed neighbours, a ratio indicative of an access network rather than a transit provider.
Notable
- Registrants include "Private Enterprise 'Fivestars'" for the 185.248.128.0/23 and 194.31.168.0/23 blocks, while the 193.16.101.0/24 and 194.31.170.0/24 blocks are registered to "TOV Point" and "JUPITER" respectively.
- The operator rebranded as Jupiter in 2011, transitioning from its previous identity to the current name used in its reverse DNS and public presence.
- The inventory consists of four IPv4 prefixes with no IPv6 announcements, reflecting a legacy IPv4-only deployment.
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.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-26, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 4 prefixes · 1.54K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| UA | Ukraine | 4 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS31531- Registry name
- JUPITER-AS
- Registrant
- TOV Point
- Abuse contact
- admin@jupiter.ru.net
- Registered
- 2004-06-07
- Last changed
- 2023-02-28
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- TOV Point
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
- Website
- https://point.zp.ua
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
- RPKI
- 100% valid · 5 valid, 0 with no ROA
- ROAs
- 6 authorising AS31531
- ASPA
- no ASPA record
- IRR
- 100% registered · 5 of 5 announcements
- Route objects
- 7 naming AS31531
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: 446 networks and 1,852 prefixes, as published 2026-10-27. 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