f02813403
London, England, GB
Sample Piece URL not found
442.16 TiB
Total Deal Size
14.3%
Deal Percentage
0% / 0 B
Duplication
79410
Total Claims
N/A
RPA
N/A
Consistent RPA
N/A
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Open
No
N/A
0.13 day
Client is receiving DataCap from single allocator.
Client has unspent DataCap and was inactive for more than a 2 months
The below table shows the distribution of storage providers that have stored data for this client.
London, England, GB
Sample Piece URL not found
442.16 TiB
Total Deal Size
14.3%
Deal Percentage
0% / 0 B
Duplication
79410
Total Claims
N/A
RPA
N/A
Consistent RPA
N/A
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Newark, New Jersey, US
Sample Piece URL not found
500.81 TiB
Total Deal Size
16.2%
Deal Percentage
0% / 0 B
Duplication
85113
Total Claims
N/A
RPA
N/A
Consistent RPA
N/A
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Ho Chi Minh City, Ho Chi Minh City (HCMC), VN
Sample Piece URL not found
543 TiB
Total Deal Size
17.56%
Deal Percentage
0% / 0 B
Duplication
98164
Total Claims
N/A
RPA
N/A
Consistent RPA
N/A
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
London, England, GB
Sample Piece URL not found
537.66 TiB
Total Deal Size
17.39%
Deal Percentage
0% / 0 B
Duplication
89023
Total Claims
N/A
RPA
N/A
Consistent RPA
N/A
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Newark, New Jersey, US
Sample Piece URL not found
1.04 PiB
Total Deal Size
34.55%
Deal Percentage
50% / 534.03 TiB
Duplication
149225
Total Claims
N/A
RPA
N/A
Consistent RPA
N/A
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
The below table shows how each many unique data are replicated across storage providers.
| Providers | Unique Data | Total Deals | Percentage |
|---|---|---|---|
| 2 | 320 GiB | 640 GiB | 0.02% |
| 4 | 157.75 TiB | 779.78 TiB | 25.22% |
| 1 | 352 GiB | 352 GiB | 0.01% |
| 5 | 384.5 TiB | 2.25 PiB | 74.61% |
| 3 | 1.06 TiB | 3.94 TiB | 0.12% |
| 543.97 TiB Total |
The below table shows how many unique data are shared with other clients. Usually different applications owns different data and should not resolve to the same CID.
However, this could be possible if all below clients use same software to prepare for the exact same dataset or they belong to a series of LDN applications for the same dataset.
| Client | Total Deals Affected | Unique CIDs |
|---|---|---|
| No results. | ||