AS51104 Remini-Telecom VIP GROUP (S.A.R.L)
🇱🇧Org handle: ORG-VG109-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
3 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)768
Announced (BGP)768
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)0
Listed on the threat map (2026-10-11)
Large hosting providers appear because attackers rent their servers, not necessarily because of the operator.
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 |
Allocated Prefixes
(RIR)4Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.26.85.0/24 | 🇱🇧 LB | RIPENCC | allocated |
| 185.169.7.0/24 | 🇱🇧 LB | RIPENCC | allocated |
| 213.239.155.0/24 | 🇱🇧 LB | RIPENCC | allocated |
| 2a14:af80::/29 | 🇱🇧 LB | RIPENCC | allocated |
All 3 announced prefixes of AS51104 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS51104 hands its own prefixes to: transit providers, or peers at an exchange.
- AS42020LibanTelecom OGERO3
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 AS51104 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/51104Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/51104" | jq