f02003699
Moscow, Moscow, RU
Sample Piece URL not found
126.69 TiB
Total Deal Size
16.22%
Deal Percentage
0% / 0 B
Duplication
163863
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
0.75 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.
Moscow, Moscow, RU
Sample Piece URL not found
126.69 TiB
Total Deal Size
16.22%
Deal Percentage
0% / 0 B
Duplication
163863
Total Claims
N/A
RPA
N/A
Consistent RPA
N/A
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Montréal, Quebec, CA
Sample Piece URL not found
198.28 TiB
Total Deal Size
25.38%
Deal Percentage
0% / 0 B
Duplication
108784
Total Claims
N/A
RPA
N/A
Consistent RPA
N/A
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Piscataway, New Jersey, US
Sample Piece URL not found
159.75 TiB
Total Deal Size
20.45%
Deal Percentage
0% / 0 B
Duplication
109098
Total Claims
N/A
RPA
N/A
Consistent RPA
N/A
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Dallas, Texas, US
Sample Piece URL not found
96.94 TiB
Total Deal Size
12.41%
Deal Percentage
0% / 0 B
Duplication
86125
Total Claims
N/A
RPA
N/A
Consistent RPA
N/A
Inconsistent RPA
N/A
Time to First Byte
N/A
Bandwidth
Osaka, Osaka, JP
Sample Piece URL not found
199.63 TiB
Total Deal Size
25.55%
Deal Percentage
0% / 0 B
Duplication
84805
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 |
|---|---|---|---|
| 2 | 28.91 TiB | 57.81 TiB | 7.39% |
| 1 | 126.81 TiB | 126.81 TiB | 16.23% |
| 4 | 83.75 TiB | 335 TiB | 42.87% |
| 3 | 87.22 TiB | 261.66 TiB | 33.49% |
| 326.69 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. | ||