Every FWSS data set on PDP mainnet, with each payer's live Filecoin Pay funding state in the same table.
A data set that goes silent is flagged, never hidden.
Last refresh: -Chain head epoch: -Latest indexed proof: -Source: observer.yablu.net (YABLU observer, mainnet)
Data set health
Severity order, largest first. Cards filter, columns sort.
Terminated, dormant and deleted sets are collapsed below the table.
Loading the network...
Last refresh: -Chain head epoch: -Latest indexed proof: -Source: observer.yablu.net (YABLU observer, mainnet)
Data set health under the #583 pricing upgrade
Waiting for the network snapshot...
Last refresh: -Source: observer.yablu.net (indexed fwss_piece_added events, mainnet)
Second-copy onboarding progress
Second-copy datasets for the four Storacha-migration clients, onboarding to external SPs
(infrafolio, SP 7 and Mongo2Stor, SP 5). Progress = pieces committed on chain vs the client's known
piece total; every piece is exactly 1 GiB, so pieces = GiB. NFTs2Me is split across two datasets (one per SP)
and rolls up as one client.
Loading second-copy progress...
Data set health
The same health view as the Migration Health tab, applied to the four second-copy data sets on
infrafolio (SP 7) and Mongo2Stor (SP 5). Stale = no proving advance (possession proof or period roll)
for over 36 h with provable pieces on chain; a set that never proves flags 36 h after creation. Payer funding is the same
live FilecoinPay state as the Migration Health tab (same payers, same accounts).