Open
No
N/A
1.30 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.
| Provider | Location | Total Deal Size | Percentage | Duplication | Total claims | RPA | Piece URL |
|---|---|---|---|---|---|---|---|
| f02002333 | Seoul, Seoul, KR | 799.63 TiB | 0.16% | 0% | 99345 | 99% | |
| f02002555 | Los Angeles, California, US | 799.63 TiB | 0.16% | 0% | 97139 | 100% | |
| f02003699 | Moscow, Moscow, RU | 1008.13 TiB | 0.2% | 0% | 160101 | 100% | |
| f03519250 | Los Angeles, California, US | 210 TiB | 0.04% | 0% | 34676 | 100% | |
| f03519255 | Guangzhou, Guangdong, CN | 1009.38 TiB | 0.2% | 0% | 37387 | 56% | |
| f03519265 | Seoul, Seoul, KR | 209.84 TiB | 0.04% | 0% | 31965 | N/A | |
| f03519270 | Hong Kong, Hong Kong, HK | 1009.41 TiB | 0.2% | 0% | 37388 | 100% |
The below table shows how each many unique data are replicated across storage providers.
| Providers | Unique Data | Total Deals | Percentage |
|---|---|---|---|
| 5 | 1007 TiB | 4.92 PiB | 99.78% |
| 4 | 2.75 TiB | 11 TiB | 0.21% |
| 1009.75 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 |
|---|---|---|
| f03146629 | 159.94 TiB | 5118 |