AS3130 RGNET-SEA RGnet OU
🇪🇪Org handle: ORG-RO47-RIPE
RGnet Seattle Westin
RIPE NCCallocated
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)1.2×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 | - | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 192.83.230.0/24 | 🇪🇪 EE | RIPENCC | assigned |
| 198.180.153.0/24 | 🇪🇪 EE | RIPE | assigned |
All 4 announced prefixes of AS3130 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS3130 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (8)
Networks whose own prefixes AS3130 passes on: usually its customers.
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 AS3130 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/3130Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/3130" | jq