f03074583
Tokyo, Tokyo, JP
Sample Piece URL not found
561.16 TiB
Total Deal Size
18.36%
Deal Percentage
0% / 0 B
Duplication
75026
Total Claims
N/A
RPA
N/A
Consistent RPA
N/A
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Enterprise
No
N/A
0.49 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.
Tokyo, Tokyo, JP
Sample Piece URL not found
561.16 TiB
Total Deal Size
18.36%
Deal Percentage
0% / 0 B
Duplication
75026
Total Claims
N/A
RPA
N/A
Consistent RPA
N/A
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Tung Chung, Islands, HK
Sample Piece URL not found
557.31 TiB
Total Deal Size
18.24%
Deal Percentage
0% / 0 B
Duplication
74995
Total Claims
N/A
RPA
N/A
Consistent RPA
N/A
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Seoul, Seoul, KR
Sample Piece URL not found
551.88 TiB
Total Deal Size
18.06%
Deal Percentage
0% / 0 B
Duplication
75017
Total Claims
N/A
RPA
N/A
Consistent RPA
N/A
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Tung Chung, Islands, HK
Sample Piece URL not found
551.69 TiB
Total Deal Size
18.05%
Deal Percentage
0% / 0 B
Duplication
75455
Total Claims
N/A
RPA
N/A
Consistent RPA
N/A
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Los Angeles, California, US
Sample Piece URL not found
833.78 TiB
Total Deal Size
27.29%
Deal Percentage
0.01% / 128 GiB
Duplication
75297
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 |
|---|---|---|---|
| 4 | 538.94 TiB | 2.11 PiB | 70.54% |
| 1 | 833.66 TiB | 833.78 TiB | 27.28% |
| 3 | 21.66 TiB | 64.97 TiB | 2.12% |
| 2 | 672 GiB | 1.31 TiB | 0.04% |
| 1.36 PiB 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. | ||