Autonomous system
AS207366 REDIUM
Unclassified RIPE Content
Summary
Redium
business netherlands content
REDIUM is operated by Redium B.V.
What it's used for
- The address space carries business traffic, identified by the netname
NL-REDIUM-20200115and registrantRedium B.V. - The AS announces 256 IPv4 addresses across 1 prefix with 1 observed neighbour, indicating a small-scale business or content delivery footprint rather than a transit or large access network
- Traffic consists of web and API endpoints for Redium's content services, as the company operates as a content provider in the Netherlands
Notable
- Registrants align with the announcer, with
Redium B.V.listed for the sole prefix91.220.231.0/24 - The address inventory is minimal, consisting of a single /24 block in the Netherlands with no IPv6 prefixes announced
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 |
|---|---|---|
| AS49127 | Asimo Networks B.V. | 58 |
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 1 prefixes · 256 addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| NL | Netherlands | 1 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS207366- Registry name
- REDIUM
- Registrant
- mnt-nl-redium-1
- Abuse contact
- abuse@redium.net
- Registered
- 2020-02-18
- Last changed
- 2020-02-18
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Redium
- Also known as
- Redium
- Network type
- Content
- Scope
- Regional
- Traffic ratio
- Mostly Outbound
- Peering policy
- Open
- IRR as-set
AS-REDIUM- Facilities
- 2 facilities
- Website
- https://www.redium.net
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 · 1 valid, 0 with no ROA
- ROAs
- 3 authorising AS207366
- ASPA
- no ASPA record
- IRR
- 100% registered · 1 of 1 announcements
- Route objects
- 3 naming AS207366
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: 445 networks and 1,817 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