AS199334 rigilweb RIGIL WEB TECHNOLOGIES LIMITED
🇳🇿Org handle: ORG-RWTL1-RIPE
-----BEGIN TOKEN-----07973545ef84c02c7da1762b49fe81fdb6983604fc571017707c98c08f45eae976588a1126a44cad34b68afdc85c59a18a406ff44b05795eca3a173269a40275-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)0
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 159.255.146.0/24 | 🇳🇿 NZ | RIPENCC | allocated |
| 185.176.132.0/24 | 🇳🇿 NZ | RIPENCC | allocated |
| 2a13:c680::/29 | 🇳🇿 NZ | RIPENCC | allocated |
All 2 announced prefixes of AS199334 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS199334 hands its own prefixes to: transit providers, or peers at an exchange.
- AS16276OVH SAS2
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 AS199334 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/199334Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/199334" | jq