AS200709 Flotek-Shared-MNT Flotek Group Limited
🇬🇧Org handle: ORG-FG166-RIPE
-----BEGIN TOKEN-----e9053c09bd27832d987cb434e4fe5a004f244a5cb41edf3705073b81a66c647e3b87b5aed10f60569ed0d1da1f9da4efba6326c575b5c7c826166564f9f23d72-----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 |
|---|---|---|---|
| 178.92.119.0/24 | 🇬🇧 GB | RIPE | assigned |
All 1 announced prefix of AS200709 →
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS200709 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 AS200709 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/200709Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/200709" | jq