Tampa Co-Op
BGP inherited
Cluster stats
| Netblocks | 8 · 766 IPv4 addresses |
| Cluster ID | 208805999 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 2 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
5 weekly snapshots · JSON
8
0 netblocks since 2026-07-05
2026-07-05
peak 8
2026-07-19
IP Ranges (8)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 23.152.24.0/24 | Tampa Co-Op | BGP | ANNOUNCED | ● high |
| 44.98.248.0/23 | Tampa Co-Op | BGP | ANNOUNCED | ● high |
| 149.112.178.4/32 | Tampa Co-Op | PEERINGDB | ASSIGNED | ● high |
| 206.108.114.30/32 | Tampa Co-Op | PEERINGDB | ASSIGNED | ● high |
| 2001:504:3c::30/128 | Tampa Co-Op | PEERINGDB | ASSIGNED | ● high |
| 2602:2af:100::/48 | Tampa Co-Op | BGP | ANNOUNCED | ● high |
| 2602:f527::4/128 | Tampa Co-Op | PEERINGDB | ASSIGNED | ● high |
| 2605:900:1000::/40 | Tampa Co-Op | BGP | ANNOUNCED | ● high |
Network trust
what's this?
RPKI hygiene: D
how networks compare →
25.0%
of checked blocks have valid RPKI ROA coverage
(2 of 8)
Possible discrepancies (2)
These blocks are registered to Tampa Co-Op 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.
| 2602:2af:100::/48 /48 | authorized for AS12110 — Internex Inc. |
| 23.152.24.0/24 /24 | authorized for AS12110 — Internex Inc. |
NIC Handles
AS400846
AS400846