User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
Is Jamie down?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Web app is down | Web app is down
Source: the vendor's status page · We are not affiliated with Jamie.
What to try while Jamie is having problems
Estimated fix: Not enough Jamie history yet; similar Productivity outages lasted 45 min (median, typically 14 min–4 h; 27 outages).
- Desktop and mobile apps often keep working offline on files you opened recently.
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 → meetjamie.ai—
Your browser → us—
Our checksReaching it
Official · ReportsMinor incident · 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 1 hr ago. Last stored result reached it in 276 ms.
Official status
Minor incident
Web app is down | Web app is down Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 241 ms | 0 |
| Mon 18 | 0 | 0.0 | 218 ms | 0 |
| Mon 20 | 0 | 0.0 | 260 ms | 0 |
| Mon 22 | 0 | 0.0 | 386 ms | 0 |
| Tue 01 | 0 | 0.0 | 213 ms | 0 |
| Tue 03 | 0 | 0.0 | 196 ms | 0 |
| Tue 05 | 0 | 0.0 | 190 ms | 0 |
| Tue 07 | 0 | 0.0 | 394 ms | 0 |
| Tue 09 | 0 | 0.0 | 308 ms | 0 |
| Tue 11 | 0 | 0.0 | 276 ms | 0 |
| Tue 13 | 0 | 0.0 | 475 ms | 0 |
| Tue 16 | 0 | 0.0 | 245 ms | 0 |
| Tue 18 | 0 | 0.0 | 212 ms | 0 |
| Tue 20 | 0 | 0.0 | 217 ms | 0 |
| Tue 22 | 0 | 0.0 | 190 ms | 0 |
| Wed 01 | 0 | 0.0 | 214 ms | 0 |
| Wed 03 | 0 | 0.0 | 205 ms | 0 |
| Wed 05 | 0 | 0.0 | 213 ms | 0 |
| Wed 07 | 0 | 0.0 | 204 ms | 0 |
| Wed 10 | 0 | 0.0 | 250 ms | 0 |
| Wed 12 | 0 | 0.0 | 330 ms | 0 |
| Wed 14 | 0 | 0.0 | 194 ms | 0 |
| Wed 16 | 0 | 0.0 | 190 ms | 0 |
| Wed 18 | 0 | 0.0 | 336 ms | 0 |
| Wed 20 | 0 | 0.0 | 216 ms | 0 |
| Wed 23 | 0 | 0.0 | 240 ms | 0 |
| Thu 01 | 0 | 0.0 | 249 ms | 0 |
| Thu 03 | 0 | 0.0 | 222 ms | 0 |
| Thu 05 | 0 | 0.0 | 294 ms | 0 |
| Thu 07 | 0 | 0.0 | 193 ms | 0 |
| Thu 09 | 0 | 0.0 | 229 ms | 0 |
| Thu 11 | 0 | 0.0 | 197 ms | 0 |
| Thu 13 | 0 | 0.0 | 229 ms | 0 |
| Thu 15 | 0 | 0.0 | 409 ms | 0 |
| Thu 17 | 0 | 0.0 | 292 ms | 0 |
| Thu 19 | 0 | 0.0 | 226 ms | 0 |
| Thu 21 | 0 | 0.0 | 280 ms | 0 |
| Thu 23 | 0 | 0.0 | 210 ms | 0 |
| Fri 01 | 0 | 0.0 | 346 ms | 0 |
| Fri 04 | 0 | 0.0 | 196 ms | 0 |
| Fri 06 | 0 | 0.0 | 197 ms | 0 |
| Fri 08 | 0 | 0.0 | 212 ms | 0 |
| Fri 10 | 0 | 0.0 | 213 ms | 0 |
| Fri 12 | 0 | 0.0 | 217 ms | 0 |
| Fri 14 | 0 | 0.0 | 441 ms | 0 |
| Fri 16 | 0 | 0.0 | 212 ms | 0 |
| Fri 18 | 0 | 0.0 | 422 ms | 0 |
| Fri 20 | 0 | 0.0 | 276 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 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Jamie 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 Jamie yet. Outages of 10 minutes or more get their own page here.
Having trouble with Jamie?
One report per service every 10 minutes from this network. No account.
Follow Jamie
Get an email when Jamie goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Jamie alerts to Slack, Discord or a webhook — free.
About Jamie
We track Jamie (meetjamie.ai) as part of the Productivity group. The meeting intelligence platform you can trust. Jamie turns every meeting into knowledge you can act on, with no bot on the call, data hosted in the EU, ISO 27001 and GDPR.
Jamie publishes an official status page at status.meetjamie.ai; when we can read it, its incident level is folded into the status shown here.
Common problems for productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 270 ms average, 194–588 ms range across 14 successful checks.
Questions
Is Jamie down right now?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Web app is down | Web app is down
When was Jamie last down?
We have not recorded a public Jamie incident since monitoring began 8 days ago.
What is Jamie's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Jamie respond?
270 ms on average over the last 24 hours (194–588 ms).
Does Jamie have an official status page?
Yes, at https://status.meetjamie.ai.
Jamie 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 productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Jamie here at once, the problem is on Jamie'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 Jamie. 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.