AS206049 COMMUNICATE Communicate Technology LTD
🇬🇧Org handle: ORG-CTP6-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
3 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)1,536
Announced (BGP)1,536
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)3.1×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)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.197.56.0/22 | 🇬🇧 GB | RIPENCC | allocated |
| 212.11.67.0/24 | 🇬🇧 GB | RIPENCC | allocated |
| 212.11.76.0/24 | 🇬🇧 GB | RIPENCC | allocated |
All 4 announced prefixes of AS206049 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS206049 hands its own prefixes to: transit providers, or peers at an exchange.
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 AS206049 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/206049Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/206049" | jq