AS219463 THEBATTLE-GROUP-LTD THEBATTLE GROUP LTD
🇬🇧Org handle: ORG-TGL35-RIPE
-----BEGIN TOKEN-----29b97a699a5d130cda200e567b8fa85d7832aef428214e5debd3cf2c832cdd54470e3674f86a86b789e1a8041303a9a84ce83d2f6304165eab48b9f7e2ce2c34-----END TOKEN-----
RIPE NCCallocated
Announced Prefixes (BGP)
2total
2 IPv40 IPv6
IPv4 Addresses
Allocated (RIR)256
Announced (BGP)512
IPv6 Addresses
Allocated (RIR)1.2×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)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 195.123.172.0/24 | 🇺🇦 UA | RIPE | assigned |
| 2a14:ae00:108::/48 | 🇵🇱 PL | RIPE | assigned |
All 2 announced prefixes of AS219463 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS219463 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 AS219463 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/219463Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/219463" | jq