BGP Tunnel
BGPTunnel
Data as of 2026-07-26
Registry
Cluster stats
| Netblocks | 3 |
| IPv6 | 3 prefixes (largest 2a0c:9a40:a000::/36) |
| All fragments | 4 blocks across 2 clusters |
| Cluster ID | 213754288 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a0c:9a40:a000::/36 | BGPTunnel | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0c:9a47::/44 | BGPTunnel | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0c:9a47:20::/48 | BGPTunnel | RIPE | ASSIGNED | ● low |
IPv6 ranges (3)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
Possible discrepancies (3)
These blocks are registered to BGPTunnel but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2a0c:9a40:a000::/36 /36 | authorized for AS209533 — iFog GmbH |
| 2a0c:9a47::/44 /44 | authorized for AS209533 — iFog GmbH |
| 2a0c:9a47:20::/48 /48 | authorized for AS209533 — iFog GmbH |
NIC Handles
DUMY-RIPE
DUMY-RIPE
ch-ifog-1-mnt