AS57513 MIC1-ALFA-AS Mobile interim company 1 S.A.L.
🇱🇧Org handle: ORG-MICS1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
14total
9 IPv45 IPv6
IPv4 Addresses
Allocated (RIR)2,816
Announced (BGP)2,304
IPv6 Addresses
Allocated (RIR)1×10³⁰
Announced (BGP)3.9×10²⁹
Announced Prefixes
(BGP)14|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 | |
| Valid | RIPE | 2026-10-09 |
1-10 of 14
1 / 2
Allocated Prefixes
(RIR)12Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.197.46.0/23 | 🇱🇧 LB | RIPENCC | allocated |
| 91.232.100.0/23 | 🇱🇧 LB | RIPENCC | allocated |
| 185.81.140.0/22 | 🇱🇧 LB | RIPENCC | allocated |
| 185.81.142.0/24 | 🇱🇧 LB | RIPE | assigned |
| 185.81.143.0/24 | 🇱🇧 LB | RIPE | assigned |
| 185.132.148.0/24 | 🇱🇧 LB | RIPE | assigned |
| 2a05:8800::/29 | 🇱🇧 LB | RIPENCC | allocated |
| 2a05:8800::/32 | 🇱🇧 LB | RIPE | assigned |
| 2a05:8801::/32 | 🇱🇧 LB | RIPE | assigned |
| 2a05:8802::/32 | 🇱🇧 LB | RIPE | assigned |
1-10 of 12
1 / 2
All 14 announced prefixes of AS57513 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS57513 hands its own prefixes to: transit providers, or peers at an exchange.
- AS42020LibanTelecom OGERO14
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 AS57513 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/57513Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/57513" | jq