AS203551 PL-GO-NET-AS GO-NET Spolka z o.o.
🇵🇱Org handle: ORG-GSZO26-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)0
Routing hygiene
Score 65/100 · High riskRPKI ROA coverage
0%
no RPKI invalid prefixes
IRR route objects
0%
1 prefix registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- 100% of announced prefixes (1 of 1) have no valid ROA
- 100% of announced prefixes (1 of 1) have no IRR route object for this ASN
- 1 prefix registered in IRR route objects for another active network and not authorized by a ROA
- Only one upstream seen in the AS paths of its routes
Based on 1 announced prefix, updated daily (2026-10-12). How the score works · RPKI explained
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | - | 2026-10-12 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 84.234.117.0/24 | 🇵🇱 PL | RIPENCC | assigned |
| 2a06:1e00:d::/48 | 🇵🇱 PL | RIPE | assigned |
All 1 announced prefix of AS203551 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS203551 hands its own prefixes to: transit providers, or peers at an exchange.
- AS62081EPIX WAW GlobalMix Stowarzyszenie E Poludnie1
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 AS203551 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/203551Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/203551" | jq