AS42357 progest ProGest SA
π¨πOrg handle: ORG-PS412-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)6.3Γ10Β²βΉ
Announced (BGP)0
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
5
Country
π¨π CHRIR
RIPE NCCStatus
allocated
Allocated
2020-11-23
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.218.196.0/24 | π¨π CH | RIPENCC | allocated |
| 194.140.194.0/24 | π¨π CH | RIPENCC | allocated |
| 2a10:c680::/29 | π¨π CH | RIPENCC | allocated |
All 2 announced prefixes of AS42357 β
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS42357 hands its own prefixes to: transit providers, or peers at an exchange.
- AS198385AlpineDC2
Downstreams (1)
Networks whose own prefixes AS42357 passes on: usually its customers.
- AS203529GETUPLINK SYSTEM AND NETWORK SOLUTIONS, LDA1
Other adjacent networks (1)
Adjacent to AS42357 in the transit part of AS paths: peers, providers or customers.
- AS174Cogent Communications1
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 AS42357 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/42357Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/42357" | jq