AS201103 gomailify Mercata Sagl
🇨🇭Org handle: ORG-MS807-RIPE
-----BEGIN TOKEN-----f80990651c83670f2be7fc31e0378cd34ddf16fe9f85aec45a49c7c9d6fb29f87ccb3763c18339d0f756c91c3dad58014d8e20952558c6c11885e9e0529123f6-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 45.153.89.0/24 | 🇨🇭 CH | RIPENCC | allocated |
| 159.255.151.0/24 | 🇨🇭 CH | RIPENCC | allocated |
All 2 announced prefixes of AS201103 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS201103 hands its own prefixes to: transit providers, or peers at an exchange.
- AS16276OVH SAS2
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 AS201103 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/201103Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/201103" | jq