f02825740
Tokyo, Tokyo, JP
Sample Piece URL not found
41.53 TiB
Total Deal Size
18.55%
Deal Percentage
0% / 0 B
Duplication
28264
Total Claims
N/A
RPA
N/A
Consistent RPA
100%
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Enterprise
Yes
10
1.48 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
41.53 TiB
Total Deal Size
18.55%
Deal Percentage
0% / 0 B
Duplication
28264
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
49.09 TiB
Total Deal Size
21.93%
Deal Percentage
3.5% / 1.72 TiB
Duplication
28401
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
23.66 TiB
Total Deal Size
10.57%
Deal Percentage
0% / 0 B
Duplication
27676
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
52.91 TiB
Total Deal Size
23.64%
Deal Percentage
0% / 0 B
Duplication
27985
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
56.66 TiB
Total Deal Size
25.31%
Deal Percentage
0% / 0 B
Duplication
28204
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 | 6.84 TiB | 13.75 TiB | 6.14% |
| 5 | 9.72 TiB | 48.97 TiB | 21.87% |
| 4 | 24.31 TiB | 98.06 TiB | 43.8% |
| 1 | 1.09 TiB | 1.09 TiB | 0.48% |
| 3 | 20.5 TiB | 61.97 TiB | 27.68% |
| 62.47 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. | ||