AS59945 HYNASINSKI-AS A. Z. Hynasinscy sp. j.
🇵🇱Org handle: ORG-AZHs1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
4total
4 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)4|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 91.224.46.0/23 | 🇵🇱 PL | RIPENCC | assigned |
| 185.80.57.0/24 | 🇵🇱 PL | RIPE | assigned |
| 185.80.58.0/24 | 🇵🇱 PL | RIPE | assigned |
All 4 announced prefixes of AS59945 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS59945 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (1)
Networks whose own prefixes AS59945 passes on: usually its customers.
- AS215985PODDEBICE Gmina Poddebice1
Other adjacent networks (1)
Adjacent to AS59945 in the transit part of AS paths: peers, providers or customers.
- AS5617TPNET Orange Polska Spolka Akcyjna1
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 AS59945 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/59945Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/59945" | jq