AS200804 NSS OU NORTHSIDE SOLUTIONS
🇪🇪Org handle: ORG-ONS8-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)2,048
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)0
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-08 | |
| Valid | RIPE | 2026-10-08 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.94.112.0/22 | 🇪🇪 EE | RIPENCC | allocated |
| 185.94.112.0/23 | 🇪🇪 EE | RIPE | assigned |
| 185.94.114.0/23 | 🇪🇪 EE | RIPE | assigned |
| 2a04:c280::/29 | 🇪🇪 EE | RIPENCC | allocated |
All 2 announced prefixes of AS200804 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS200804 hands its own prefixes to: transit providers, or peers at an exchange.
- AS3327CITIC Telecom CPC Netherlands B.V2
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 AS200804 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/200804Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/200804" | jq