US Tech Automations

Other dated records Earthquake record archive 5 rows held

Earthquakes in Utah that USGS went back and changed

We caught USGS revising 5 Utah earthquakes after it first published them. Below is what it said the first time, what it said the second time, and both dates. Reading was switched back on by a dated decision on 23 Aug 2026, after a pause, so this list can still grow. Our newest copy is 6 Sep 2026 and a newer one may follow.

Price
Not for sale
Built for
Researchers and reporters who need what USGS said on a past day
Read
About once a day. Reading again since 23 Aug 2026.
Newest sealed read
2026-09-06

Email us about the copies we holdNo card needed to ask. We reply with what we hold.

Newest sealed read: 2026-09-06. We read this source about once a day. We hold 128 sealed runs going back to 2026-06-23.

What this page is5 rows held · newest sealed read 2026-09-06

  • We caught USGS revising 5 Utah earthquakes, out of 404 revisions we caught anywhere.
  • In Utah, the magnitude moved on 4 of them, the depth on 5, and the place on 0.
  • We hold a dated copy of 373 separate Utah events, out of 16,617 events across every region.
  • Our oldest sealed copy is 23 Jun 2026 and our newest one is 6 Sep 2026. Reading was switched back on by a dated decision on 23 Aug 2026, after a pause, so this list can still grow.
  • We hold two or more dated copies for 3,140 of 16,617 events, and a single copy for the other 13,477. Where we hold two copies you can see what changed between them; where we hold one there is nothing to compare it with. USGS publishes this history itself, including superseded versions, so we do not charge for it.

Real rows out of our sealed copies

These are rows we read out of dated copies we keep ourselves. The live source shows today only, so once a row moves, what it said before is gone from the place you would go to look.

Real revisions we caught in Utah. 5 of 5 shown; the file you buy carries all 5. Numbers are printed exactly as USGS published them, long decimals and all. We do not round, because the value USGS actually put out is the whole point of the archive. 23 Jun 2026 – 6 Sep 2026
USGS event idWhere USGS said it wasWhat USGS changedFirst readSecond read
uu8015252116 km NE of Milford, Utahmagnitude 1.95 → 2.11; depth in km 1.79 → 2.59; time it happened 2026-08-31T04:59:36+00:00 → 2026-08-31T04:59:35+00:00; and 4 more values moved31 Aug 20261 Sep 2026
uu8015405612 km NE of Milford, Utahmagnitude 2.07 → 2.02; depth in km 0.66 → 1.51; significance score 66 → 63; and 3 more values moved4 Sep 20265 Sep 2026
uu8015243116 km NE of Milford, Utahmagnitude 1.85 → 1.92; depth in km 1.71 → 1.77; significance score 53 → 57; and 2 more values moved31 Aug 20261 Sep 2026
uu8015039113 km NE of Milford, Utahmagnitude 1.36 → 1.35; depth in km 3.25 → 2.9; longitude -112.905 → -112.90683333333326 Aug 202627 Aug 2026
uu8015028116 km NE of Milford, Utahdepth in km 1.36 → 1.85; longitude -112.886166666667 → -112.884166666667; latitude 38.5121666666667 → 38.50725 Aug 202626 Aug 2026
The largest Utah events we hold a dated copy of. 12 of 373 shown. Numbers are printed exactly as USGS published them, long decimals and all. We do not round, because the value USGS actually put out is the whole point of the archive. sealed 23 Jun 2026 – 6 Sep 2026
USGS event idWhere USGS said it wasMagnitude we holdDay we sealed it
us6000tgte24 km NNE of Maeser, Utah3.130 Jul 2026
uu801475216 km NNW of Saratoga Springs, Utah2.868 Aug 2026
uu801471119 km N of New Harmony, Utah2.785 Aug 2026
uu8014330612 km E of Millville, Utah2.5925 Jun 2026
uu8014860116 km NE of Milford, Utah2.5613 Aug 2026
uu8015391117 km NE of Milford, Utah2.523 Sep 2026
uu801541167 km NE of Hildale, Utah2.44 Sep 2026
uu8015399116 km NE of Milford, Utah2.373 Sep 2026
uu8015101617 km NE of Milford, Utah2.2628 Aug 2026
uu801484715 km E of Mount Pleasant, Utah2.2613 Aug 2026
uu8015035616 km NE of Milford, Utah2.1725 Aug 2026
uu801471968 km SSW of Randolph, Utah2.146 Aug 2026

What this page cannot tell you

  • We can only show a change between two of our own reads. USGS can revise an event whenever it likes, so if it changed a number and changed it back between two of our reads, we never saw it and it is not on this page.
  • Each file we saved holds the last 24 hours of events, and our runs were about 24 hours apart, so two copies sealed on consecutive days usually share no event at all: only 19 of our 67 consecutive day pairs had one in common. A before and an after exists only where two runs landed closer together than usual.
  • 13,477 of the 16,617 events we hold were caught on one day only. There is no second reading to compare them with, so they cannot show a revision.
  • We ran on 14 Aug 2026, 15 Aug 2026, 16 Aug 2026, 17 Aug 2026 and the feed gave us nothing back, so there is no copy for those days. We say that rather than skipping over it.
  • 4 days inside our range have no run at all: 4 Jul 2026, 15 Jul 2026, 22 Aug 2026, 23 Aug 2026.
  • We hold what USGS published. We are not saying which reading is right. The current catalogue keeps only the later one.
  • The region on this page is read off the place text USGS itself writes, such as “16 km NE of Milford, Utah”. We do not put an event in a region USGS did not name.

See the file we hold

You do not have to take our word for what is in the file. Here are 25 rows of the real thing, carrying all 7 of its columns, cut out of the dated copies we sealed ourselves. Nothing in it is made up and nothing in it is tidied up.

  • Open the 25 rows as a CSVA plain spreadsheet file. It saves to your machine rather than painting itself into a browser tab, and it opens in Excel, Numbers or Google Sheets.
  • The same 25 rows as JSONThe same rows again, laid out for reading with code.

Nothing on this page is for sale. The sample file is free to read, and so is every row on the page above it.

These 25 rows are a slice of the file, not the whole of it. What we cannot show you here is how far back it goes: the file goes back further than these rows do.

Ask what we hold for a named event

No pay button on this one yet. Email operations@ustechautomations.com. We reply with what we hold for this one, and with what we do not hold, before you spend anything.

What you would be paying for: Not for sale. USGS publishes this history itself, superseded versions included, so there is nothing here to charge for. Email us an event id and we tell you which dated copies we hold for it, at no charge. A person emails you the sealed copies we hold for the event you name, with the date we sealed each one. No payment is involved.

Email us about the copies we hold

Say that you want Utah earthquake revisions and we will tell you which weeks we hold for it and since when.

More from this feed