AS216067 AS216067 BHS Solutions GmbH
🇩🇪Org handle: ORG-BSG327-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
4 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,280
Announced (BGP)1,280
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
104.167.26.0/23MOAS | Valid | RIPE | 2026-10-10 |
| Valid | RIPE | 2026-10-10 | |
185.188.16.0/24MOAS | Valid | RIPE | 2026-10-10 |
| Valid | RIPE | 2026-10-10 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 104.167.26.0/23 | 🇩🇪 DE | RIPENCC | allocated |
| 176.116.4.0/24 | 🇩🇪 DE | RIPENCC | allocated |
| 185.188.16.0/24 | 🇩🇪 DE | RIPENCC | allocated |
| 217.114.35.0/24 | 🇩🇪 DE | RIPENCC | allocated |
All 4 announced prefixes of AS216067 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS216067 hands its own prefixes to: transit providers, or peers at an exchange.
- AS33891CORE BACKBONE Core Backbone4
Other adjacent networks (1)
Adjacent to AS216067 in the transit part of AS paths: peers, providers or customers.
- AS49666TIC GW Telecommunication Infrastructure Company89
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 AS216067 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/216067Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/216067" | jq