Autonomous system
AS25085 ALUE-NET ALUE LTD
Unclassified RIPE Network Services
Summary
Alue Network
transit ipv6 uk network
The AS handle DMITRY-AS is held by Alue Network (ALUE LTD).
What it's used for
- The address space consists entirely of IPv6 prefixes, including
2a0f:1cc5:4001::/48and2a12:cb41:1101::/48, with no IPv4 addresses announced. - The network announces 8 IPv6 prefixes against 14 observed neighbours, a ratio that suggests a transit or interconnection role rather than a large-scale access network.
Notable
- The RDAP registrant lookup was unavailable, so registrant details could not be verified against the announcer.
- The inventory is composed of eight distinct IPv6 blocks, all located in the United Kingdom.
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
9 upstream, 2 downstream and 11 adjacent networks observed; most-used upstreams first.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-11-01, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 0 prefixes · 0 addresses IPv6 9 prefixes
| Country | Name | Prefixes |
|---|---|---|
| GB | United Kingdom | 9 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS25085- Registry name
- ALUE-NET
- Registrant
- ALUE-MNT
- Abuse contact
- abuse@alue.uk
- Registered
- 2013-10-11
- Last changed
- 2026-08-08
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- ALUE NETWORK
- Also known as
- ALUE NETWORK
- Network type
- Network Services
- Scope
- Global
- Traffic ratio
- Balanced
- Peering policy
- Open
- IRR as-set
RADB::AS-ALUE- Present at
- 8 exchanges
- Facilities
- 1 facilities
- Website
- https://bgp.tn/
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 · 12 valid, 0 with no ROA
- ROAs
- 4 authorising AS25085
- ASPA
- no ASPA record
- IRR
- 100% registered · 12 of 12 announcements
- Route objects
- 19 naming AS25085
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: 447 networks and 1,843 prefixes, as published 2026-11-02. 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