AS39647 REDHOSTING-AS Enreach Netherlands B.V.
π³π±Org handle: ORG-WRGB1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
66total
61 IPv45 IPv6
IPv4 Addresses
Allocated (RIR)121,088
Announced (BGP)123,648
IPv6 Addresses
Allocated (RIR)7.1Γ10Β²βΉ
Announced (BGP)9.5Γ10Β²βΉ
Prefix Limit (IPv4)
200
Prefix Limit (IPv6)
20
Country
π³π± NLRIR
RIPE NCCStatus
allocated
Allocated
2006-03-31
Announced Prefixes
(BGP)66|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
80.85.175.0/24MOAS | Valid | RIPE | 2026-10-11 |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
1-10 of 66
1 / 7
Allocated Prefixes
(RIR)59Prefix | Country | RIR | Status |
|---|---|---|---|
| 5.178.32.0/21 | π³π± NL | RIPENCC | allocated |
| 37.152.8.0/21 | π³π± NL | RIPENCC | allocated |
| 45.10.228.0/22 | π³π± NL | RIPENCC | allocated |
| 45.88.48.0/22 | π³π± NL | RIPENCC | allocated |
| 46.102.224.0/21 | π³π± NL | RIPENCC | allocated |
| 46.231.80.0/21 | π³π± NL | RIPENCC | allocated |
| 62.212.128.0/19 | π³π± NL | RIPENCC | allocated |
| 80.85.175.0/24 | π³π± NL | RIPE | assigned |
| 81.28.80.0/20 | π³π± NL | RIPENCC | allocated |
| 84.243.192.0/18 | π³π± NL | RIPENCC | allocated |
1-10 of 59
1 / 6
All 66 announced prefixes of AS39647 β
BGP Neighbours
(seen in AS paths)Upstreams (7)
Networks AS39647 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (4)
Networks whose own prefixes AS39647 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS39647 in the transit part of AS paths: peers, providers or customers.
- AS20562OPEN PEERING Broadband Hosting B.V1
ASPA
No ASPA
Abuse Contact
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS39647 should publish an ASPA object
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/39647Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/39647" | jq