Two Earthquakes, One MBG Seismic Status Standard

MBG Watch · 2026-10-04

The premise

On 3–4 October 2026, Indonesia had two material seismic signals on opposite sides of the archipelago.

Near Sumba, the USGS recorded an M5.9 earthquake 39 km west-southwest of Tambolaka at 22:55:55 UTC on 3 October, at 9.567°S, 118.908°E and 46.0 km depth. GDACS classified the event as a low-humanitarian-impact earthquake: M5.9, 46 km depth, 130,000 people exposed in MMI V, inserted at 23:14 UTC.

BMKG’s public release gives the operationally more local account: a tectonic earthquake initially reported as M6.1 and updated to M5.9 struck the southwest coast of Sumba Barat Daya at 05:55:52 WIB on 4 October, did not have tsunami potential, and was associated with shallow fault activity likely related to the Waikabubak fault system. BMKG reported VI MMI shaking in Kodi Balaghar, Kodi Bangedo, and Kodi; IV MMI in Tambolaka, Waikabubak, Waibakul, and Raba; III MMI in Bima; damage to houses and school facilities in Desa Perokonda; at least 62 aftershocks by 08:05 WIB; and one light injury in preliminary reporting.

Near Aceh, the USGS event page viewed for this piece listed an M5.3 earthquake 81 km south-southwest of Banda Aceh at 23:37:34 UTC on 3 October, at 4.825°N, 95.162°E and 56.3 km depth. Earlier automated summaries and local reporting carried higher parameters — M5.6 to M5.8 — which is normal in the first hours after an earthquake as agencies revise magnitude, location, and depth. RRI Takengon reported that an M5.8 Aceh earthquake was felt from central Aceh to Banda Aceh, alongside a BMKG Aceh weather notice warning of possible moderate rain and high waves in the Indian Ocean.

The record I found does not show an MBG failure. It shows a gap in public operating evidence.

What the evidence supports

The Sumba event crossed the threshold from hazard signal to local operational concern. That does not mean every service should stop. It means a meal program with kitchens, delivery routes, school handoffs, water dependence, cold-chain needs, and vulnerable recipients should be able to say what was checked.

The strongest public evidence supports four points.

First, the Sumba shaking was not merely distant instrumentation. BMKG reported VI MMI shaking in parts of Kodi and damage to houses and school facilities in Desa Perokonda. RRI later quoted the Sumba Barat Daya BPBD head saying community activity in Desa Perokonda was gradually returning to normal, while preliminary impact included one light injury, 27 lightly damaged houses, and nine lightly damaged public facilities, including a hospital, puskesmas, and school building.

Second, the Sumba event had aftershock conditions. BMKG reported at least 62 aftershocks by 08:05 WIB, with magnitudes from M1.5 to M4.3. That matters for kitchens because the risk is not only the first shock. It is staff returning to a cracked building, a delivery team using a compromised route, a school receiving meals while deciding whether rooms are safe, or a kitchen drawing water from a disrupted supply.

Third, the Aceh event was felt across a wide area but, in the sources retrieved here, did not yet show a comparable public damage record. RRI’s Aceh item emphasized that shaking was felt as far as Banda Aceh, that people should use verified BMKG information, and that weather and marine conditions also needed monitoring. It did not report school, kitchen, road, water, power, or MBG disruption.

Fourth, I found no BGN or MBG-specific operating notice for either affected area in the public sources retrieved for this piece. That silence should not be converted into a claim that meals were disrupted. It should be treated as the accountability problem itself: the public cannot distinguish “checked and normal” from “not checked,” “checked but unpublished,” or “unknown.”

What the evidence does not support

The evidence does not support calling this a national MBG crisis.

It does not support a broad program pause. GDACS’ Sumba page described low expected humanitarian impact. USGS listed green alert status for the Sumba event in its event data, and the Aceh event page viewed later had revised parameters below the first signal. None of that removes the need to check kitchens, routes, and schools, but it argues against treating the earthquakes as proof of meal-system failure.

The evidence also does not support assuming that a damaged school building automatically means an MBG delivery failure. A school can have damage in one room and still receive meals elsewhere. A kitchen can keep operating while one route is restricted. A route can pause while substitute feeding is arranged. The missing piece is a status record fine-grained enough to separate those cases.

Nor does the evidence support treating “green” as “nothing to record.” Green is a disaster-impact classification. MBG needs an operating-status classification. Those are related, but they are not the same thing.

Why green earthquakes still matter to MBG

MBG is a dispersed physical service. It is not only a budget line or a menu. On any service day it depends on:

That is why MBG Watch’s earlier seismic pieces asked for local trigger records after Flores, Ruteng, the Indonesia–Timor arc, and Kepulauan Seribu. This piece is the national version of the same argument. When two earthquakes appear close together on opposite sides of the country, the question is not whether Jakarta should command a blanket shutdown. The question is whether BGN can produce a same-day, comparable record from the affected service areas.

A national program needs national comparability without pretending every district faces the same event.

The status standard BGN should publish

BGN does not need to publish private household information or children’s names. It needs a small public operating ledger, by kitchen or service area, with one status per affected area and a timestamp.

The statuses should be plain:

  1. Checked / no change — kitchen, route, water, power, and receiving points checked; service continued as normal.
  2. Checked / restricted — service continued with named limits, such as one route avoided, one school moved to outdoor handoff, or one kitchen zone kept out of use.
  3. Substituted — normal hot-meal delivery was replaced by safe substitute feeding, emergency rations, alternate pickup, or another temporary arrangement.
  4. Paused — service paused for a defined area and reason, with next review time.
  5. Emergency feeding — MBG assets or vendors were redirected to shelter or emergency feeding, with safeguards against taking meals away from scheduled beneficiaries without a replacement plan.
  6. Unknown / pending verification — the honest status when contact has not yet been made or checks are incomplete.

Each line should answer six questions:

For Sumba Barat Daya, the public trigger should have been automatic once BMKG reported VI MMI shaking, aftershocks, and damage to houses and school facilities in Desa Perokonda. For Aceh, the proportional trigger is lighter: felt shaking across several areas and possible weather/marine complications justify a checked/no-change or unknown record, not an implied disruption.

What to watch next

The next evidence that would change the MBG reading is not another headline saying “earthquake.” It is operational evidence.

The important signals are:

If none of those appear, the right public record is still not silence. It is a same-day “checked/no change” ledger.

What I am uncertain about

The largest uncertainty is MBG-specific operating status in Sumba Barat Daya and Aceh. I found public hazard records, BMKG impact statements, and local reporting, but not a BGN operating note saying which MBG kitchens or routes were checked.

The second uncertainty is parameter reconciliation for the Aceh event. The first signal described an M5.6 earthquake south of Banda Aceh; RRI’s local item carried M5.8; the USGS event page viewed for this piece had revised the event to M5.3, 81 km SSW of Banda Aceh, 56.3 km depth. The operational conclusion does not depend on choosing the largest number. Felt shaking was enough to justify a visible check; the absence of retrieved damage evidence argues against presuming disruption.

The third uncertainty is whether any internal BGN or local-government checks occurred but were not public. They may have. If they did, publishing the status format above would turn internal diligence into public accountability without increasing panic.

The least-harm path is narrow: no alarm, no blanket shutdown, no inference from silence. Just a national seismic operating-status standard that lets the public see, on the same day, whether MBG service in affected areas was normal, restricted, substituted, paused, redirected to emergency feeding, or still unknown.

Sources

  1. M 5.9 - 39 km WSW of Tambolaka, Indonesia — USGS time, location, magnitude, coordinates, and depth for the Sumba/Tambolaka event
  2. Overall Green Earthquake in Indonesia on 03 Oct 2026 22:55 UTC — GDACS low-impact classification and exposed population for the Sumba event
  3. Gempa Sumba Barat Daya Tak Berpotensi Tsunami, BMKG Imbau Warga Waspadai Bangunan Retak — BMKG local parameters, tsunami assessment, intensity, aftershocks, damage, and public safety advice for Sumba Barat Daya
  4. Aktivitas Warga kembali Normal usai gempa di Sumba Barat Daya — BPBD Sumba Barat Daya reporting on normalizing activity, light injury, light damage to homes, and public facilities
  5. M 5.3 - 81 km SSW of Banda Aceh, Indonesia — USGS updated parameters for the Banda Aceh-area event
  6. Gempa Magnitudo 5,8 Guncang Aceh, Getaran Dirasakan hingga Banda Aceh — Local reporting that Aceh shaking was felt from central Aceh to Banda Aceh and that official BMKG information should be monitored
  7. Gempa M 6,1 Guncang Kodi Sumba Barat Daya, Tak Berpotensi Tsunami — Contemporaneous report of BMKG's initial Sumba magnitude, time, location, and no-tsunami statement