Statusfield LogoStatusfield
LimaCharlie status
LimaCharlie logo and current status indicator

LimaCharlie Incident History

Operational

limacharlie.io ↗7 top-level components

checked Oct 23, 2026 9:27 PM UTC · LimaCharlie's official status page

LimaCharlie is up and running.

LimaCharlie is currently operational with all systems functioning normally.

All components operational

Be the first to know

Statusfield watches LimaCharlie alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.

30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.

LimaCharlie incident history

2 reports published by LimaCharlie in the last 30 days

When LimaCharlie breaks, it is typically resolved in 4h 9m — median across 1 resolved incidents over 30 days.

October 20, 2026

Degraded Replay search and Insight queries in the UK region (Google Cloud London incident)

Last update

  1. resolvedOct 20 · 16:20 UTC

    Resolved. Between 06:10 and 11:10 UTC on 20 October 2026, a Google Cloud infrastructure incident in the London (europe-west2) region caused intermittent failures for BigQuery-backed features in the LimaCharlie UK region:

    • Replay / historical searches and search cost estimates, which could fail with "failed to get sensor event count: googleapi: Error 400: The job encountered an error during execution ... jobBackendError"
    • The Insight usage overview in the web app
    • Scheduled IOC index refreshes

    Telemetry ingestion, detection & response, and the UK API endpoints remained available throughout. Google has mitigated the incident (Google Cloud incident Xs2XTHzAVC9YnafnPyzj) and we have seen no further errors since 11:10 UTC. Searches that failed during the window can simply be re-run; scheduled index refreshes resume on their next run.

Reported by LimaCharlie on their status page.

October 8, 2026

app.limacharlie.io outage

Last update

  1. resolvedOct 8 · 05:26 UTC

    GCP has rolled back the breaking change, and services are confirmed normalized. We are calling this issue resolved.

Reported by LimaCharlie on their status page.