1,695
2K
Probes last 7d
June 2, 2026, 10:54 p.m. UTC
Last updated now
0
0/3
Criteria met last 7d
June 2, 2026, 10:54 p.m. UTC
Last updated now
0.52
0.52s
Median TTFB last 7d
June 2, 2026, 10:54 p.m. UTC
Last updated now

Mongo2Stor Mainnet Approved

Storage Provider Details

Dealbot performance for storage provider Mongo2Stor Mainnet.

Approval Criteria

Approval Criteria

Approval Criteria

Each gauge shows a methodology criterion's success rate over the selected time range for this provider and probe location. The arc is split at the approval threshold into a red fail zone and a green pass zone; the value reads green once the rate clears the threshold (and "no data" when there are no samples). The figure under each gauge is the number of samples the rate is based on — green once it clears the required minimum, amber while it is still below it. Data Retention is shown as success (100 − fault), so all gauges read "higher is better".

Success rate over the selected range vs the approval threshold

Acceptance Criteria Trends

Daily Data Storage Success

Daily Data Storage Success

The share of data-storage checks that reached the deal_created state each day, for the selected provider and probe location. A check succeeds when the dealbot uploads a piece, gets it added and confirmed on-chain, and a deal is created.

The bars show the daily success rate; the overlaid line shows how many checks were run that day (the samples used to compute the rate), plotted against the right axis. A high rate over very few samples is less meaningful than the same rate over many.

Loading ...

Daily Retrieval Success

Daily Retrieval Success

The share of retrieval checks that succeeded each day, for the selected provider and probe location. A retrieval check succeeds when the dealbot fetches a previously stored piece back from the provider without error or timeout.

The bars show the daily success rate; the overlaid line shows how many retrieval checks were run that day (the samples used to compute the rate), plotted against the right axis.

Loading ...

Daily Data Retention Success

Daily Data Retention Success

The share of proving periods that were proven (not faulted) each day, for the selected provider and probe location. Computed from per-poll deltas of the cumulative proving-period counters, so each day reflects the periods that came due that day. The dashed bars' overlaid line shows the number of periods (samples) each day. Approval requires ≥ 99.8% (i.e. ≤ 0.2% faulted).

Loading ...

Data Storage

Data Storage Pipeline

Data Storage Pipeline

Each column is a single data-storage check for the selected provider and probe location, ordered oldest (left) to newest (right). Each row is a stage of the storage pipeline:

  • Upload — the dealbot uploaded the piece to the provider.
  • On-chain — the piece was added and confirmed on-chain.
  • Discoverability — the piece's root CID was verified findable via IPNI.
  • Retrieval — a retrieval check for the resulting deal succeeded (joined from the retrieval checks by deal id).

A cell is green when the stage succeeded, red when it failed, and gray when it was skipped or never reached (for example, on-chain confirmation is skipped when the upload itself failed). Hover a cell for the probe timestamp and stage detail.

Loading ...

Timings

Retrieval Latency

Retrieval Latency

Daily p50, p90 and p95 of the retrieval time to first byte (TTFB) for the selected provider and probe location, in seconds. Computed over successful retrieval checks only — failed or timed-out retrievals have no first-byte time.

The dashed line shows the number of samples each day, plotted against the right axis. Tail percentiles (p90/p95) capture the slow retrievals that median latency hides.

Loading ...

IPNI Timing

IPNI Timing

Daily p50, p90 and p95 of how long IPNI took, in seconds, for the selected provider and probe location. Use the dropdown to switch stage:

  • Ingest — from on-chain confirmation until the piece is advertised on IPNI.
  • Verification — from on-chain confirmation until the root CID is confirmed findable via IPNI.

Both are measured from pieces_confirmed_at; only checks that reached the chosen IPNI milestone are counted. The dashed line shows the daily sample count.

Loading ...

Latest probes

Time Location Status IPNI Piece CID File size Error

Times are shown in UTC.

Page 1
Time Location Status Service HTTP TTFB Bytes

Times are shown in UTC.

Page 1
Time Due Proven Faulted Δ Proven Δ Faulted Overdue (est.)

Times are shown in UTC.

Page 1