This post measures one property of the reports behind the coverage board: how many days pass between the date a report covers and the date the issuer's document carries. Every date below is the document's own, read from the reports ReserveBeat has captured for each tracked stablecoin. Nothing here is a judgment of any issuer's solvency.
The short answer
Across the 60 reports on file with a recorded issue date, the gap runs from 21 to 32 days. The shortest gaps are 21 days: Circle's November 2024 and November 2025 USDC reports and the November 2025 RLUSD report. The longest is 32 days: Circle's August 2025 USDC report, which covers 2025-08-29 and is dated 2025-09-30. USD1's April 2026 report was earlier held with no issue date because the parser did not extract one; its parsed record was corrected by restatement, and the document is dated 2026-05-28.
| Token | Reports on file with an issue date | Lag range, days | Latest report | Lag of the latest report, days |
|---|---|---|---|---|
| PYUSD | 8 | 23–27 | 2026-08 | 24 |
| RLUSD | 12 | 21–29 | 2026-07 | 27 |
| USD1 | 4 | 27–31 | 2026-07 | 27 |
| USDC | 23 | 21–32 | 2026-07 | 27 |
| USDG | 5 | 24–29 | 2026-07 | 26 |
| USDT | 2 | 30–31 | 2026-06 | 31 |
| USDtb | 6 | 26–28 | 2026-07 | 28 |
Each token's page lists the reports behind its row, for example USDC or USDT.
July 2026: every monthly report within four days
The monthly series (PYUSD, RLUSD, USD1, USDC, USDG and USDtb; USDT reports quarterly) all covered 2026-07-31, and their July documents are dated within four days of each other:
- PYUSD, 2026-08-25 (25 days);
- USDG, 2026-08-26 (26 days);
- RLUSD, USD1 and USDC, 2026-08-27 (27 days);
- USDtb, 2026-08-28 (28 days).
The attestation calendar lists each report on file on the date its document carries, and each report has its own page, such as USDC 2026-07.
Month-end is not always the last day of the month
Lag is measured from the date the report states, not from the calendar month-end. The two are not always the same. For May 2026, the USDC, PYUSD, RLUSD and USDG reports cover 2026-05-29, a Friday. The USD1 and USDtb reports cover 2026-05-31.
Some reports carry two as-of dates
The July 2026 reports for PYUSD, RLUSD, USD1, USDC and USDG each state two as-of dates: one earlier in July and the month-end date. USDC's, for example, carries 2026-07-08 and 2026-07-31. ReserveBeat measures lag from the later of the two.
The quarterly series
The Tether reports on file are quarterly, and their stated scope is a consolidated group rather than one token. The March 2026 report covers 2026-03-31 and is dated 2026-04-30 (30 days). The June 2026 report covers 2026-06-30 and is dated 2026-07-31 (31 days).
Reading the same dates yourself
Every date in this post is stored with its report, and the keyless API
returns the same dates. GET /v1/board/attestations lists every report
on file with its composition_as_of and issued_on, and
GET /v1/board/coverage gives each token's publication_lag_days with the
basis it was measured on (lag_basis). The
methodology covers how a report is captured before it is
parsed.
What this does not measure
Publication lag is a fact about a document's date. It says nothing about the reserves the document describes, or about the days between two reports. It also does not measure when ReserveBeat captured a report, which is a separate figure about ReserveBeat's own pipeline.