AS207535 SONEXTIS SONEXTIS GmbH
🇩🇪Org handle: ORG-SG310-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)768
Announced (BGP)768
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)7.9×10²⁸
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 5.154.180.0/24 | 🇩🇪 DE | RIPENCC | allocated |
| 91.192.11.0/24 | 🇩🇪 DE | RIPENCC | allocated |
| 91.250.242.0/24 | 🇩🇪 DE | RIPENCC | allocated |
| 2a10:ab40::/32 | 🇩🇪 DE | RIPENCC | allocated |
All 4 announced prefixes of AS207535 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS207535 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (1)
Networks whose own prefixes AS207535 passes on: usually its customers.
- AS201395IT TIM IT TIM D.O.O4
Other adjacent networks (1)
Adjacent to AS207535 in the transit part of AS paths: peers, providers or customers.
- AS41110DSLmobil1
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 AS207535 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/207535Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/207535" | jq