Skip to main content
​
April 19, 2026
LocusCodexUpdate

​
Automatic detection of unresponsive data sources

The platform now detects when a data source stops returning records across multiple consecutive collection runs and flags it as failed — even if the source’s API responds without errors. Previously, a data source could go completely silent (returning zero records indefinitely) without triggering any alert, because the system only flagged runs where records were fetched but failed to persist. This change is what caught the civic and environmental review sources described below. No action is required on your part — the detection runs automatically and feeds into existing data freshness monitoring.
​
April 19, 2026
CodexLocusFix

​
Council decisions, zoning variances, and environmental reviews now populated

Three Civic Intelligence tables — council_decisions, zoning_variances, and environmental_reviews — were empty since launch because upstream data sources changed. Legistar-powered cities now use an HTML scraping fallback when the JSON API is unavailable, and California environmental reviews pull from the new CEQANet endpoint. If you query council decisions or zoning data through the Locus API or MCP server, you should now see results for cities that use Legistar (including San Francisco and New York City). EPA EIS environmental reviews are not yet available.
​
April 19, 2026
CodexFeature

​
Port authority governance dataset

Codex now includes a comprehensive governance dataset covering five major US port authorities — Oakland, Long Beach, Los Angeles, JAXPORT, and the Port Authority of New York and New Jersey. The dataset contains structured board meeting records, agenda items, claims, facts, tariff documents, and resolutions going back over a year. Each port’s records are normalized into a consistent schema so you can run cross-port queries out of the box. JAXPORT tariff data includes line-item extraction with bitemporal diffing, letting you track rate changes over time. See the full schema reference for field details and join keys.
​
April 19, 2026
CodexFeature

​
APRS envelope coverage across all datasets

All 111 Codex tables now carry the full APRS envelope — record_id, chunk_id, bitemporal fields, confidence_score, and provenance. A new compliance gate in CI ensures every table passes shape checks before deployment, so envelope coverage won’t regress. You can track current coverage on the envelope coverage dashboard.
​
April 19, 2026
LocusFeature

​
In-app support chat

Locus now has an in-app support chat. When you’re signed in, the chat verifies your identity so conversations are automatically linked to your account — meaning faster responses with no need to re-identify yourself. Anonymous chat is available for unauthenticated visitors.
​
April 19, 2026
OverwatchUpdate

​
Expanded AIS coverage area

Overwatch now tracks vessels across a much wider area around each monitored port. The default coverage radius has been expanded from approximately 55 km to 220 km, catching in-transit vessels well before they reach anchorage so your map views populate earlier. If you need full ocean tracking for use cases like dark fleet detection or open-ocean STS monitoring, you can now enable global AIS coverage. See AIS coverage for configuration details.
​
April 19, 2026
OverwatchUpdate

​
Tiered AIS data retention

Overwatch now applies structured data retention and downsampling to AIS position data. Positions from the last 7 days are kept at full resolution. Data between 7 and 30 days old is thinned to one report per vessel per minute — enough for route replay and behavioral analysis. Data older than 30 days is archived to cold storage at full resolution and can be rehydrated on request. This keeps queries fast on recent data while preserving deep history for investigations.
​
April 19, 2026
LocusUpdate

​
Landing page visual refresh

The Locus landing page has been polished with motion effects, improved card interactions, and a refreshed editorial layout including section breaks, a masthead dateline, and updated product marks across all four Axiom products.
​
April 19, 2026
CodexUpdate

​
Improved data quality for NFIP and HMDA datasets

NFIP flood claims with missing dates have been removed, cleaning up approximately 97,000 orphan records. HMDA mortgage disclosure data has been corrected to fix field-name mismatches and hash collisions that could cause duplicate records. These changes improve the reliability of queries against both datasets.
​
April 19, 2026
CodexUpdate

​
Faster APRS backfill for large datasets

HMDA loan records — previously missed during the initial backfill rollout — are now being populated with full APRS envelope metadata. Processing speed for the five largest legacy tables (EPA facilities, HMDA lending, CDC health metrics, building permits, and tax assessments) has also been increased 5x, bringing projected backfill completion from months to under 60 days. You can monitor progress on the envelope coverage dashboard.
​
April 19, 2026
CodexUpdate

​
Restored NTD transit ridership data

The National Transit Database ridership data source has been restored after the upstream API was retired by FTA. Codex now pulls directly from the official monthly data files, so transit ridership records are flowing into cell scoring again without interruption.
​
April 19, 2026
LocusFix

​
Code enforcement data collection restored

Fixed an issue where the code enforcement data collector was attempting a full refresh on every run instead of incremental updates, causing it to time out repeatedly. The collector now processes only the last 30 days of records on each run, keeping code enforcement data in cell scoring current without exceeding processing limits.
​
April 19, 2026
LocusCodexFix

​
Platform security hardening

A comprehensive security audit addressed several critical issues: API authentication now correctly rejects malformed bearer tokens, webhook endpoints enforce idempotency to prevent replay attacks, admin endpoints require proper authorization, and rate limiting no longer fails open under load. Filter parameters are validated to prevent injection. No action is required on your part — all fixes apply automatically.
​
April 19, 2026
OverwatchFix

​
More reliable global vessel tracking

Fixed an issue where enabling global AIS tracking could cause vessel processing errors. Vessels with shared or recycled MMSIs — and vessels seen for the first time — would fail to process, resulting in dropped position updates. Both cases are now handled correctly, so global tracking processes all vessels without interruption.
​
April 19, 2026
OverwatchFix

​
Flag-hopping detection now tracks all flag changes

Fixed an issue where flag-state changes were not being recorded for some vessels due to an incorrect column reference in the tracking trigger. Flag-hopping history is now captured reliably for all vessels, so the risk scoring system has complete data when evaluating registry-change patterns.
​
April 19, 2026
OverwatchFix

​
Fixed a client-side crash on page load

Resolved an issue where Overwatch could display “Application error: a client-side exception has occurred” when loading a page. The crash was caused by an analytics initialization timing issue and has been fixed — pages now load reliably.
​
April 19, 2026
LocusFix

​
Performance and privacy improvements

Video playback components now load on demand instead of at page load, reducing initial bundle size. Scroll-heavy pages use frame-throttled listeners for smoother performance. Analytics tracking now respects consent preferences before initializing.
​
April 19, 2026
OverwatchFix

​
More reliable kinematic fingerprint computation

Fixed an issue where the kinematic fingerprint computation could silently fail without logging an error. If the function timed out before reaching its success or error handler, no ingestion log was written, making it appear as though the run never happened — even though the scheduler reported it as complete. Kinematic fingerprint profiles now update reliably, so vessel behavioral data stays current. No action is required on your part.
​
April 19, 2026
OverwatchFix

​
More reliable Equasis vessel enrichment

Fixed an issue where vessel metadata enrichment from Equasis failed approximately 96% of the time after a session renewal. When a session expired mid-run, the immediate retry did not fully establish the new session before requesting vessel data, causing the request to be rejected. Enrichment retries now mirror the full session setup flow, so vessel profiles — including registered owner, flag state, and deadweight tonnage — are populated more consistently.