2a0c:3580:3000::/36 - Zap Hosting ZAP Hosting (AS206996)
CIDR
2a0c:3580:3000::/36
IP Version
IPv6
Addresses
4951.7Y
Mask
/36
Country
🇺🇸 United States
City
Los Angeles
RIR
RIPE NCC
Status
announced
Allocated
-
Announced BGP Routes
1 of 1 routeRPKI:
IRR:
Swipe sideways to see all columns →
| Prefix | Origin AS | RPKI | IRR | Last Seen |
|---|---|---|---|---|
| 2a0c:3580:3000::/36 | AS206996 zap-hosting ZAP-Hosting GmbH | Valid | - | 2026-10-11 |
RPKI ROAs
| Prefix | Origin | Max Length | Trust Anchor |
|---|---|---|---|
| 2a0c:3580::/29 | AS206996 | /48 | ripe |
Transfer History
Registry transfers of 2a0c:3580:3000::/36, blocks inside it, or blocks containing it.
- 2a0c:3580::/29Transfer ·
| Date | Resource | From | To | Type |
|---|---|---|---|---|
| 2a0c:3580::/29 | Marvin Kluck trading as ZAP-Hosting GmbH & Co.KG | ZAP-Hosting Holding GmbH | Transfer |
Origin ASN
AS206996
zap-hosting ZAP-Hosting GmbH
Related Prefixes
Geolocation
Abuse Contact
Learn more
- RPKI and ROAs explainedWhat RPKI valid, invalid and no ROA mean
- RPKI validatorCheck ROA coverage for any prefix or ASN
- What is BGP?How prefixes are announced and routed
- More-specific prefixesGlossary: covering and more-specific routes
- IPv4 transfers in the RIPE NCC regionWho bought and sold address space recently
API
Open https://api.ipctl.io/v1/prefix/2a0c:3580:3000::/36Returns prefix allocation, BGP routes, and more-specific subnets.
curl -s "https://api.ipctl.io/v1/prefix/2a0c:3580:3000::/36" | jq
External Links