Open
No
N/A
0.98 day
Client is receiving DataCap from single allocator.
Client was active in last month or spent all its DataCap
The below table shows the distribution of storage providers that have stored data for this client.
Provider | Location | Total Deal Size | Percentage | Duplication | IPNI Misreporting | Total claims | HTTP Retrievability | RPA | Piece URL |
|---|---|---|---|---|---|---|---|---|---|
| f01021773 | 256 GiB | 0.01% | 0.00% | OK | 13632 | 24.39% | 69.00% | ||
| f01996719 | 92.56 TiB | 2.19% | 0.00% | OK | 67519 | 22.01% | 51.00% | ||
| f02088691 | 56.53 TiB | 1.34% | 0.83% | OK | 6623 | 0.00% | 0.00% | ||
| f03336022 | 191.88 TiB | 4.55% | 0.00% | OK | 92329 | 9.56% | 8.00% | ||
| f03528662 | 649.75 TiB | 15.40% | 0.00% | OK | 69094 | 10.36% | 0.00% | ||
| f03528925 | 650.63 TiB | 15.42% | 0.00% | OK | 71442 | 11.32% | 5.00% | ||
| f03528938 | 650.41 TiB | 15.41% | 0.00% | OK | 72183 | 8.45% | 1.00% | ||
| f03528948 | 220.28 TiB | 5.22% | 0.00% | OK | 81658 | 2.91% | 0.00% | ||
| f03528979 | 222.06 TiB | 5.26% | 0.00% | OK | 81624 | 2.55% | 0.00% | ||
| f03529412 | 220.94 TiB | 5.24% | 0.00% | OK | 82857 | 3.09% | 0.00% | ||
| f03540144 | 214.16 TiB | 5.08% | 0.00% | OK | 211631 | 4.69% | 15.00% | ||
| f03540147 | 220.72 TiB | 5.23% | 0.00% | OK | 211799 | 5.49% | 27.00% | ||
| f03540153 | 221.31 TiB | 5.25% | 0.00% | OK | 222412 | 2.52% | 0.00% | ||
| f03558637 | 274.81 TiB | 6.51% | 0.00% | OK | 123596 | 4.44% | 91.00% | ||
| f03600845 | 251.97 TiB | 5.97% | 0.00% | OK | 77903 | 13.42% | 100.00% | ||
| f03601451 | 81.22 TiB | 1.92% | 0.00% | OK | 159495 | 7.05% | 29.00% |
The below table shows how each many unique data are replicated across storage providers.
Providers | Unique Data | Total Deals | Percentage |
|---|---|---|---|
1 | 258.13 TiB | 258.59 TiB | 6.12% |
2 | 294.5 TiB | 589 TiB | 13.95% |
3 | 889.25 TiB | 2.61 PiB | 63.22% |
4 | 176.03 TiB | 704.13 TiB | 16.68% |
| 1.58 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.