User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is LimaCharlie down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → limacharlie.io—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 2 hr ago. Last stored result reached it in 153 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 19 | 0 | 0.0 | 374 ms | 0 |
| Tue 22 | 0 | 0.0 | 307 ms | 0 |
| Wed 00 | 0 | 0.0 | 448 ms | 0 |
| Wed 02 | 0 | 0.0 | 365 ms | 0 |
| Wed 04 | 0 | 0.0 | 246 ms | 0 |
| Wed 07 | 0 | 0.0 | 175 ms | 0 |
| Wed 09 | 0 | 0.0 | 186 ms | 0 |
| Wed 11 | 0 | 0.0 | 221 ms | 0 |
| Wed 13 | 0 | 0.0 | 348 ms | 0 |
| Wed 15 | 0 | 0.0 | 469 ms | 0 |
| Wed 17 | 0 | 0.0 | 385 ms | 0 |
| Wed 19 | 0 | 0.0 | 258 ms | 0 |
| Wed 21 | 0 | 0.0 | 393 ms | 0 |
| Wed 22 | 0 | 0.0 | 96 ms | 0 |
| Thu 00 | 0 | 0.0 | 213 ms | 0 |
| Thu 02 | 0 | 0.0 | 189 ms | 0 |
| Thu 04 | 0 | 0.0 | 242 ms | 0 |
| Thu 06 | 0 | 0.0 | 273 ms | 0 |
| Thu 08 | 0 | 0.0 | 190 ms | 0 |
| Thu 10 | 0 | 0.0 | 337 ms | 0 |
| Thu 12 | 0 | 0.0 | 222 ms | 0 |
| Thu 14 | 0 | 0.0 | 95 ms | 0 |
| Thu 16 | 0 | 0.0 | 220 ms | 0 |
| Thu 18 | 0 | 0.0 | 206 ms | 0 |
| Thu 20 | 0 | 0.0 | 311 ms | 0 |
| Thu 22 | 0 | 0.0 | 531 ms | 0 |
| Fri 01 | 0 | 0.0 | 186 ms | 0 |
| Fri 03 | 0 | 0.0 | 355 ms | 0 |
| Fri 05 | 0 | 0.0 | 363 ms | 0 |
| Fri 06 | 0 | 0.0 | 339 ms | 0 |
| Fri 08 | 0 | 0.0 | 316 ms | 0 |
| Fri 10 | 0 | 0.0 | 316 ms | 0 |
| Fri 12 | 0 | 0.0 | 147 ms | 0 |
| Fri 14 | 0 | 0.0 | 262 ms | 0 |
| Fri 16 | 0 | 0.0 | 235 ms | 0 |
| Fri 18 | 0 | 0.0 | 257 ms | 0 |
| Fri 20 | 0 | 0.0 | 105 ms | 0 |
| Fri 22 | 0 | 0.0 | 307 ms | 0 |
| Sat 00 | 0 | 0.0 | 388 ms | 0 |
| Sat 02 | 0 | 0.0 | 249 ms | 0 |
| Sat 04 | 0 | 0.0 | 402 ms | 0 |
| Sat 06 | 0 | 0.0 | 315 ms | 0 |
| Sat 08 | 0 | 0.0 | 291 ms | 0 |
| Sat 10 | 0 | 0.0 | 314 ms | 0 |
| Sat 12 | 0 | 0.0 | 332 ms | 0 |
| Sat 15 | 0 | 0.0 | 192 ms | 0 |
| Sat 17 | 0 | 0.0 | 334 ms | 0 |
| Sat 19 | 0 | 0.0 | 153 ms | 0 |
Reliability
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.
Embed this status: free live LimaCharlie badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for LimaCharlie yet. Outages of 10 minutes or more get their own page here.
Having trouble with LimaCharlie?
One report per service every 10 minutes from this network. No account.
Follow LimaCharlie
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.
About LimaCharlie
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: 309 ms average, 153–482 ms range across 13 successful checks.
Questions
Is LimaCharlie down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was LimaCharlie last down?
We have not recorded a public LimaCharlie incident since monitoring began 9 days ago.
What is LimaCharlie's uptime?
From our own checks: 100% over 9 days of checks.
How fast does LimaCharlie respond?
309 ms on average over the last 24 hours (153–482 ms).
Does LimaCharlie have an official status page?
Yes, at https://status.limacharlie.io.
LimaCharlie not working for me but the status is fine. What now?
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.