f01100139
Tokyo, Tokyo, JP
Sample Piece URL not found
130 TiB
Total Deal Size
11.1%
Deal Percentage
2.91% / 3.78 TiB
Duplication
52577
Total Claims
N/A
RPA
N/A
Consistent RPA
100%
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Open
No
N/A
3.33 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.
Tokyo, Tokyo, JP
Sample Piece URL not found
130 TiB
Total Deal Size
11.1%
Deal Percentage
2.91% / 3.78 TiB
Duplication
52577
Total Claims
N/A
RPA
N/A
Consistent RPA
100%
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Seoul, Seoul, KR
Sample Piece URL not found
207.69 TiB
Total Deal Size
17.73%
Deal Percentage
0.14% / 288 GiB
Duplication
35408
Total Claims
N/A
RPA
N/A
Consistent RPA
100%
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Jakarta, Jakarta, ID
Sample Piece URL not found
209.91 TiB
Total Deal Size
17.92%
Deal Percentage
49.26% / 103.41 TiB
Duplication
111462
Total Claims
N/A
RPA
N/A
Consistent RPA
100%
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Seoul, Seoul, KR
Sample Piece URL not found
475.69 TiB
Total Deal Size
40.61%
Deal Percentage
22.28% / 105.97 TiB
Duplication
111049
Total Claims
N/A
RPA
N/A
Consistent RPA
100%
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Singapore, Singapore, SG
Sample Piece URL not found
148.16 TiB
Total Deal Size
12.65%
Deal Percentage
0% / 0 B
Duplication
38687
Total Claims
N/A
RPA
N/A
Consistent RPA
100%
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 |
|---|---|---|---|
| 1 | 473.44 TiB | 488.88 TiB | 41.73% |
| 3 | 128 GiB | 384 GiB | 0.03% |
| 2 | 242.09 TiB | 682.19 TiB | 58.23% |
| 715.66 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.