Tracking

One read is a snapshot. Tracking shows wear moving.

Tracking reads the same cards again on a schedule and signs every read. When a counter moves, you see it, and so can anyone you share the record with.

First 100 days included with every record. Then $0.60 per GB per year, annual only.

Start tracking We set it up with you

Install the reader One line, read only

NVIDIA A10 built Apr 2022

NVIDIA A10 · serial ···3197 · 8 signed reads over 30 days, Aug 30 to Sep 29 · 3 GPU resets between reads, marked · Provider withheld.

What only tracking sees

Three signals live between reads.

Each mark is one signed read of a real card.

Card · condition

nothing moved
a counter rose
reset seen
repair waiting for a reset
a counter fell

···3611 A100-PCIE-40GB Clean
···9659 H100 80GB HBM3 A few fixed bit flips
···7343 A100 80GB PCIe Repaired, stable
···0230 L40S Serious
···3343 A100-SXM4-80GB Serious
···3197 A10 Failing
···7829 A10 Flagged
···6065 L40 Flagged

Date of each signed read, 2026

Our eight published cards, 54 signed reads. Provider withheld.

After day 100

Why people keep tracking.

A listing

NVIDIA A100-PCIE-40GB 40 GB · serial ···3611

Voltry record · Clean · 14 reads over 87 days Check

Sell it for what it is

A card with months of clean reads is easier to sell than a card with one.

Relying lens · granted cards

···3197 A10 Uncorrectable errors rose rose Sep 29
···0230 L40S Repair waiting for a reset, 30+ days since Jul 16
···3611 A100-PCIE-40GB No trigger read Oct 6

Finance and insure it

Lenders and insurers can hold a read grant and watch the fleet they back.

From: Voltry
Subject: A tracked card moved

A100-SXM4-80GB ···3343. Fixed errors went from 2 to 755 between Sep 14 and Oct 3.

See the record

Catch wear early

Get an email when a tracked card moves, before a job crashes on it.

Signed read log A10 ···3197

2026-09-13 06:24 UTC signed uncorrectable errors 172,069 reset seen
2026-09-15 14:25 UTC signed uncorrectable errors 239,124
2026-09-29 09:47 UTC signed uncorrectable errors 373,598 reset seen

Signature checks

Settle claims on facts

Every read is signed and dated, so a dispute starts from the record.

What you get

Your fleet, one table, one renewal.

8 cards 5 serious, failing or flagged 54 signed reads

Our eight published cards as a fleet table
Card	Condition	Reads	Last read	Included until
···3611 A100-PCIE-40GB	Clean	14	Oct 6, 2026	Oct 20, 2026
···9659 H100 80GB HBM3	A few fixed bit flips	4	Oct 6, 2026	Oct 13, 2026
···7343 A100 80GB PCIe	Repaired, stable	5	Oct 5, 2026	Nov 11, 2026
···0230 L40S	Serious	7	Sep 30, 2026	Oct 24, 2026
···3343 A100-SXM4-80GB	Serious	7	Oct 4, 2026	Dec 12, 2026
···3197 A10	Failing	8	Sep 29, 2026	Dec 8, 2026
···7829 A10	Flagged	4	Oct 5, 2026	Dec 12, 2026
···6065 L40	Flagged	5	Oct 4, 2026	Nov 25, 2026

Our eight published cards, as they would sit in your table. Included until is the first read plus 100 days.

day 0 First read

100 days included
day 100 Renew once a year, one invoice for the fleet

Tracked
day 465 Not renewed

Stopped: the record stays, the gap shows
Renewed

Tracking resumes

How it runs

A scheduled read. Nothing stops.

The reader runs on a timer on your host and files each signed read. It reads at rest, through the driver's own interface, and never writes to the card, resets it or loads it. No workload stops.

What leaves the host is the signed record, and only when you submit it. The raw readings stay with you. What the reader reads

Reads are taken at rest and cover condition, not speed under load.

Start tracking We set it up with you

See pricing Fleet math in one table