f02825740
Tokyo, Tokyo, JP
Sample Piece URL not found
358.16 TiB
Total Deal Size
20.22%
Deal Percentage
0.04% / 160 GiB
Duplication
28492
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
0.33 day
Client is receiving DataCap from single allocator.
Client was active in last 60 days or spent all its DataCap
The below table shows the distribution of storage providers that have stored data for this client.
Tokyo, Tokyo, JP
Sample Piece URL not found
358.16 TiB
Total Deal Size
20.22%
Deal Percentage
0.04% / 160 GiB
Duplication
28492
Total Claims
N/A
RPA
N/A
Consistent RPA
100%
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
357.34 TiB
Total Deal Size
20.17%
Deal Percentage
0.03% / 128 GiB
Duplication
28626
Total Claims
N/A
RPA
N/A
Consistent RPA
100%
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Taipei, Taiwan, TW
Sample Piece URL not found
358 TiB
Total Deal Size
20.21%
Deal Percentage
0.04% / 160 GiB
Duplication
27964
Total Claims
N/A
RPA
N/A
Consistent RPA
100%
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Los Angeles, California, US
Sample Piece URL not found
356.09 TiB
Total Deal Size
20.1%
Deal Percentage
0.04% / 160 GiB
Duplication
28219
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
341.88 TiB
Total Deal Size
19.3%
Deal Percentage
0.05% / 192 GiB
Duplication
28295
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 |
|---|---|---|---|
| 2 | 384 GiB | 768 GiB | 0.04% |
| 1 | 96 GiB | 96 GiB | 0% |
| 4 | 19.78 TiB | 79.13 TiB | 4.46% |
| 5 | 337.56 TiB | 1.65 PiB | 95.32% |
| 3 | 992 GiB | 2.91 TiB | 0.16% |
| 358.78 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. | ||