ΛRC Open Governance ARC Grid — Central Sierra

Regional Hazard View — Central Sierra

Data: The Grid — Sierra Grid Team · data.sierragridteam.org — a public, keyless data service. Every event on this page carries the source's own provenance.

Snapshot: 2026-10-24T23:40:27.542Z Events in frame: 64. Newest ingested: 2026-10-24T23:33:10.306234979Z. Health: OK.

The map — the region, from the feed

County fill = the feed's situation mode (QUIET slate · WATCH amber · ACTIVE red; Mono hatched = NOT COVERED by the source). Markers plot only where the API itself publishes a position; ▦ badges count events the API places by county without a position — they are listed below, never pinned by invention. Drag to pan, pinch or use + / − to zoom, ⤢ takes the map full-screen.

Mesh glyphs: ▲ repeater — relays traffic for other nodes · ■ room server — hosts message rooms · ◆ companion — a personal radio · ● sensor / other events — dots are sized by the severity the API assigns. A mesh node's position is the location the node itself advertises, as published by the feed — a point, not an area outline.

Mesh nodes in frame: 17 — repeater 14 · room server 3 — each plotted at the position it advertises, as the feed publishes it.

Connections: the feed publishes no who-heard-whom radio links, and no event in it carries a packet path (the documented path fields arrive empty). What it does publish: each mesh node's record names the internet bridge gateways that reported it — in this snapshot, 511 references naming 42 distinct gateways; 23 of the distinct gateways are themselves nodes in the wider feed — all outside this six-county frame — and 19 are bridge identities the feed does not publish as nodes. No connection lines are drawn: a line on this map needs both ends on it — a node and a reporting gateway that is itself a positioned node inside this frame — and in this snapshot there are none.

Layers & filters

County Severity Status

Snapshot age: — · Reload fetches the newest published snapshot — this page is a snapshot, not a live stream, and says so.

County briefs & event detail

Area brief — the frame

Tuolumne County — mode QUIET · evacuations: 0 active, status OK · events in frame: 5

Alpine County — mode ACTIVE · evacuations: 0 active, status OK · events in frame: 12

Calaveras County — mode WATCH · evacuations: 0 active, status OK · events in frame: 35

Mariposa County — mode QUIET · evacuations: 0 active, status OK · events in frame: 2

Stanislaus County — mode QUIET · evacuations: 0 active, status OK · events in frame: 10

Mono County — mode NOT COVERED · evacuations: unknown (not covered) · events in frame: unknown

Select a county on the map for its full brief — mode, per-domain status, source freshness. Select any event, on the map or in the list, for its full provenance card. Modes are the feed's own situation vocabulary (QUIET / WATCH / ACTIVE), never our judgment.

Event list (64)

The watch — ARC Mesh 001 in the public mesh feed

Every snapshot checks the standing watch: has any bridge-connected gateway published our node (MeshCore key prefix afa21e5e…) into the public mesh feed? Source of this reading: the standing feed-watch record (full sweeps).

State: NOT YET PUBLISHED — not yet published by any bridge-connected gateway — silence is not proof of absence.

The watch sweeps the feed's mesh layer in full: 573 events across 6 pages at 2026-10-24T22:43:49.665Z, key prefix afa21e5e… — no match. The feed's direct read for our key answers not found (404) — the same answer the feed gives for any node no bridge has published yet.

Presence, when it comes, will be machine-grade: the feed itself reporting our node. Absence proves nothing in either direction, and this page claims neither. Our node never appears on the map above: ARC publishes no position for it — it is watched for here, not pinned there.

One mesh, two systems — the demonstration

ARC's node and this data service run on the same mesh technology. This panel is the demonstration, graded the way we grade everything: each claim at exactly the strength its evidence carries — every line checkable against the public feed itself.

Same protocol, same regional profile

ARC Mesh 001 and the nodes in this feed both run MeshCore, on the published regional convention — 910.525 MHz, 62.5 kHz bandwidth, spreading factor 7. Our node's profile matches it exactly.

PROVEN — published

Data interop, working now

Everything on this page is read live from The Grid's public API — no key, no special access — and the same service's agent-protocol (MCP) interface has been exercised and verified from our side.

PROVEN — first-hand

Our node is transmitting

ARC Mesh 001 (ARC registry Node 011) sent its first MeshCore adverts and a first plain-text transmission on October 24, 2026, from Tuolumne County — witnessed at the device by the founder.

PROVEN — witnessed

Heard back — not yet

No gateway has yet published our node into the feed. Under the feed's published ingestion model — presence crosses only through a bridge-connected gateway — that is expected at this stage, and it is not evidence that no radio heard us: silence is not proof of absence. The watch panel above keeps the instrument on the page, refreshed at every snapshot.

OPEN — under test

The named path to closing the open claim is already in our test program: a standing advert cadence from Node 011, and a community-bridge path so an advert can reach a publishing gateway.

What we're testing next — VALIS on MeshCore

Governed, signed presence. Node statements on the mesh that carry the same signatures and receipts as every other ARC act.

Receipt-backed mesh acts. Anything the mesh carries for ARC leaves the same evidence trail as the rest of the network.

Custody patterns. Node keys held by their owners, on their own machines, never in transit — the pattern Node 004's account key now stands on.

A test program, stated as plans, not capabilities. Claims on this page move up a grade only when the evidence lands — the same rule the page applies to hazard data.

What ARC adds — the difference, tracked

The panel above grades the interop claims. This section tracks the difference ARC's own machinery makes on the same mesh — each difference defined only by the record that proves it, each carrying its grade on its face: LIVE (running now), IN TEST (the program is exercising it), DESIGNED (specified, not yet exercised). Every figure below recomputes from its named source when this page is fetched; nothing here is typed by hand, and nothing is graded above its evidence.

The reachability ladder — how far Node 011's advert has climbed

Consequential reachability asks how far an act travels with proof at each step. The founding record's lifecycle runs proposal → settlement → release → execution → evidence → receipt; this ladder is the program's after-the-act measurement of one act's climb, mapped onto that lifecycle — transmitted is execution seen at its origin, witnessed is independent evidence, published is the act standing where third parties read it, attested is the act bound to an identity whose validity is an exact check, settled is the act carried through settlement to a receipt.

1 · TransmittedSTANDSNode 011's advert pair and first plain-text transmission went out on October 24, 2026 (2:36–2:41 PM Pacific), witnessed at the device by the founder — the test battery's T1 record. This rung stands at founder-witnessed strength, no stronger.

2 · WitnessedOPENNo independent reception of our traffic stands anywhere yet. The first listening window closed silent, graded in the test battery as not yet witnessed at this location/conditions — a statement about that window, not about the radio. The chartered second receiving end is a listen-only ARC bridge standing in Tuolumne County.

3 · PublishedOPENOur node does not yet stand in the public feed. The standing watch has logged 1 full sweeps of the mesh feed; the latest verdict is ABSENT across 573 events. Under the feed's published ingestion model — presence crosses only through bridge-connected gateways or credentialed monitors — ABSENT is the expected grade at this stage, and it is not evidence that no radio heard us.

4 · AttestedIDENTITY — STANDS THE ACT — OPENThe node's identity stands attested — registry entry 011 of 24 entries in the registry ledger of record, admitted October 24, 2026 on a custodian attestation (attestation digest de519343…), entry hash 191a97ca… — re-walkable by anyone on the ARC Living Ledger. The advert itself binds no identity yet: plain traffic carries no signature. Binding each act to the identity is difference D2, in test below.

5 · SettledOPENNo mesh act has passed settlement: 0 stand settled, because zero stand received. The governed operations around the node — its filing, this watch, the advert cadence — each run the full settlement lifecycle under admission, with receipts (D4); the mesh acts themselves join that road when reception exists.

The contrast is the point: ARC's record acts climb with proof at every rung. Plain mesh traffic cannot climb past its first rung — nothing in it binds an identity, and nothing in it survives checking.

The five tracked differences

D1 · Reachability, measured — not declared

A node's radio act is not announced as reachable; its climb up the ladder above is measured against independent instruments, and the measurement is published on this page. Standing instruments: the feed watch (1 sweeps logged; latest verdict ABSENT), the advert cadence — 0 confirmed sends across 0 logged days in the 14-day advert cadence — zero with its reason: the run has not begun (its first day is Sunday, October 25, 2026), so no cadence log stands yet. A send will count only on the founder's confirmation — a sent time is never inferred. — and the chartered listen-only bridge as the second receiving end.

IN TEST

D2 · Statement-grade traffic, not plain traffic

Plain mesh traffic binds nothing to anyone. The ARC form is a signed beat reference — 114 bytes carried as ordinary channel data over the same dumb, untrusted transport, verified at the receiving end against the record: signature valid and digest matched, or refused and counted. The refusal battery passed in full in synthetic form (5 of 5 core cases, 3 of 3 supplementary); live carriage waits on a second ARC-controlled endpoint. Verified signed beat receipts on the live record: 0 — zero because no receiving end stands yet, printed as zero with its reason.

IN TEST

D3 · An evidence chain, custody at each hand

Node 011's filing: a custody record → a custodian attestation → a registration that verified (or would have stood refused) → registry entry 011 of 24 entries in the registry ledger of record, admitted October 24, 2026 on a custodian attestation (attestation digest de519343…), entry hash 191a97ca… — re-walkable by anyone on the ARC Living Ledger. Every registry verification pass revalidates the attestation, so the chain is re-walked, not remembered. Each hand is named, signed, or attested — the difference from a database row.

LIVE

D4 · Governed machine work, with receipts

The machinery around this mesh admits every consequential act before it acts and receipts it after — no unattended scripts, no self-approval. Standing specimens: Node 011's filing itself; this feed watch (1 governed sweeps on the log); the advert cadence (0 confirmed sends across 0 logged days in the 14-day advert cadence — zero with its reason: the run has not begun (its first day is Sunday, October 25, 2026), so no cadence log stands yet. A send will count only on the founder's confirmation — a sent time is never inferred.); and this page's own build, run under the same admission discipline.

LIVE

D5 · Records a government can rely on

The requirement class: a statement whose validity is an exact check anyone can recompute; one hash-linked chain a reviewer walks without trusting whoever presents it; registrations that verify or stand refused; presence counted only from verified beats; custody named at each hand; retention on the record, not in someone's outbox. The underlying machinery is live at registry scope (D3, D4); the mesh field-report form is the specimen below — designed, not yet exercised.

DESIGNED

The emergency-response specimen

A field report's road to the public record

The worked path, on our node and our traffic only: (1) a field report originates on Node 011; (2) it is signed at origin in the D2 form, bound to the node's identity; (3) a second ARC-controlled end receives it and files the receipt — the bridge in its listen-only phases, whose gate stands shut: hearing is one act, publishing is another, and nothing heard enters any external network under this design; (4) the verified report is restated as a signed statement in the registry's statement form; (5) the statement enters the registry ledger on the one recomputable chain, custody named at each hand; (6) anyone — an emergency manager, an insurer, a resident — re-walks the whole path on the public record and recomputes each link, trusting no one presenting it.

Open rungs, named: the report content standard; a live signing path on the radio; any receiving end standing at all; and the statement filing for mesh reports. Steps 5–6 stand on machinery already live at registry scope. This specimen has not been run; it is a design, graded as one.

DESIGNED

Sources, named: the test battery's T1 record; the standing feed-watch log; the ARC registry ledger of record; the advert cadence log; the mesh program's charters (the bridge charter, the cadence plan, the test battery). Grades per the tracked-differences framework in the build's evidence record.

Evacuation invariant (fail-loud)

County	Active evacuations	Evacuation status	Area mode	Events
Tuolumne County	0 reported (per Cal OES, via the API summary)	OK	QUIET	5
Alpine County	0 reported (per Cal OES, via the API summary)	OK	ACTIVE	12
Calaveras County	0 reported (per Cal OES, via the API summary)	OK	WATCH	35
Mariposa County	0 reported (per Cal OES, via the API summary)	OK	QUIET	2
Stanislaus County	0 reported (per Cal OES, via the API summary)	OK	QUIET	10
Mono County	NOT COVERED — the API has no such place; state unknown from this source	unknown	unknown	unknown

Evacuation data is reference only; the API surfaces the presence of orders from Cal OES and never asserts an area is safe. A count of UNKNOWN means the feed did not answer — it is never read as zero.

What changed since the last snapshot

No earlier snapshot stands on record for this view, so no diff can be computed. The next snapshot will diff against this one, revision by revision.

Full record — every event, with its provenance (64 events)

SEVERE · WILDFIRE · ACTIVE — Willow — 0 ac

Location: county:alpine-county · Event id: firis:willow · Category: wildfire

Observed: unknown · Ingested by the API: 2026-10-20T22:02:58.392385171Z (data age at snapshot: 4 d 1 h old) · Revision: 1

Provenance: CAL FIRE / FIRIS · Attribution: CAL FIRE / FIRIS / NIFC · Source fetched at: 2026-10-20T22:02:58.345445768Z

SEVERE · ROAD_INCIDENT · ACTIVE — Hwy 26 full closure (Roadway Excavation)

Location: Hwy 26 from Route 49 Mokelumne Hill to Main Street (Left) · Event id: caltrans:C26EA-1-bfa4ac · Category: closure

Observed: 2026-10-09T08:58:03Z · Ingested by the API: 2026-10-09T09:02:13.088026741Z (data age at snapshot: 15 d 14 h old) · Revision: 49

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-09T09:02:01.394325006Z

Closed: all lanes (of 2 lanes).

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 88 one-way traffic control (ITS/Various Electrical Works)

Location: Hwy 88 at Schneidr Road (Left), near Markleeville · Event id: caltrans:d10-C88EA-0011-2026-10-30-070100 · Category: closure

Observed: 2026-10-23T14:03:04Z · Ingested by the API: 2026-10-23T14:08:13.051088913Z (data age at snapshot: 33 h 32 min old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-23T14:08:12.550307899Z

Closed: lane 1, right shoulder (of 2 lanes).

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 26 one-way traffic control (Drainage Work)

Location: Hwy 26 from Higdon Road (Left) to North Fork Mokelumne River Bridge, near West Point · Event id: caltrans:d10-C26GA-0005-2026-10-30-070100 · Category: closure

Observed: 2026-10-23T14:03:04Z · Ingested by the API: 2026-10-23T14:08:12.789509122Z (data age at snapshot: 33 h 32 min old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-23T14:08:12.550200632Z

Closed: left shoulder, lane 1, right shoulder (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 26 one-way traffic control (Utility Work)

Location: Hwy 26 from Prindle Road (Right) to Church Street, near Mokelumne Hill · Event id: caltrans:d10-P26FA-0006-2026-10-30-070100 · Category: closure

Observed: 2026-10-23T14:03:04Z · Ingested by the API: 2026-10-23T14:08:13.376447198Z (data age at snapshot: 33 h 32 min old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-23T14:08:12.550647927Z

Closed: left shoulder, lane 1, right shoulder (of 2 lanes). Estimated delay: 2 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 88 one-way traffic control (Drainage Work)

Location: Hwy 88 from Woods Lake Road (Right) to Meiss Meadows Entrance, near Markleeville · Event id: caltrans:d10-C88QA-0005-2026-10-30-063000 · Category: closure

Observed: 2026-10-23T13:33:04Z · Ingested by the API: 2026-10-23T13:38:14.158093793Z (data age at snapshot: 34 h 2 min old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-23T13:38:12.959569806Z

Closed: lane 1 (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 4 one-way traffic control (Grinding and Paving)

Location: Hwy 4 from San Joaquin/Stanislaus County Line to Hoods Creek, near Farmington · Event id: caltrans:d10-C4NB-0010-2026-10-29-190100 · Category: closure

Observed: 2026-10-23T02:03:03Z · Ingested by the API: 2026-10-23T02:08:14.103206545Z (data age at snapshot: 45 h 32 min old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-23T02:08:11.266252543Z

Closed: lane 1 (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 49 one-way traffic control (Survey Work)

Location: Hwy 49 from Mokelumne River, Calaveras/Amador County Line to Swett Road, near Mokelumne Hill · Event id: caltrans:d10-P49RB-0002-2026-10-27-060100 · Category: closure

Observed: 2026-10-22T22:43:03Z · Ingested by the API: 2026-10-22T22:48:13.286449777Z (data age at snapshot: 2 d 0 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-22T22:48:13.186259936Z

Closed: lane 1, right shoulder (of 2 lanes).

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 49 one-way traffic control (Survey Work)

Location: Hwy 49 from Mokelumne River, Calaveras/Amador County Line to Swett Road, near Mokelumne Hill · Event id: caltrans:d10-P49RB-0003-2026-10-28-060100 · Category: closure

Observed: 2026-10-22T22:43:03Z · Ingested by the API: 2026-10-22T22:48:13.427937006Z (data age at snapshot: 2 d 0 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-22T22:48:13.186266855Z

Closed: lane 1, right shoulder (of 2 lanes).

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 49 one-way traffic control (Survey Work)

Location: Hwy 49 from Mokelumne River, Calaveras/Amador County Line to Swett Road, near Mokelumne Hill · Event id: caltrans:d10-P49RB-0004-2026-10-29-060100 · Category: closure

Observed: 2026-10-22T22:43:03Z · Ingested by the API: 2026-10-22T22:48:13.536982823Z (data age at snapshot: 2 d 0 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-22T22:48:13.186282371Z

Closed: lane 1, right shoulder (of 2 lanes).

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 49 one-way traffic control (Survey Work)

Location: Hwy 49 from Mokelumne River, Calaveras/Amador County Line to Swett Road, near Mokelumne Hill · Event id: caltrans:d10-P49RB-0007-2026-10-26-060100 · Category: closure

Observed: 2026-10-22T22:43:03Z · Ingested by the API: 2026-10-22T22:48:13.709784515Z (data age at snapshot: 2 d 0 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-22T22:48:13.186289452Z

Closed: lane 1, right shoulder (of 2 lanes).

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 26 one-way traffic control (Roadway Excavation)

Location: Hwy 26 from Route 49 Mokelumne Hill to Church Street · Event id: caltrans:d10-C26EA-0001-2026-10-25-200100 · Category: closure

Observed: 2026-10-22T18:33:03Z · Ingested by the API: 2026-10-22T18:38:12.926395144Z (data age at snapshot: 2 d 5 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-22T18:38:12.839661947Z

Closed: lane 1 (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 49 one-way traffic control (Roadway Excavation)

Location: Hwy 49 from Route 26, Mokelumne Hill to Main Street (Mokelumne Hill) · Event id: caltrans:d10-C49GA-0001-2026-10-25-200100 · Category: closure

Observed: 2026-10-22T18:33:03Z · Ingested by the API: 2026-10-22T18:38:13.116285362Z (data age at snapshot: 2 d 5 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-22T18:38:12.839726408Z

Closed: lane 1 (of 2 lanes).

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 88 one-way traffic control (Drainage Work)

Location: Hwy 88 from Woods Lake Road (Right) to Meiss Meadows Entrance, near Markleeville · Event id: caltrans:d10-C88QA-0001-2026-10-26-063000 · Category: closure

Observed: 2026-10-22T15:33:04Z · Ingested by the API: 2026-10-22T15:38:12.586703214Z (data age at snapshot: 2 d 8 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-22T15:38:12.474963256Z

Closed: lane 1 (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 88 one-way traffic control (Drainage Work)

Location: Hwy 88 from Woods Lake Road (Right) to Meiss Meadows Entrance, near Markleeville · Event id: caltrans:d10-C88QA-0002-2026-10-27-063000 · Category: closure

Observed: 2026-10-22T15:33:04Z · Ingested by the API: 2026-10-22T15:38:12.730144115Z (data age at snapshot: 2 d 8 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-22T15:38:12.474969684Z

Closed: lane 1 (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 88 one-way traffic control (Drainage Work)

Location: Hwy 88 from Woods Lake Road (Right) to Meiss Meadows Entrance, near Markleeville · Event id: caltrans:d10-C88QA-0003-2026-10-28-063000 · Category: closure

Observed: 2026-10-22T15:33:04Z · Ingested by the API: 2026-10-22T15:38:12.831550678Z (data age at snapshot: 2 d 8 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-22T15:38:12.474976725Z

Closed: lane 1 (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 88 one-way traffic control (Drainage Work)

Location: Hwy 88 from Woods Lake Road (Right) to Meiss Meadows Entrance, near Markleeville · Event id: caltrans:d10-C88QA-0004-2026-10-29-063000 · Category: closure

Observed: 2026-10-22T15:33:04Z · Ingested by the API: 2026-10-22T15:38:12.933484301Z (data age at snapshot: 2 d 8 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-22T15:38:12.474983805Z

Closed: lane 1 (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 26 one-way traffic control (Tree Work)

Location: Hwy 26 from Andrew Lane (Left) to Main Street (Left), near Mokelumne Hill · Event id: caltrans:d10-M26CA-0004-2026-10-29-080100 · Category: closure

Observed: 2026-10-22T15:03:03Z · Ingested by the API: 2026-10-22T15:08:10.281510995Z (data age at snapshot: 2 d 8 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-22T15:08:09.976567887Z

Closed: lane 1, right shoulder (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 49 one-way traffic control (Tree Work)

Location: Hwy 49 from High School Street (Right) to George Reed Company Entracne (Left), near San Andreas · Event id: caltrans:d10-M49OA-0003-2026-10-29-080100 · Category: closure

Observed: 2026-10-22T15:03:03Z · Ingested by the API: 2026-10-22T15:08:10.415681884Z (data age at snapshot: 2 d 8 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-22T15:08:09.976637561Z

Closed: lane 1, right shoulder (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 88 one-way traffic control (ITS/Various Electrical Works)

Location: Hwy 88 at Schneidr Road (Left), near Markleeville · Event id: caltrans:d10-C88EA-0010-2026-10-29-070100 · Category: closure

Observed: 2026-10-22T14:03:03Z · Ingested by the API: 2026-10-22T14:08:14.317390957Z (data age at snapshot: 2 d 9 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-22T14:08:12.461812692Z

Closed: lane 1, right shoulder (of 2 lanes).

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 26 one-way traffic control (Drainage Work)

Location: Hwy 26 from Higdon Road (Left) to North Fork Mokelumne River Bridge, near West Point · Event id: caltrans:d10-C26GA-0004-2026-10-29-070100 · Category: closure

Observed: 2026-10-22T14:03:03Z · Ingested by the API: 2026-10-22T14:08:13.975294438Z (data age at snapshot: 2 d 9 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-22T14:08:12.461685535Z

Closed: left shoulder, lane 1, right shoulder (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 26 one-way traffic control (Utility Work)

Location: Hwy 26 from Prindle Road (Right) to Church Street, near Mokelumne Hill · Event id: caltrans:d10-P26FA-0005-2026-10-29-070100 · Category: closure

Observed: 2026-10-22T14:03:03Z · Ingested by the API: 2026-10-22T14:08:14.750422740Z (data age at snapshot: 2 d 9 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-22T14:08:12.462213623Z

Closed: left shoulder, lane 1, right shoulder (of 2 lanes). Estimated delay: 2 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 26 one-way traffic control (Utility Work)

Location: Hwy 26 from Prindle Road (Right) to Church Street, near Mokelumne Hill · Event id: caltrans:d10-P26FA-0002-2026-10-26-070100 · Category: closure

Observed: 2026-10-22T04:23:03Z · Ingested by the API: 2026-10-22T04:28:16.303505450Z (data age at snapshot: 2 d 19 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-22T04:28:12.258278900Z

Closed: lane 1, right shoulder, left shoulder (of 2 lanes). Estimated delay: 2 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 26 one-way traffic control (Utility Work)

Location: Hwy 26 from Prindle Road (Right) to Church Street, near Mokelumne Hill · Event id: caltrans:d10-P26FA-0003-2026-10-27-070100 · Category: closure

Observed: 2026-10-22T04:23:03Z · Ingested by the API: 2026-10-22T04:28:16.409324136Z (data age at snapshot: 2 d 19 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-22T04:28:12.258289570Z

Closed: left shoulder, lane 1, right shoulder (of 2 lanes). Estimated delay: 2 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 26 one-way traffic control (Utility Work)

Location: Hwy 26 from Prindle Road (Right) to Church Street, near Mokelumne Hill · Event id: caltrans:d10-P26FA-0004-2026-10-28-070100 · Category: closure

Observed: 2026-10-22T04:23:03Z · Ingested by the API: 2026-10-22T04:28:16.522050009Z (data age at snapshot: 2 d 19 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-22T04:28:12.258337652Z

Closed: left shoulder, lane 1, right shoulder (of 2 lanes). Estimated delay: 2 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 4 one-way traffic control (Grinding and Paving)

Location: Hwy 4 from San Joaquin/Stanislaus County Line to Hoods Creek, near Farmington · Event id: caltrans:d10-C4NB-0009-2026-10-28-190100 · Category: closure

Observed: 2026-10-22T02:03:03Z · Ingested by the API: 2026-10-22T02:08:13.084243472Z (data age at snapshot: 2 d 21 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-22T02:08:10.264571473Z

Closed: lane 1 (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 26 one-way traffic control (Drainage Work)

Location: Hwy 26 from Higdon Road (Left) to North Fork Mokelumne River Bridge, near West Point · Event id: caltrans:d10-C26GA-0001-2026-10-26-070100 · Category: closure

Observed: 2026-10-21T21:53:04Z · Ingested by the API: 2026-10-21T21:58:16.064975653Z (data age at snapshot: 3 d 1 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-21T21:58:11.710140220Z

Closed: left shoulder, lane 1, right shoulder (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 26 one-way traffic control (Drainage Work)

Location: Hwy 26 from Higdon Road (Left) to North Fork Mokelumne River Bridge, near West Point · Event id: caltrans:d10-C26GA-0002-2026-10-27-070100 · Category: closure

Observed: 2026-10-21T21:53:04Z · Ingested by the API: 2026-10-21T21:58:16.552339448Z (data age at snapshot: 3 d 1 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-21T21:58:11.710147455Z

Closed: left shoulder, lane 1, right shoulder (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 26 one-way traffic control (Drainage Work)

Location: Hwy 26 from Higdon Road (Left) to North Fork Mokelumne River Bridge, near West Point · Event id: caltrans:d10-C26GA-0003-2026-10-28-070100 · Category: closure

Observed: 2026-10-21T21:53:04Z · Ingested by the API: 2026-10-21T21:58:16.652003226Z (data age at snapshot: 3 d 1 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-21T21:58:11.710155487Z

Closed: left shoulder, lane 1, right shoulder (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 26 one-way traffic control (Tree Work)

Location: Hwy 26 at Lower Dorray Road (Left), near Glencoe · Event id: caltrans:d10-M26CA-0003-2026-10-27-080100 · Category: closure

Observed: 2026-10-21T21:53:04Z · Ingested by the API: 2026-10-21T21:58:16.780384633Z (data age at snapshot: 3 d 1 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-21T21:58:11.710495014Z

Closed: lane 1, right shoulder (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 49 one-way traffic control (Tree Work)

Location: Hwy 49 from High School Street (Right) to George Reed Company Entracne (Left), near San Andreas · Event id: caltrans:d10-M49OA-0001-2026-10-27-080100 · Category: closure

Observed: 2026-10-21T21:53:04Z · Ingested by the API: 2026-10-21T21:58:16.895275216Z (data age at snapshot: 3 d 1 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-21T21:58:11.710542408Z

Closed: lane 1, right shoulder (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 49 one-way traffic control (Tree Work)

Location: Hwy 49 from High School Street (Right) to George Reed Company Entracne (Left), near San Andreas · Event id: caltrans:d10-M49OA-0002-2026-10-28-080100 · Category: closure

Observed: 2026-10-21T21:53:04Z · Ingested by the API: 2026-10-21T21:58:17.002857063Z (data age at snapshot: 3 d 1 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-21T21:58:11.710559230Z

Closed: lane 1, right shoulder (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 49 one-way traffic control (Tree Work)

Location: Hwy 49 from Stockton Hill Road to Poverty Gulch Court (Right), near Mokelumne Hill · Event id: caltrans:d10-M49OA-0004-2026-10-27-080100 · Category: closure

Observed: 2026-10-21T21:53:04Z · Ingested by the API: 2026-10-21T21:58:17.098891844Z (data age at snapshot: 3 d 1 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-21T21:58:11.710580070Z

Closed: lane 1, right shoulder (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 49 one-way traffic control (Tree Work)

Location: Hwy 49 from Stockton Hill Road to Poverty Gulch Court (Right), near Mokelumne Hill · Event id: caltrans:d10-M49OA-0005-2026-10-28-080100 · Category: closure

Observed: 2026-10-21T21:53:04Z · Ingested by the API: 2026-10-21T21:58:17.209967787Z (data age at snapshot: 3 d 1 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-21T21:58:11.710587839Z

Closed: lane 1, right shoulder (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 26 one-way traffic control (Utility Work)

Location: Hwy 26 at Lower Dorray Road (Left), near Glencoe · Event id: caltrans:d10-P26FA-0001-2026-10-28-080100 · Category: closure

Observed: 2026-10-21T21:53:04Z · Ingested by the API: 2026-10-21T21:58:17.450322835Z (data age at snapshot: 3 d 1 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-21T21:58:11.710671521Z

Closed: left shoulder, lane 1, right shoulder (of 2 lanes). Estimated delay: 5 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 4 lane closure (Utility Work)

Location: Hwy 4 from Allen Lane (Left), Murphys to Tanner Lane (Right) · Event id: caltrans:d10-P4LA-0001-2026-10-26-090100 · Category: closure

Observed: 2026-10-21T21:53:04Z · Ingested by the API: 2026-10-21T21:58:17.321669820Z (data age at snapshot: 3 d 1 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-21T21:58:11.710655728Z

Closed: lane 1 (of 2 lanes). Estimated delay: 5 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 88 one-way traffic control (ITS/Various Electrical Works)

Location: Hwy 88 at Schneidr Road (Left), near Markleeville · Event id: caltrans:d10-C88EA-0007-2026-10-26-070100 · Category: closure

Observed: 2026-10-21T21:23:04Z · Ingested by the API: 2026-10-21T21:28:16.640841262Z (data age at snapshot: 3 d 2 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-21T21:28:12.463586756Z

Closed: lane 1, right shoulder (of 2 lanes).

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 88 one-way traffic control (ITS/Various Electrical Works)

Location: Hwy 88 at Schneidr Road (Left), near Markleeville · Event id: caltrans:d10-C88EA-0008-2026-10-27-070100 · Category: closure

Observed: 2026-10-21T21:23:04Z · Ingested by the API: 2026-10-21T21:28:16.831312964Z (data age at snapshot: 3 d 2 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-21T21:28:12.463597324Z

Closed: lane 1, right shoulder (of 2 lanes).

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 88 one-way traffic control (ITS/Various Electrical Works)

Location: Hwy 88 at Schneidr Road (Left), near Markleeville · Event id: caltrans:d10-C88EA-0009-2026-10-28-070100 · Category: closure

Observed: 2026-10-21T21:23:04Z · Ingested by the API: 2026-10-21T21:28:17.036108180Z (data age at snapshot: 3 d 2 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-21T21:28:12.463618808Z

Closed: lane 1, right shoulder (of 2 lanes).

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 4 one-way traffic control (Grinding and Paving)

Location: Hwy 4 from San Joaquin/Stanislaus County Line to Hoods Creek, near Farmington · Event id: caltrans:d10-C4NB-0006-2026-10-25-200100 · Category: closure

Observed: 2026-10-21T16:03:03Z · Ingested by the API: 2026-10-21T16:08:16.640880143Z (data age at snapshot: 3 d 7 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-21T16:08:10.362968571Z

Closed: lane 1 (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 4 one-way traffic control (Grinding and Paving)

Location: Hwy 4 from San Joaquin/Stanislaus County Line to Hoods Creek, near Farmington · Event id: caltrans:d10-C4NB-0007-2026-10-26-190100 · Category: closure

Observed: 2026-10-21T16:03:03Z · Ingested by the API: 2026-10-21T16:08:19.219090316Z (data age at snapshot: 3 d 7 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-21T16:08:10.362976696Z

Closed: lane 1 (of 2 lanes). Estimated delay: 10 min.

MODERATE · ROAD_INCIDENT · SCHEDULED — Hwy 4 one-way traffic control (Grinding and Paving)

Location: Hwy 4 from San Joaquin/Stanislaus County Line to Hoods Creek, near Farmington · Event id: caltrans:d10-C4NB-0008-2026-10-27-190100 · Category: closure

Observed: 2026-10-21T16:03:03Z · Ingested by the API: 2026-10-21T16:08:19.443736055Z (data age at snapshot: 3 d 7 h old) · Revision: 1

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-21T16:08:10.362983871Z

Closed: lane 1 (of 2 lanes). Estimated delay: 10 min.

MINOR · ROAD_INCIDENT · ACTIVE — Collision between a white van and a motorcycle; EMS responding.

Location: 26 Mile Rd / Eastman Rd · Event id: chp:261024MR0413 · Category: incident

Observed: 2026-10-24T23:32:00Z · Ingested by the API: 2026-10-24T23:33:10.306234979Z (data age at snapshot: 7 min old) · Revision: 1

Provenance: CHP / Caltrans · Attribution: quickmap.dot.ca.gov · Source fetched at: 2026-10-24T23:33:10.268730309Z

Traffic collision involving a white van and a motorcycle at 26 Mile Road and Eastman Road. Emergency medical responders (AMR) and a CHP rider unit were dispatched. Incident reported at 4:21 PM; further updates followed. No information in the report about lanes being closed or injury severity.

CHP Incident 261024MR0413 1179-Trfc Collision-1141 Enrt Oct 24 2026 4:21PM 26 Mile Rd / Eastman Rd Oct 24 2026 4:23PM [6] 1039 AMR - Oct 24 2026 4:22PM [3] RIDER 1125 Oct 24 2026 4:21PM [1] WHI VN VS MC Information courtesy of CHP

MINOR · ROAD_INCIDENT · ACTIVE — Hwy 132 westbound lane closure (Roadway Excavation)

Location: Hwy 132 at Codoni Road/Frazine Road, near Modesto · Event id: caltrans:d10-P132HA-0003-2026-10-12-060100 · Category: closure

Observed: 2026-10-22T16:33:03Z · Ingested by the API: 2026-10-22T16:38:12.288410327Z (data age at snapshot: 2 d 7 h old) · Revision: 2

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-22T16:38:12.171619692Z

Closed: Lf Turn Ln (of 1 lane).

MINOR · ROAD_INCIDENT · ACTIVE — Hwy 49 lane closure (Roadway Excavation)

Location: Hwy 49 from Route 26, Mokelumne Hill to Main Street (Mokelumne Hill) · Event id: caltrans:C49GA-1-42a84b · Category: closure

Observed: 2026-10-09T08:58:03Z · Ingested by the API: 2026-10-09T09:02:13.720937121Z (data age at snapshot: 15 d 14 h old) · Revision: 65

Provenance: Caltrans · Attribution: cwwp2.dot.ca.gov · Source fetched at: 2026-10-09T09:02:01.394386355Z

Closed: right-turn lane, left shoulder (of 2 lanes).

INFO · BURN_STATUS · ACTIVE — Tuolumne County — no-burn day; CAL FIRE burning suspended

Location: Tuolumne County · Event id: burn:tuolumne-county · Category: burn_status

Observed: 2026-10-24T22:48:08.277481741Z · Ingested by the API: 2026-10-15T00:48:00.586825903Z (data age at snapshot: 9 d 22 h old) · Revision: 3

Provenance: County Burn Line · Attribution: County air district burn information line · Source fetched at: 2026-10-24T22:48:08.373642160Z · upstream detail

INFO · BURN_STATUS · ACTIVE — Calaveras County — no-burn day; CAL FIRE burning suspended

Location: Calaveras County · Event id: burn:calaveras-county · Category: burn_status

Observed: 2026-10-24T22:48:08.277481741Z · Ingested by the API: 2026-10-09T10:02:24.446504734Z (data age at snapshot: 15 d 13 h old) · Revision: 2

Provenance: County Burn Line · Attribution: County air district burn information line · Source fetched at: 2026-10-24T22:48:08.277496664Z · upstream detail

INFO · MESH · ACTIVE — SIERRA Lake Alpine (repeater)

Location: area:ebbetts-pass, county:alpine-county · Event id: meshcore:3cda55d3c1fe9435d18d51dfa0fc78d3dfc7580b496ff1804a168a06e629a82f · Category: repeater

Observed: 2026-10-24T00:52:11Z · Ingested by the API: 2026-10-24T00:53:11.098833408Z (data age at snapshot: 22 h 47 min old) · Revision: 41

Provenance: MeshCore Mesh · Attribution: MeshCore community mesh via gomesh.dev · Source fetched at: 2026-10-24T00:53:10.664735149Z · source · upstream detail

INFO · MESH · ACTIVE — SIERRA BigPratherMeadow (repeater)

Location: area:ebbetts-pass, county:tuolumne-county · Event id: meshcore:3d444c8b75a6b45b5e1c773deb39f131fefda7d78c4e541a9a09416a26699912 · Category: repeater

Observed: 2026-10-24T00:51:03Z · Ingested by the API: 2026-10-24T00:53:11.236931509Z (data age at snapshot: 22 h 47 min old) · Revision: 93

Provenance: MeshCore Mesh · Attribution: MeshCore community mesh via gomesh.dev · Source fetched at: 2026-10-24T00:53:10.664535403Z · source · upstream detail

INFO · MESH · ACTIVE — SIERRA Hathaway Pines (repeater)

Location: area:ebbetts-pass, corridor:hwy4-murphys-arnold, county:calaveras-county · Event id: meshcore:a30081749739257489c372a0183f5f7cfd1705eb1dc4441ae11dd30533927c71 · Category: repeater

Observed: 2026-10-24T00:36:37Z · Ingested by the API: 2026-10-24T00:53:11.446944095Z (data age at snapshot: 22 h 47 min old) · Revision: 72

Provenance: MeshCore Mesh · Attribution: MeshCore community mesh via gomesh.dev · Source fetched at: 2026-10-24T00:53:10.664170871Z · source · upstream detail

INFO · MESH · ACTIVE — SIERRA Arnold Summit (repeater)

Location: area:ebbetts-pass, county:calaveras-county · Event id: meshcore:30059adfc99019769d6ee095ed2dbf81c6cf2b640d8fafb0a2aa6249558a9656 · Category: repeater

Observed: 2026-10-24T00:35:53Z · Ingested by the API: 2026-10-24T00:53:10.901787294Z (data age at snapshot: 22 h 47 min old) · Revision: 69

Provenance: MeshCore Mesh · Attribution: MeshCore community mesh via gomesh.dev · Source fetched at: 2026-10-24T00:53:10.664195454Z · source · upstream detail

INFO · MESH · ACTIVE — SIERRA Camp Connell (repeater)

Location: area:ebbetts-pass, corridor:hwy4-arnold-bearvalley, county:calaveras-county · Event id: meshcore:ab074a85d45b976a6b7b35189d43781385a309e2dbb878cc6507687be2c3e95b · Category: repeater

Observed: 2026-10-24T00:34:47Z · Ingested by the API: 2026-10-24T00:53:13.720479788Z (data age at snapshot: 22 h 47 min old) · Revision: 64

Provenance: MeshCore Mesh · Attribution: MeshCore community mesh via gomesh.dev · Source fetched at: 2026-10-24T00:53:10.664339473Z · source · upstream detail

INFO · MESH · ACTIVE — SIERRA Columbia jwt1 (repeater)

Location: area:ebbetts-pass, county:tuolumne-county · Event id: meshcore:655ea0b218aeb164ad793709793a8dd3c84c359adfdffbfa3f824f1a79b7c8b3 · Category: repeater

Observed: 2026-10-23T22:31:29Z · Ingested by the API: 2026-10-23T22:32:11.456111806Z (data age at snapshot: 25 h 8 min old) · Revision: 39

Provenance: MeshCore Mesh · Attribution: MeshCore community mesh via gomesh.dev · Source fetched at: 2026-10-23T22:32:10.604954043Z · source · upstream detail

INFO · MESH · ACTIVE — SIERRA Lilac Park (repeater)

Location: area:ebbetts-pass, corridor:hwy4-murphys-arnold, county:calaveras-county · Event id: meshcore:a2d649457de4481afba636761b186898107959fe6f906fc9f838447b965ace71 · Category: repeater

Observed: 2026-10-23T22:31:29Z · Ingested by the API: 2026-10-23T22:32:11.606033123Z (data age at snapshot: 25 h 8 min old) · Revision: 60

Provenance: MeshCore Mesh · Attribution: MeshCore community mesh via gomesh.dev · Source fetched at: 2026-10-23T22:32:10.605880322Z · source · upstream detail

INFO · MESH · ACTIVE — SIERRA Snowshoe Lake (repeater)

Location: area:ebbetts-pass, corridor:hwy4-arnold-bearvalley, county:calaveras-county · Event id: meshcore:2cfec925b5532214b6a2b02fdefbe68c34ca1f8c7b1e2ba0a730fe01cd7c7b1c · Category: repeater

Observed: 2026-10-23T22:16:53.458752769Z · Ingested by the API: 2026-10-23T22:32:10.700331685Z (data age at snapshot: 25 h 8 min old) · Revision: 54

Provenance: MeshCore Mesh · Attribution: MeshCore community mesh via gomesh.dev · Source fetched at: 2026-10-23T22:32:10.606413698Z · source · upstream detail

INFO · MESH · ACTIVE — SIERRA Forest Meadows (repeater)

Location: area:ebbetts-pass, corridor:hwy4-murphys-arnold, county:calaveras-county · Event id: meshcore:55678f4147f9d04a32c89aa857a1fdb2b7777f3a9144fa7e63702b66081a797d · Category: repeater

Observed: 2026-10-23T21:55:04.546291518Z · Ingested by the API: 2026-10-23T22:32:11.308631264Z (data age at snapshot: 25 h 8 min old) · Revision: 75

Provenance: MeshCore Mesh · Attribution: MeshCore community mesh via gomesh.dev · Source fetched at: 2026-10-23T22:32:10.605479474Z · source · upstream detail

INFO · MESH · ACTIVE — Turlock South Repeater (repeater)

Location: county:stanislaus-county · Event id: meshcore:9d8440d60f150e03285cca4c59a24973b8ae5e8da12de6fba15d0ee61832a7cb · Category: repeater

Observed: 2026-10-23T20:04:57.651363702Z · Ingested by the API: 2026-10-23T20:05:10.830227160Z (data age at snapshot: 27 h 35 min old) · Revision: 38

Provenance: MeshCore Mesh · Attribution: MeshCore community mesh via gomesh.dev · Source fetched at: 2026-10-23T20:05:10.655508357Z · source · upstream detail

INFO · MESH · ACTIVE — Bald Mountain Solar (repeater)

Location: area:ebbetts-pass, county:tuolumne-county · Event id: meshcore:f379c1f5b0a5c4ba0ed1ba2b4eb207c21a8a3c5854931183123d589fa7adfa6f · Category: repeater

Observed: 2026-10-23T07:37:09.635184235Z · Ingested by the API: 2026-10-23T07:37:10.837653064Z (data age at snapshot: 40 h 3 min old) · Revision: 3

Provenance: MeshCore Mesh · Attribution: MeshCore community mesh via gomesh.dev · Source fetched at: 2026-10-23T07:37:10.678257015Z · source · upstream detail

INFO · MESH · ACTIVE — SIERRA Eagle One 🦅 (repeater)

Location: area:ebbetts-pass, corridor:hwy4-murphys-arnold, county:calaveras-county · Event id: meshcore:ca57b9577ee6ee8444ffaa632c1bcaab62cd1cb3f8c0d0090b55c9ded65bbb25 · Category: repeater

Observed: 2026-10-22T19:27:33Z · Ingested by the API: 2026-10-23T22:32:11.985758494Z (data age at snapshot: 25 h 8 min old) · Revision: 94

Provenance: MeshCore Mesh · Attribution: MeshCore community mesh via gomesh.dev · Source fetched at: 2026-10-23T22:32:10.605228868Z · source · upstream detail

INFO · MESH · ACTIVE — Cloud 9 (room_server)

Location: county:stanislaus-county · Event id: meshcore:c059f13be443880b1841f314cb2d15c50e0b223650e56ed3f6ef6d038a34adc4 · Category: room_server

Observed: 2026-10-22T16:17:54.269565335Z · Ingested by the API: 2026-10-22T16:18:10.942890281Z (data age at snapshot: 2 d 7 h old) · Revision: 9

Provenance: MeshCore Mesh · Attribution: MeshCore community mesh via gomesh.dev · Source fetched at: 2026-10-22T16:18:10.608699960Z · source · upstream detail

INFO · MESH · ACTIVE — Tuolumne-RS-01 (room_server)

Location: county:tuolumne-county · Event id: meshcore:9bde91a109a76584509996fef19a0a63b9f1ccaa4b46cb759b0b54457340c16b · Category: room_server

Observed: 2026-10-21T15:32:59.360091476Z · Ingested by the API: 2026-10-21T15:33:10.809634765Z (data age at snapshot: 3 d 8 h old) · Revision: 24

Provenance: MeshCore Mesh · Attribution: MeshCore community mesh via gomesh.dev · Source fetched at: 2026-10-21T15:33:10.652820897Z · source · upstream detail

INFO · MESH · ACTIVE — VLK-RS-LZ2 (repeater)

Location: county:stanislaus-county · Event id: meshcore:0d0d0d0a6c8e7711f7d6d04368629556edc73408ce00b7bc7db41777bf7bb1f2 · Category: repeater

Observed: 2026-10-14T13:39:56.599719203Z · Ingested by the API: 2026-10-14T13:40:03.690868916Z (data age at snapshot: 10 d 10 h old) · Revision: 5

Provenance: MeshCore Mesh · Attribution: MeshCore community mesh via gomesh.dev · Source fetched at: 2026-10-14T13:40:03.638826841Z · source · upstream detail

INFO · MESH · ACTIVE — Bullion Room (hello) (room_server)

Location: county:mariposa-county · Event id: meshcore:7b453bbe1fea715751f3d0844b7858e42807029fd63343eb2afd6e7cc4327ad4 · Category: room_server

Observed: 2026-10-13T11:40:41.427589309Z · Ingested by the API: 2026-10-13T11:41:03.698777339Z (data age at snapshot: 11 d 11 h old) · Revision: 21

Provenance: MeshCore Mesh · Attribution: MeshCore community mesh via gomesh.dev · Source fetched at: 2026-10-13T11:41:03.638307975Z · source · upstream detail

INFO · MESH · ACTIVE — Bullion Repeater (repeater)

Location: county:mariposa-county · Event id: meshcore:fb2fe1354c4f1df260fecb517cec905b0e2bc2214d7d302cb8582d3229ef3ed8 · Category: repeater

Observed: 2026-10-12T06:34:07.883852348Z · Ingested by the API: 2026-10-12T06:34:23.017874039Z (data age at snapshot: 12 d 17 h old) · Revision: 32

Provenance: MeshCore Mesh · Attribution: MeshCore community mesh via gomesh.dev · Source fetched at: 2026-10-12T06:34:22.963902513Z · source · upstream detail

About this data

Data: The Grid — Sierra Grid Team · data.sierragridteam.org. This page is an unprivileged read of a public API, published with source credit in the source's own provenance form. It implies no relationship, endorsement, or agreement with the Sierra Grid Team.

Coverage frame. Tuolumne, Alpine, Calaveras, Mariposa, Stanislaus and Mono counties, read through the API's own place= filter per county, merged and deduped by event id. Counts are this snapshot's window (active + scheduled events, as the API lists them by default).

Mono County, in full. Mono County is not a place the API covers (place lookup returned 404). No data is shown for it — that is a coverage gap in the source, not an all-clear for the county.

How the page is fed. This snapshot was read over the API's REST endpoints at the stamp above. The same service's agent-protocol (MCP) interface has been exercised and verified from our side; it is not the feed behind this snapshot, and the page does not pretend otherwise.

Fail-loud rules. A stale or unavailable feed shows as STALE / UNAVAILABLE — never as an all-clear. A field shown as unknown means the source did not provide it (null = unknown, never zero). A county the API does not carry shows as NOT COVERED, never as zero events. There is no live stream behind this page: it is a snapshot, republished when the feed is re-read, and its age is printed on its face.

Positions. An event plots only where the API itself publishes a position. A mesh node's position is the location the node itself advertises, as published by the feed — a point, not an area outline. Events the API places by county without a position are listed and badged, never pinned.

Connections, field by field. The feed's mesh records carry exactly one link-naming field: each node's telemetry names the internet bridge gateways that reported it. The documented packet-path fields arrive empty on every event we can read, and the feed publishes no who-heard-whom radio links — so no radio links are drawn or implied, at any zoom. In this snapshot the frame's mesh records carry 511 gateway references naming 42 distinct gateways; 23 of those gateways are themselves nodes in the wider feed, all outside this frame; 19 are bridge identities the feed does not publish as nodes; 0 resolve to another positioned node inside this frame. Lines are drawn only for that last class — both ends on the map, the link named in the node's own record.

County boundaries: cb_2024_us_county_500k (2024 TIGER/Line cartographic boundary file, counties, 1:500,000) — U.S. Census Bureau, public domain (a work of the U.S. federal government). Rings simplified with Douglas–Peucker (tolerance 0.0035°) and rounded to 0.1 SVG units for display. Boundaries are approximate — cartographic, not survey, grade.

Snapshot generated 2026-10-24T23:40:27.542Z · Data: The Grid — Sierra Grid Team · An ARC Open Governance data surface — recursive-settlement.com. Republished when the feed is re-read; the stamp is the moment of the read.