AS200651 FlokiNET FlokiNET ehf
🇮🇸Org handle: ORG-FE72-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
42total
36 IPv46 IPv6
IPv4 Addresses
Allocated (RIR)17,408
Announced (BGP)9,728
IPv6 Addresses
Allocated (RIR)2.5×10³⁰
Announced (BGP)7.2×10²⁴
Prefix Limit (IPv4)
100
Prefix Limit (IPv6)
20
Country
🇮🇸 ISRIR
RIPE NCCStatus
allocated
Allocated
2015-05-15
Listed on the threat map (2026-10-11)
Large hosting providers appear because attackers rent their servers, not necessarily because of the operator.
Announced Prefixes
(BGP)42|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
178.83.99.0/24MOAS | Invalid | - | 2026-10-11 |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
1-10 of 42
1 / 5
Allocated Prefixes
(RIR)52Prefix | Country | RIR | Status |
|---|---|---|---|
| 37.156.68.0/24 | 🇮🇸 IS | RIPENCC | allocated |
| 37.228.128.0/23 | 🇮🇸 IS | RIPE | assigned |
| 37.228.128.0/24 | 🇮🇸 IS | RIPENCC | allocated |
| 37.228.129.0/24 | 🇮🇸 IS | RIPENCC | allocated |
| 85.193.77.0/24 | 🇮🇸 IS | RIPENCC | allocated |
| 89.124.252.0/24 | 🇮🇸 IS | RIPENCC | allocated |
| 94.198.190.0/24 | 🇮🇸 IS | RIPENCC | allocated |
| 95.133.160.0/23 | 🇮🇸 IS | RIPENCC | allocated |
| 95.133.164.0/22 | 🇺🇦 UA | RIPENCC | allocated |
| 95.133.166.0/23 | 🇮🇸 IS | RIPENCC | allocated |
1-10 of 52
1 / 6
All 42 announced prefixes of AS200651 →
BGP Neighbours
(seen in AS paths)Upstreams (5)
Networks AS200651 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (1)
Networks whose own prefixes AS200651 passes on: usually its customers.
- AS208414WEDOS GLOBAL WEDOS Internet, A.S1
Transfer History
Registry transfers of AS200651 between organisations.
- AS200651Transfer ·
- AS200651Transfer ·
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 AS200651 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/200651Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/200651" | jq