AS28824 ASN-EMPSECURE EMP SECURE AS
🇳🇴Org handle: ORG-HA11-RIPE
EMP Secure AS
RIPE NCCallocated
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)17,408
Announced (BGP)17,408
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)4|
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 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 46.250.192.0/19 | 🇳🇴 NO | RIPENCC | allocated |
| 185.115.244.0/22 | 🇳🇴 NO | RIPENCC | allocated |
| 213.162.224.0/19 | 🇳🇴 NO | RIPENCC | allocated |
| 2001:4da8::/32 | 🇳🇴 NO | RIPENCC | allocated |
All 4 announced prefixes of AS28824 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS28824 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (2)
Networks whose own prefixes AS28824 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS28824 in the transit part of AS paths: peers, providers or customers.
- AS6939Hurricane Electric1
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 AS28824 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/28824Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/28824" | jq