User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 275 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 286 ms | 0 |
| Nov 7 | 0 | 0.0 | 231 ms | 0 |
| Nov 7 | 0 | 0.0 | 283 ms | 0 |
| Nov 7 | 0 | 0.0 | 421 ms | 0 |
| Nov 7 | 0 | 0.0 | 464 ms | 0 |
| Nov 8 | 0 | 0.0 | 260 ms | 0 |
| Nov 8 | 0 | 0.0 | 229 ms | 0 |
| Nov 8 | 0 | 0.0 | 347 ms | 0 |
| Nov 8 | 0 | 0.0 | 332 ms | 0 |
| Nov 9 | 0 | 0.0 | 184 ms | 0 |
| Nov 9 | 0 | 0.0 | 274 ms | 0 |
| Nov 9 | 0 | 0.0 | 290 ms | 0 |
| Nov 9 | 0 | 0.0 | 338 ms | 0 |
| Nov 10 | 0 | 0.0 | 355 ms | 0 |
| Nov 10 | 0 | 0.0 | 200 ms | 0 |
| Nov 10 | 0 | 0.0 | 284 ms | 0 |
| Nov 10 | 0 | 0.0 | 341 ms | 0 |
| Nov 11 | 0 | 0.0 | 309 ms | 0 |
| Nov 11 | 0 | 0.0 | 186 ms | 0 |
| Nov 11 | 0 | 0.0 | 385 ms | 0 |
| Nov 11 | 0 | 0.0 | 258 ms | 0 |
| Nov 12 | 0 | 0.0 | 213 ms | 0 |
| Nov 12 | 0 | 0.0 | 273 ms | 0 |
| Nov 12 | 0 | 0.0 | 170 ms | 0 |
| Nov 12 | 0 | 0.0 | 311 ms | 0 |
| Nov 13 | 0 | 0.0 | 348 ms | 0 |
| Nov 13 | 0 | 0.0 | 316 ms | 0 |
| Nov 13 | 0 | 0.0 | 235 ms | 0 |
| Nov 13 | 0 | 0.0 | 257 ms | 0 |
| Nov 14 | 0 | 0.0 | 355 ms | 0 |
| Nov 14 | 0 | 0.0 | 314 ms | 0 |
| Nov 14 | 0 | 0.0 | 314 ms | 0 |
| Nov 14 | 0 | 0.0 | 214 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for LimaCharlie yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when LimaCharlie goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
LimaCharlie is listed in our AI category and checked at limacharlie.io. LimaCharlie is the agentic SecOps platform for MSSPs and MDRs: telemetry, detection, and response across every client you serve, on infrastructure built to be operated. Run it the way you already work, and turn on AI operators when you decide.
LimaCharlie publishes an official status page at status.limacharlie.io; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 306 ms average, 153–482 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public LimaCharlie incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
306 ms on average over the last 24 hours (153–482 ms).
Yes, at https://status.limacharlie.io.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report LimaCharlie here at once, the problem is on LimaCharlie's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with LimaCharlie. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.