TIG-Arrow
Data as of 2026-08-09
BGP inherited
Limited data: only 2 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 2 |
| IPv6 | 1 prefix (largest 2a0c:1ec1:300::/48) |
| Cluster ID | 220030011 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| 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 (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 185.251.237.48/28 | TIG-Arrow | RIPE | ASSIGNED PA | ● low |
| 2a0c:1ec1:300::/48 | TIG-Arrow | RIPE | ASSIGNED | ● low |
IPv6 ranges (1)
| CIDR |
|---|
| 2a0c:1ec1:300::/48 |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
Possible discrepancies (1)
These blocks are registered to TIG-Arrow 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:1ec1:300::/48 /48 | authorized for AS60341 — Ekco B.V. |
NIC Handles
BOSWORX-MNT
DUMY-RIPE
DUMY-RIPE