AS201633 perfectsense Perfect Sense AB
🇸🇪Org handle: ORG-PSA163-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
2 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)2.4×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)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 193.33.156.0/24 | 🇸🇪 SE | RIPENCC | allocated |
| 206.225.17.0/24 | 🇸🇪 SE | RIPENCC | allocated |
| 2a12:d4c0::/29 | 🇸🇪 SE | RIPENCC | allocated |
| 2a12:d4c0:b00b::/48 | 🇸🇪 SE | RIPE | assigned |
| 2a12:d4c0:beef::/48 | 🇸🇪 SE | RIPE | assigned |
All 4 announced prefixes of AS201633 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS201633 hands its own prefixes to: transit providers, or peers at an exchange.
- AS35661VIRTUASYS EU VIRTUA SYSTEMS SAS4
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 AS201633 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/201633Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/201633" | jq