Counted from the archive on 2026-08-08: 44 daily seals held, 2026-06-23 to 2026-08-07, covering 10354 events. 10 of the 85 events we read on more than one day were changed by USGS after publication, and 6 of those changes moved a magnitude or a review status.
The USGS all-day feed holds 24 hours and is overwritten in place, so the question "what did the public record say about this event on that date?" has no answer once the feed rolls. We have sealed one dated copy a day since 2026-06-23 and never rewritten one. Name an event or a date window and we hand you what USGS asserted at each seal we hold, and what changed between them.
$249
one-time
Request this →Checkout for this service opens by emailed invoice link. Tell us where to send it and we reply the same working day.
USGS revises earthquakes after it publishes them. Magnitudes move, epicentres move, and an automatic solution becomes a reviewed one. When that happens the earlier figure is not marked superseded anywhere public — it is simply gone, because the feed is a rolling window and the catalogue behind it serves the current value of an earthquake, never the value it carried on a past date.
If you priced a contract, filed a claim, or triggered a payout on what the record said that morning, you now have no way to show what it said. We have been sealing the feed daily since June, so we can hand you a dated file of what the authoritative source asserted on the day you acted, with the fetch time and the response hash behind each row.
An attestation is a read of what we sealed. It is not an earthquake report, not a seismological opinion, and not affiliated with USGS.
The archive holds 44 daily seals covering 2026-06-23 to 2026-08-07 and 10354 events. Of those, 85 were read on more than one day, which is the only population in which a revision can be seen at all: 10 of them changed after publication and 6 changed magnitude or review status.
10 revised out of 85 comparable, not out of 10354. An event we sealed once cannot be shown to have changed, and the feed window is 24 hours against a daily seal, so only events near the boundary are ever read twice. Dividing by the total would be a fabricated rate.
One of them: tx2026nczjul, 36 km SSW of Los Ybanez, Texas — sealed 2026-07-05, resealed 2026-07-06.
| Field | As asserted first | As asserted after |
|---|---|---|
| magnitude | 1.1 | 1.2 |
| origin time | 2026-07-05T18:07:24+00:00 | 2026-07-05T18:07:25+00:00 |
| review status | automatic | reviewed |
| significance | 19 | 22 |
| longitude | -102.12 | -102.115 |
| latitude | 32.435 | 32.438 |
| depth (km) | 3.9116 | 7.1045 |
| title | M 1.1 - 36 km SSW of Los Ybanez, Texas | M 1.2 - 36 km SSW of Los Ybanez, Texas |
You send:
You get back:
Days inside the span we did not seal, named rather than spanned: 2026-07-04, 2026-07-15.
There is no filled-in attestation here because the event is yours. The specimen above is a real event this archive caught being revised, so what the file cannot show you is only which event it will be about.
The USGS realtime summary feed is a rolling 24-hour window that is overwritten in place, and the catalogue behind it serves the current value of an event, not the value it carried last Tuesday. We seal one immutable row per event per day, so the archive holds what the authoritative source asserted on the day it asserted it. An attestation is a read of those rows. A date we did not seal is named as a gap and never spanned, because a day we did not read is not a day nothing happened.
Machine-readable offer details
US Tech Automations is a data and automation company. These are our own service terms, not a government fee, filing cost, or permit charge. Nothing on this page is legal, engineering, or financial advice.