f01912298
Ashburn, Virginia, US
Sample Piece URL not found
100.02 TiB
Total Deal Size
20.11%
Deal Percentage
0% / 0 B
Duplication
44084
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
194.32 days
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.
Ashburn, Virginia, US
Sample Piece URL not found
100.02 TiB
Total Deal Size
20.11%
Deal Percentage
0% / 0 B
Duplication
44084
Total Claims
N/A
RPA
N/A
Consistent RPA
N/A
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Columbus, Ohio, US
Sample Piece URL not found
99.86 TiB
Total Deal Size
20.08%
Deal Percentage
0% / 0 B
Duplication
41886
Total Claims
3%
RPA
N/A
Consistent RPA
N/A
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Zhengzhou, Henan, CN
Sample Piece URL not found
96.25 TiB
Total Deal Size
19.35%
Deal Percentage
0% / 0 B
Duplication
41806
Total Claims
N/A
RPA
N/A
Consistent RPA
N/A
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Hohhot, Inner Mongolia, CN
100.81 TiB
Total Deal Size
20.27%
Deal Percentage
0% / 0 B
Duplication
41696
Total Claims
N/A
RPA
N/A
Consistent RPA
N/A
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Ashburn, Virginia, US
Sample Piece URL not found
100.47 TiB
Total Deal Size
20.2%
Deal Percentage
0% / 0 B
Duplication
42029
Total Claims
1%
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 |
|---|---|---|---|
| 4 | 6.34 TiB | 25.38 TiB | 5.1% |
| 1 | 496 GiB | 496 GiB | 0.09% |
| 5 | 93.02 TiB | 465.08 TiB | 93.5% |
| 2 | 768 GiB | 1.5 TiB | 0.3% |
| 3 | 1.66 TiB | 4.97 TiB | 0.99% |
| 102.25 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. | ||