Conflicting Reports on Earthquake Magnitude, Location, and Time
News outlets disagree on the details of a reported earthquake, with magnitude estimates ranging from 3.5 to 5.3 and locations spanning Tibet to Colombia.
2 reports on this incident · first at Aug 24, 2026, 2:25 a.m. ET
Earlier reports
Aug 24, 2026, 2:25 a.m. ETFirst report
Magnitude 3.5 Earthquake Strikes Near Leh, Ladakh
An earthquake of magnitude 3.5 struck near Leh, Ladakh, on August 24, 2026, at approximately 08:25:07 local time, according to bignewsnetwork.com. The quake occurred at a depth of 120 kilometers, the report said.
The event was reported as an earthquake hazard by bignewsnetwork.com. No further details were immediately available.
Was this report accurate and useful?
Sources
- Ladakh: Earthquake of magnitude 3.5 strikes Lehbignewsnetwork.com
- 5.1 Magnitude Earthquake Hits Sichuandeccanchronicle.com
- Earthquake of magnitude 5.1 strikes Tibet days after flood tragedyhindustantimes.com
- Magnitude 5.3 earthquake hits Tibet, tremors felt in Nepal days after destructive floodshindustantimes.com
- 5.0-magnitude earthquake strikes Tibet as rescue efforts continue after Nepal glacier disaster | Indiablooms - First Portal on Digital News Managementindiablooms.com
- Magnitude 5.3 Earthquake Strikes Afghanistan’s Badakhshan - Khaama Presskhaama.com
- Sikkim: Earthquake of magnitude 3.9 strikes Mangan Districtnepalnational.com
- 5.1 magnitude earthquake strikes Colombianzherald.co.nz
- 4.1-Magnitude Earthquake Jolts Guwahatisentinelassam.com
- Magnitude 5 earthquake hits Tibet, hundreds of miles north of Himalayan floodstraitstimes.com
- Magnitude 5 earthquake hits Tibet, hundreds of miles north of Himalayan floodyahoo.com
Revision history
- Version 98 Sept 2026, 17:58current
Updated to reflect the latest conflicting reports on magnitude, depth, location, and time.
- Version 88 Sept 2026, 08:22
Updated to include all reported magnitudes, depths, locations, and times with attribution, and noted the automatic magnitude status.
- Version 73 Sept 2026, 12:56
Updated to include all conflicting reports on magnitude, depth, and location, and added the automatic magnitude status.
- Version 63 Sept 2026, 09:55
Conflicting Reports on Earthquake Magnitude, Depth, and Location
- Version 51 Sept 2026, 00:17
Updated to reflect conflicting reports on magnitude, depth, and location.
- Version 427 Aug 2026, 17:52
Updated to reflect conflicting reports on magnitude, depth, and location.
- Version 326 Aug 2026, 22:15
Added nzherald.co.nz as a conflicting source for magnitude and location.
- Version 225 Aug 2026, 10:14
Updated to reflect conflicting reports on magnitude, depth, and location; removed previous revision language.
- Version 124 Aug 2026, 06:31
First published.
- Version 124 Aug 2026, 06:25current
First published.
How we work
This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.
Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.
Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.
None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.