AS44134 BOLIGNET-AS BOLIGNET A/S
🇩🇰Org handle: ORG-BA218-RIPE
- - - Transit - - -
RIPE NCCallocated
Announced Prefixes (BGP)
3total
2 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)8,192
Announced (BGP)8,192
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 79.142.224.0/20 | 🇩🇰 DK | RIPENCC | allocated |
| 217.71.0.0/20 | 🇩🇰 DK | RIPENCC | allocated |
| 2a02:2190::/29 | 🇩🇰 DK | RIPENCC | allocated |
All 3 announced prefixes of AS44134 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS44134 hands its own prefixes to: transit providers, or peers at an exchange.
- AS31027GlobalConnect AS31027 GlobalConnect A/S3
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 AS44134 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/44134Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/44134" | jq