AS35261 DYNAMIC-AS Core Telecom S.R.L.
🇷🇴Org handle: ORG-CTS68-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
3 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)3,840
Announced (BGP)1,536
IPv6 Addresses
Allocated (RIR)7.9×10²⁸
Announced (BGP)0
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)7Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.138.64.0/22 | 🇷🇴 RO | RIPENCC | allocated |
| 45.138.64.0/23 | 🇷🇴 RO | RIPE | assigned |
| 45.138.66.0/23 | 🇷🇴 RO | RIPE | assigned |
| 93.189.124.0/22 | 🇷🇴 RO | RIPENCC | allocated |
| 185.62.231.0/24 | 🇷🇴 RO | RIPENCC | allocated |
| 193.239.212.0/23 | 🇷🇴 RO | RIPENCC | assigned |
| 2a09:100::/32 | 🇷🇴 RO | RIPENCC | allocated |
All 3 announced prefixes of AS35261 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS35261 hands its own prefixes to: transit providers, or peers at an exchange.
- AS49909DIRECT ONE Direct One3
Transfer History
Registry transfers of AS35261 between organisations.
- AS35261Transfer ·
- AS35261Transfer ·
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 AS35261 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/35261Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/35261" | jq