AS212688 AS-INSEC in.sec GmbH
🇩🇪Org handle: ORG-IG210-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
7total
1 IPv46 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)7.2×10²⁴
Announced Prefixes
(BGP)7|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 | |
| Valid | RIPE | 2026-10-10 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 212.24.125.0/24 | 🇩🇪 DE | RIPENCC | allocated |
| 2001:67c:840::/48 | 🇩🇪 DE | RIPENCC | assigned |
| 2a11:28c0::/29 | 🇩🇪 DE | RIPENCC | allocated |
| 2a11:28c0:acab::/48 | 🇩🇪 DE | RIPE | assigned |
All 7 announced prefixes of AS212688 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS212688 hands its own prefixes to: transit providers, or peers at an exchange.
- AS24961MYLOC WIIT7
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 AS212688 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/212688Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/212688" | jq