DashboardAllocatorsClientsStorage ProvidersAlertsAbout

Ecosystem

Filecoin
Fil+
Documentation
Search
Propose a Dashboard

Report 279505

Client ID: f03662041

Report Detail
Report 279505 from

Client Overview

Type of Data

Open

Using Contract

No

Client Contract Deviation

N/A

Average Time To First Deal

88.81 days

DataCap Allocations

Client is receiving DataCap from multiple allocators.

Activity

Client was active in last 60 days or spent all its DataCap

Storage Provider Distribution

The below table shows the distribution of storage providers that have stored data for this client.

Status:
6 issues
Number of providers: 3

f01697248

Seoul, Seoul, KR

Sample Piece URL not found

26.78 TiB

Total Deal Size

2.66%

Deal Percentage

0.12% / 32 GiB

Duplication

90013

Total Claims

N/A

RPA

N/A

Consistent RPA

100%

Inconsistent RPA

N/A

Time to First Byte

N/A

Bandwidth

f01904546

Seoul, Seoul, KR

442.84 TiB

Total Deal Size

44%

Deal Percentage

0% / 0 B

Duplication

71639

Total Claims

22%

RPA

22%

Consistent RPA

78%

Inconsistent RPA

10591 ms

Time to First Byte

91.29 Mbps

Bandwidth

f03199233

Seoul, Seoul, KR

536.91 TiB

Total Deal Size

53.34%

Deal Percentage

0.34% / 1.81 TiB

Duplication

103802

Total Claims

81%

RPA

81%

Consistent RPA

19%

Inconsistent RPA

10603 ms

Time to First Byte

83.02 Mbps

Bandwidth

  • RPA - default Random Piece Availability
  • Consistent - retrievability of Storage Providers including CAR files only
  • Inconsistent - retrievability of Storage Providers excluding the CAR files / including other available files that are not CAR files

Deal Data Replication

The below table shows how each many unique data are replicated across storage providers.

Status:
2 issues
ProvidersUnique DataTotal DealsPercentage
1
86.5 TiB
86.56 TiB
8.6%
2
459.09 TiB
919.97 TiB
91.39%
545.59 TiB Total
Wrong provider count
Sufficient provider count

Deal Data Shared with other Clients

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.

ClientTotal Deals AffectedUnique CIDs
No results.