Earthquake record › what the record changed

What the USGS Record Changed After Publication

Events USGS revised in place after we had already sealed them — both values, and the date of each.

Read the denominator first. A revision can only be seen in an event we sealed more than once. The feed is a rolling 24-hour window and we seal once a day, so only events near a seal boundary are ever re-read: 10,570 of 10,736 events appear in exactly one seal. The comparable population is 166 events, and every figure on this page divides by that.

What this archive is, exactly. The USGS all_day feed holds the last 24 hours and is overwritten in place. We seal one dated copy of it per day. An event that appeared in the feed and was superseded between two of our seals is not in this archive at all. These pages are a record of what USGS asserted at each seal — they are not a complete catalogue of earthquakes, and nothing here should be read as one.

Three different claims, counted separately

Claim	Events	What it means
USGS touched the record	20	the feed's own `updated` timestamp moved between our seals
A published field changed	12	we can show you the before and the after
Magnitude or review status changed	7	the subset with a downstream consequence
Re-read, nothing changed	154	the negative control: most re-reads are identical

The first row is larger than the second on purpose. USGS moving its updated timestamp tells us it rewrote the record; it does not tell us that anything we can see is different. Only the second row is a change we can demonstrate, and only the second row is counted as a revision anywhere on this site.

Revisions that crossed M3.5

A magnitude that moves across this line moves an event across the number Texas Railroad Commission seismic-response conditions are written around. We are reporting that the published value moved; we are not making a determination about any permit, operator or well.

Event, as USGS named it	Between these seals	What changed
42 km E of Pedro Bay, Alaska aka2026ppwwng	2026-08-08 → 2026-08-09 crossed the threshold	magnitude: 3.2 → 3.7 place: 45 km ESE of Pedro Bay, Alaska → 42 km E of Pedro Bay, Alaska origin time: 2026-08-08T18:01:52+00:00 → 2026-08-08T18:01:53+00:00 review status: automatic → reviewed significance: 158 → 211 longitude: -153.319 → -153.353 latitude: 59.701 → 59.74 depth (km): 134.7 → 130.7 title: M 3.2 - 45 km ESE of Pedro Bay, Alaska → M 3.7 - 42 km E of Pedro Bay, Alaska

Every revision we can demonstrate

Event, as USGS named it	Between these seals	What changed
17 km SSE of Ackerly, Texas tx2026pnoatd	2026-08-08 → 2026-08-09	place: 18 km SE of Ackerly, Texas → 17 km SSE of Ackerly, Texas longitude: -101.606 → -101.614 latitude: 32.392 → 32.396 depth (km): 3.0405 → 4.1202 title: M 2.3 - 18 km SE of Ackerly, Texas → M 2.3 - 17 km SSE of Ackerly, Texas
42 km E of Pedro Bay, Alaska aka2026ppwwng	2026-08-08 → 2026-08-09 crossed the threshold	magnitude: 3.2 → 3.7 place: 45 km ESE of Pedro Bay, Alaska → 42 km E of Pedro Bay, Alaska origin time: 2026-08-08T18:01:52+00:00 → 2026-08-08T18:01:53+00:00 review status: automatic → reviewed significance: 158 → 211 longitude: -153.319 → -153.353 latitude: 59.701 → 59.74 depth (km): 134.7 → 130.7 title: M 3.2 - 45 km ESE of Pedro Bay, Alaska → M 3.7 - 42 km E of Pedro Bay, Alaska
12 km N of Ocotillo Wells, CA ci40660106	2026-07-23 → 2026-07-24	magnitude: 1.65967180482867 → 1.59 review status: automatic → reviewed significance: 42 → 39 longitude: -116.122665405273 → -116.125666666667 latitude: 33.252498626709 → 33.2535 depth (km): 7.78000020980835 → 7.65 title: M 1.7 - 12 km N of Ocotillo Wells, CA → M 1.6 - 12 km N of Ocotillo Wells, CA
26 km NNW of Mianzhu, Deyang, Sichuan, China us6000taaa	2026-07-05 → 2026-07-06	significance: 387 → 388
33 km WSW of Ackerly, Texas tx2026ndbxhg	2026-07-05 → 2026-07-06	magnitude: 1.0 → 1.1 review status: automatic → reviewed significance: 15 → 19 longitude: -102.042 → -102.044 latitude: 32.398 → 32.403 depth (km): 4.6886 → 8.7646 title: M 1.0 - 33 km WSW of Ackerly, Texas → M 1.1 - 33 km WSW of Ackerly, Texas
36 km SSW of Los Ybanez, Texas tx2026nczjul	2026-07-05 → 2026-07-06	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
12 km ESE of Gilroy, CA nc75390006	2026-07-05 → 2026-07-06	significance: 139 → 138
21 km ENE of Little Lake, CA ci41287527	2026-07-05 → 2026-07-06	review status: automatic → reviewed
33 km WSW of Trapper Creek, Alaska aka2026nfefty	2026-07-05 → 2026-07-06	significance: 74 → 75
120 km S of Isangel, Vanuatu us6000t7lb	2026-06-23 → 2026-06-24	place: 126 km S of Isangel, Vanuatu → 120 km S of Isangel, Vanuatu origin time: 2026-06-23T13:58:36+00:00 → 2026-06-23T13:58:34+00:00 longitude: 169.1101 → 169.2307 latitude: -20.6721 → -20.6302 depth (km): 30.168 → 21.543 title: M 5.3 - 126 km S of Isangel, Vanuatu → M 5.3 - 120 km S of Isangel, Vanuatu
2 km E of Winchester, CA ci41493320	2026-06-23 → 2026-06-24	review status: automatic → reviewed
7 km N of Beaumont, CA ci41493296	2026-06-23 → 2026-06-24	magnitude: 0.65 → 0.54 review status: automatic → reviewed significance: 6 → 4 longitude: -116.967 → -116.971833333333 latitude: 33.9901666666667 → 33.9915 depth (km): 8.77 → 9.04 title: M 0.7 - 7 km N of Beaumont, CA → M 0.5 - 7 km N of Beaumont, CA

Which fields moved

Field	Events
significance	8
depth (km)	7
latitude	7
longitude	7
review status	7
title	7
magnitude	5
place	3
origin time	3

Why you cannot rebuild this yourself. USGS serves the current value of an event and nothing else. Once a magnitude is revised, the earlier one is not available from the feed, from ComCat, or from the event page — it is only in a copy somebody sealed before the change. That is what this table is made of, and it is why the deeper it gets the less reproducible it becomes.

Days we did not seal. 46 seals span 48 calendar days, so these days inside the span have no sealed copy: 2026-07-04, 2026-07-15. A missing day means we did not read the feed. It does not mean nothing happened, and those dates return a 404 here rather than a page reading zero.

One seal is wider than the others. These dates were collected more than once: 2026-07-16 (2 runs, 00:48 and 13:42 UTC). A day with two runs covers more than 24 source-hours, so its event count is larger for a collection reason and not a seismic one. Do not read it as a busy day.

Get told when the record changes for your area

USGS publishes the last day and overwrites it, then revises events in place — automatic becomes reviewed, magnitudes move, and the old value stops existing everywhere. We seal a dated copy every day. Leave your email and we'll tell you when an event in your area is revised after the fact, with what it said before.

Email me revisions in my area →

Work email only. No newsletter, no obligation.

Prefer to just buy it? See the custom, source-cited close file, priced, with a sample deliverable.

Compiled from dated copies of the U.S. Geological Survey's public all_day realtime feed (a work of the US government, in the public domain). Values are reproduced exactly as USGS published them on the date shown and may since have been revised; USGS is the authority on the current value of any event. These pages are provided for informational purposes only, carry no warranty of accuracy or completeness, and are not an earthquake warning, a safety notice, or engineering advice. Always verify against the USGS Earthquake Hazards Program before relying on any figure.

Earthquake record home · What the record changed · How this is collected · US Tech Automations.