AS35382 GLESYS-FI-2 Glesys AB
🇸🇪Org handle: ORG-GISA2-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)2,560
Announced (BGP)2,560
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 77.240.18.0/23 | 🇫🇮 FI | RIPENCC | allocated |
| 77.240.20.0/22 | 🇫🇮 FI | RIPENCC | allocated |
| 185.58.32.0/22 | 🇫🇮 FI | RIPENCC | allocated |
| 2a02:5de0::/32 | 🇫🇮 FI | RIPENCC | allocated |
All 4 announced prefixes of AS35382 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS35382 hands its own prefixes to: transit providers, or peers at an exchange.
- AS16302SUOMICOMMUNICATIONS Suomi Communications Oy4
Transfer History
Registry transfers of AS35382 between organisations.
- AS35382Transfer ·
- AS35382M&A ·
ASPA
No ASPA
Abuse Contact
+31205354444
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 AS35382 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/35382Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/35382" | jq