AS218932 FURYNET RYBCZYNSKI KACPER
🇵🇱Org handle: ORG-RKTA8-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
3total
2 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)1.2×10²⁴
Announced (BGP)1.2×10²⁴
Routing hygiene
Score 75/100 · High riskRPKI ROA coverage
33.3%
2 prefixes RPKI invalid
IRR route objects
33.3%
no origin mismatches
Hijack signals
1
1 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- Announces 1 prefix that RPKI assigns to another network (possible hijack or misconfiguration)
- 67% of announced prefixes (2 of 3) have no valid ROA, 2 of them RPKI invalid
- 67% of announced prefixes (2 of 3) have no IRR route object for this ASN
- Only one upstream seen in the AS paths of its routes
Based on 3 announced prefixes, updated daily (2026-10-21). How the score works · RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
31.42.121.0/24MOAS | Invalid | - | - |
| Invalid | - | - | |
| Valid | RIPE | - |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 130.78.9.0/24 | 🇺🇸 US | RIPE | assigned |
| 2a03:5840:15d::/48 | 🇵🇱 PL | RIPE | assigned |
All 3 announced prefixes of AS218932 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS218932 hands its own prefixes to: transit providers, or peers at an exchange.
- AS214762MATHOST Sebastian Stefanek Trading MatHost.Eu3
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 AS218932 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/218932Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/218932" | jq