AS201933 AS4NET 4net Technologies Ltd
🇬🇧Org handle: ORG-TL906-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
5total
4 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)2,304
Announced (BGP)2,048
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Announced Prefixes
(BGP)5|
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 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.90.42.0/24 | 🇬🇧 GB | RIPENCC | allocated |
| 80.247.222.0/23 | 🇬🇧 GB | RIPENCC | allocated |
| 91.193.116.0/22 | 🇬🇧 GB | RIPENCC | allocated |
| 213.193.250.0/23 | 🇬🇧 GB | RIPENCC | allocated |
| 2a06:40c0::/29 | 🇬🇧 GB | RIPENCC | allocated |
All 5 announced prefixes of AS201933 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS201933 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (4)
Networks whose own prefixes AS201933 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS201933 in the transit part of AS paths: peers, providers or customers.
- AS3223VOXILITY LLP2
Transfer History
Registry transfers of AS201933 between organisations.
- AS201933Transfer ·
- AS201933Transfer ·
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 AS201933 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/201933Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/201933" | jq