AS198075 BOUNCEZERO-MNT BounceZero Ltd
🇬🇧Org handle: ORG-BL636-RIPE
-----BEGIN TOKEN-----85c1366fafbe7c53393aecd512cda2add83778a45856a94c7f50093f50e5551d39e704513a6a6f95672c805cd2e2c295335d58cb5570b7e357519f22da8f6120-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
1total
1 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)256
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)0
Announced Prefixes
(BGP)1|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | Other IRRRIPE | 2026-10-11 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 147.79.2.0/24 | 🇬🇧 GB | RIPE | assigned |
All 1 announced prefix of AS198075 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS198075 hands its own prefixes to: transit providers, or peers at an exchange.
- AS16276OVH SAS1
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 AS198075 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/198075Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/198075" | jq