AS58329 SERVINGA-NL servinga GmbH
π©πͺOrg handle: ORG-SG288-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
10total
8 IPv42 IPv6
IPv4 Addresses
Allocated (RIR)2,304
Announced (BGP)2,304
IPv6 Addresses
Allocated (RIR)2.4Γ10Β²β΄
Announced (BGP)2.4Γ10Β²β΄
Prefix Limit (IPv4)
20
Prefix Limit (IPv6)
10
Country
π©πͺ DERIR
RIPE NCCStatus
allocated
Allocated
2012-06-27
Routing hygiene
Score 15/100 Β· Low riskRPKI ROA coverage
90%
1 prefix RPKI invalid
IRR route objects
90%
1 prefix registered for another origin
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
3
diversity 46/100
- 10% of announced prefixes (1 of 10) have no valid ROA, 1 of them RPKI invalid
Based on 10 announced prefixes, updated daily (2026-10-23). How the score works Β· RPKI explained
Announced Prefixes
(BGP)10|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
79.132.133.0/24MOAS | Invalid | - | 2026-10-26 |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 |
Allocated Prefixes
(RIR)10Prefix | Country | RIR | Status |
|---|---|---|---|
| 31.214.157.0/24 | π©πͺ DE | RIPENCC | allocated |
| 45.155.249.0/24 | π³π± NL | RIPE | assigned |
| 79.132.128.0/24 | π³π± NL | RIPE | assigned |
| 79.132.129.0/24 | π³π± NL | RIPE | assigned |
| 79.132.133.0/24 | π³π± NL | RIPE | assigned |
| 185.158.249.0/24 | π³π± NL | RIPE | assigned |
| 193.242.210.0/23 | π©πͺ DE | RIPENCC | assigned |
| 194.76.225.0/24 | π³π± NL | RIPE | assigned |
| 2001:67c:2ae8::/48 | π©πͺ DE | RIPENCC | assigned |
| 2a0b:7140:6::/48 | π³π± NL | RIPE | assigned |
All 10 announced prefixes of AS58329 β
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS16003 | πͺπΈFORNEX-NL-AS Fornex Hosting S.L. |
BGP Neighbours
(seen in AS paths)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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/58329Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/58329" | jq