AS200153 SZALAY-NET Marton Szalay
🇭🇺Org handle: ORG-MS905-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
0 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)2.4×10²⁴
Announced (BGP)2.4×10²⁴
Routing hygiene
Score 10/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
Based on 2 announced prefixes, updated daily (2026-10-21). How the score works · RPKI explained
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-22 | |
| Valid | Other IRRRIPE | 2026-10-22 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 2001:678:11cc::/48 | 🇭🇺 HU | RIPENCC | assigned |
| 2a06:9801:213::/48 | 🇭🇺 HU | RIPE | assigned |
All 2 announced prefixes of AS200153 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS200153 hands its own prefixes to: transit providers, or peers at an exchange.
- AS11967HOP179 OU2
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 AS200153 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/200153Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/200153" | jq