Rapid-Fire-y
BGP inherited
Cluster stats
| Netblocks | 4 · 510 IPv4 addresses |
| Cluster ID | 210302011 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 8 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 103.151.154.0/24 | Rapid-Fire-y | APNIC | ASSIGNED PORTABLE | ● high |
| 103.115.3.0/24 | Rapid-Fire-y | APNIC | ASSIGNED PORTABLE | ● low |
| 2001:df2:9b40::/48 | Rapid-Fire-y | APNIC | ASSIGNED PORTABLE | ● low |
| 2401:3fa0::/32 | Rapid-Fire-y | APNIC | ALLOCATED PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(2 of 4)
Possible discrepancies (1)
These blocks are registered to Rapid-Fire-y 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.
| 103.151.154.0/24 /24 | authorized for AS150369 — TelHi Corporation |
NIC Handles
APNIC-HM
AR1379-AP
AT1951-AP
ORG-RA61-AP
RA735-AP
RA735-AP
TC1146-AP
TC1146-AP