User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Omi down?
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
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 → omi.me—
Your browser → us—
Our checksOur checks can't reach Omi right now
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
Our checks can't reach Omi right now
Omi is blocking or timing out our automated checks, so we can't test it directly. We still count user reports and watch the official status page.
Last checked 1 hr ago. Last stored result reached it in 15 ms.
Official status
All clear
All systems operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 252 ms | 0 |
| Mon 20 | 0 | 0.0 | 129 ms | 0 |
| Mon 22 | 0 | 0.0 | 14 ms | 0 |
| Tue 00 | 0 | 0.0 | 16 ms | 0 |
| Tue 02 | 0 | 0.0 | 44 ms | 0 |
| Tue 04 | 0 | 0.0 | 182 ms | 0 |
| Tue 06 | 0 | 0.0 | 143 ms | 0 |
| Tue 08 | 0 | 0.0 | 183 ms | 0 |
| Tue 11 | 0 | 0.0 | 9 ms | 0 |
| Tue 13 | 0 | 0.0 | 230 ms | 0 |
| Tue 15 | 0 | 0.0 | 166 ms | 0 |
| Tue 17 | 0 | 0.0 | 163 ms | 0 |
| Tue 20 | 0 | 0.0 | 89 ms | 0 |
| Tue 22 | 0 | 0.0 | 168 ms | 0 |
| Wed 00 | 0 | 0.0 | 16 ms | 0 |
| Wed 02 | 0 | 0.0 | 98 ms | 0 |
| Wed 05 | 0 | 0.0 | 11 ms | 0 |
| Wed 07 | 0 | 0.0 | 175 ms | 0 |
| Wed 09 | 0 | 0.0 | 12 ms | 0 |
| Wed 11 | 0 | 0.0 | 18 ms | 0 |
| Wed 13 | 0 | 0.0 | 52 ms | 0 |
| Wed 15 | 0 | 0.0 | 13 ms | 0 |
| Wed 18 | 0 | 0.0 | 41 ms | 0 |
| Wed 20 | 0 | 0.0 | 12 ms | 0 |
| Wed 22 | 0 | 0.0 | 26 ms | 0 |
| Thu 00 | 0 | 0.0 | 13 ms | 0 |
| Thu 02 | 0 | 0.0 | 155 ms | 0 |
| Thu 04 | 0 | 0.0 | 194 ms | 0 |
| Thu 06 | 0 | 0.0 | 200 ms | 0 |
| Thu 09 | 0 | 0.0 | 13 ms | 0 |
| Thu 11 | 0 | 0.0 | 12 ms | 0 |
| Thu 13 | 0 | 0.0 | 208 ms | 0 |
| Thu 15 | 0 | 0.0 | 130 ms | 0 |
| Thu 17 | 0 | 0.0 | 164 ms | 0 |
| Thu 19 | 0 | 0.0 | 26 ms | 0 |
| Thu 21 | 0 | 0.0 | 146 ms | 0 |
| Thu 23 | 0 | 0.0 | 70 ms | 0 |
| Fri 01 | 0 | 0.0 | 176 ms | 0 |
| Fri 03 | 0 | 0.0 | 8 ms | 0 |
| Fri 05 | 0 | 0.0 | 38 ms | 0 |
| Fri 07 | 0 | 0.0 | 32 ms | 0 |
| Fri 09 | 0 | 0.0 | 158 ms | 0 |
| Fri 10 | 0 | 0.0 | 24 ms | 0 |
| Fri 12 | 0 | 0.0 | 16 ms | 0 |
| Fri 14 | 0 | 0.0 | 26 ms | 0 |
| Fri 16 | 0 | 0.0 | 11 ms | 0 |
| Fri 18 | 0 | 0.0 | 8 ms | 0 |
| Fri 19 | 0 | 0.0 | 15 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 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Omi 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 Omi yet. Outages of 10 minutes or more get their own page here.
Having trouble with Omi?
One report per service every 10 minutes from this network. No account.
Follow Omi
Get an email when Omi goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Omi alerts to Slack, Discord or a webhook — free.
About Omi
We track Omi (omi.me) as part of the AI group. Omi is a wearable AI pendant that captures your conversations, transcribes voice to notes, and automatically creates tasks and memories, so you never forget a thing.
Omi publishes an official status page at status.omi.me; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 70 ms average, 8–195 ms range across 15 successful checks.
Questions
Is Omi down right now?
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
When was Omi last down?
We have not recorded a public Omi incident since monitoring began 7 days ago.
What is Omi's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Omi respond?
70 ms on average over the last 24 hours (8–195 ms).
Does Omi have an official status page?
Yes, at https://status.omi.me.
Omi 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 Omi here at once, the problem is on Omi'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 Omi. 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.