User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
reclaim.ai · AI
Is Reclaim 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 → reclaim.ai—
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 32 min ago. Last stored result reached it in 142 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 |
|---|---|---|---|---|
| Tue 15 | 0 | 0.0 | 171 ms | 0 |
| Tue 17 | 0 | 0.0 | 68 ms | 0 |
| Tue 20 | 0 | 0.0 | 99 ms | 0 |
| Tue 22 | 0 | 0.0 | 201 ms | 0 |
| Wed 00 | 0 | 0.0 | 103 ms | 0 |
| Wed 02 | 0 | 0.0 | 250 ms | 0 |
| Wed 05 | 0 | 0.0 | 93 ms | 0 |
| Wed 07 | 0 | 0.0 | 128 ms | 0 |
| Wed 09 | 0 | 0.0 | 82 ms | 0 |
| Wed 11 | 0 | 0.0 | 115 ms | 0 |
| Wed 13 | 0 | 0.0 | 80 ms | 0 |
| Wed 15 | 0 | 0.0 | 177 ms | 0 |
| Wed 18 | 0 | 0.0 | 193 ms | 0 |
| Wed 20 | 0 | 0.0 | 64 ms | 0 |
| Wed 22 | 0 | 0.0 | 64 ms | 0 |
| Thu 00 | 0 | 0.0 | 69 ms | 0 |
| Thu 02 | 0 | 0.0 | 123 ms | 0 |
| Thu 04 | 0 | 0.0 | 78 ms | 0 |
| Thu 06 | 0 | 0.0 | 87 ms | 0 |
| Thu 09 | 0 | 0.0 | 92 ms | 0 |
| Thu 11 | 0 | 0.0 | 72 ms | 0 |
| Thu 13 | 0 | 0.0 | 98 ms | 0 |
| Thu 15 | 0 | 0.0 | 112 ms | 0 |
| Thu 17 | 0 | 0.0 | 175 ms | 0 |
| Thu 19 | 0 | 0.0 | 275 ms | 0 |
| Thu 21 | 0 | 0.0 | 145 ms | 0 |
| Thu 23 | 0 | 0.0 | 63 ms | 0 |
| Fri 01 | 0 | 0.0 | 102 ms | 0 |
| Fri 03 | 0 | 0.0 | 100 ms | 0 |
| Fri 05 | 0 | 0.0 | 104 ms | 0 |
| Fri 07 | 0 | 0.0 | 56 ms | 0 |
| Fri 09 | 0 | 0.0 | 78 ms | 0 |
| Fri 11 | 0 | 0.0 | 73 ms | 0 |
| Fri 14 | 0 | 0.0 | 129 ms | 0 |
| Fri 16 | 0 | 0.0 | 142 ms | 0 |
| Fri 17 | 0 | 0.0 | 276 ms | 0 |
| Fri 19 | 0 | 0.0 | 163 ms | 0 |
| Fri 21 | 0 | 0.0 | 140 ms | 0 |
| Fri 23 | 0 | 0.0 | 187 ms | 0 |
| Sat 01 | 0 | 0.0 | 99 ms | 0 |
| Sat 03 | 0 | 0.0 | 73 ms | 0 |
| Sat 06 | 0 | 0.0 | 103 ms | 0 |
| Sat 07 | 0 | 0.0 | 94 ms | 0 |
| Sat 09 | 0 | 0.0 | 90 ms | 0 |
| Sat 11 | 0 | 0.0 | 112 ms | 0 |
| Sat 14 | 0 | 0.0 | 85 ms | 0 |
| Sat 16 | 0 | 0.0 | 113 ms | 0 |
| Sat 18 | 0 | 0.0 | 142 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 Reclaim 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 Reclaim yet. Outages of 10 minutes or more get their own page here.
Having trouble with Reclaim?
One report per service every 10 minutes from this network. No account.
Follow Reclaim
Get an email when Reclaim 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 Reclaim
We track Reclaim (reclaim.ai) as part of the AI group. Reclaim is an AI-powered app that creates 40% more time for teams — auto-schedule tasks, habits, meeting & breaks – free on Google Calendar & Outlook Calendar.
Reclaim publishes an official status page at status.reclaim.ai; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong 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: 113 ms average, 73–187 ms range across 13 successful checks.
Questions
Is Reclaim down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Reclaim last down?
We have not recorded a public Reclaim incident since monitoring began 9 days ago.
What is Reclaim's uptime?
From our own checks: 100% over 9 days of checks.
How fast does Reclaim respond?
113 ms on average over the last 24 hours (73–187 ms).
Does Reclaim have an official status page?
Yes, at https://status.reclaim.ai.
Reclaim 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 Reclaim here at once, the problem is on Reclaim'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 Reclaim. 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.