AS207133 RUCOMTECH-AS RUCOMTECH LLC
🇷🇺Org handle: ORG-RL293-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
2 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)2,048
Announced (BGP)2,048
IPv6 Addresses
Allocated (RIR)1.3×10³⁰
Announced (BGP)7.1×10²⁹
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)5Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.160.216.0/22 | 🇷🇺 RU | RIPENCC | allocated |
| 185.250.48.0/22 | 🇷🇺 RU | RIPENCC | allocated |
| 2a04:2bc0::/29 | 🇷🇺 RU | RIPENCC | allocated |
| 2a04:2bc0::/32 | 🇷🇺 RU | RIPE | assigned |
| 2a0c:78c0::/29 | 🇷🇺 RU | RIPENCC | allocated |
All 4 announced prefixes of AS207133 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS207133 hands its own prefixes to: transit providers, or peers at an exchange.
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 AS207133 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/207133Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/207133" | jq