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 215 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 164 ms | 0 |
| Tue 02 | 0 | 0.0 | 142 ms | 0 |
| Tue 04 | 0 | 0.0 | 272 ms | 0 |
| Tue 06 | 0 | 0.0 | 250 ms | 0 |
| Tue 08 | 0 | 0.0 | 211 ms | 0 |
| Tue 10 | 0 | 0.0 | 264 ms | 0 |
| Tue 12 | 0 | 0.0 | 219 ms | 0 |
| Tue 15 | 0 | 0.0 | 243 ms | 0 |
| Tue 17 | 0 | 0.0 | 231 ms | 0 |
| Tue 19 | 0 | 0.0 | 301 ms | 0 |
| Tue 21 | 0 | 0.0 | 274 ms | 0 |
| Wed 00 | 0 | 0.0 | 221 ms | 0 |
| Wed 02 | 0 | 0.0 | 187 ms | 0 |
| Wed 04 | 0 | 0.0 | 263 ms | 0 |
| Wed 06 | 0 | 0.0 | 243 ms | 0 |
| Wed 08 | 0 | 0.0 | 173 ms | 0 |
| Wed 10 | 0 | 0.0 | 235 ms | 0 |
| Wed 12 | 0 | 0.0 | 240 ms | 0 |
| Wed 15 | 0 | 0.0 | 232 ms | 0 |
| Wed 17 | 0 | 0.0 | 222 ms | 0 |
| Wed 19 | 0 | 0.0 | 246 ms | 0 |
| Wed 21 | 0 | 0.0 | 249 ms | 0 |
| Wed 23 | 0 | 0.0 | 227 ms | 0 |
| Thu 01 | 0 | 0.0 | 240 ms | 0 |
| Thu 03 | 0 | 0.0 | 203 ms | 0 |
| Thu 05 | 0 | 0.0 | 225 ms | 0 |
| Thu 08 | 0 | 0.0 | 138 ms | 0 |
| Thu 10 | 0 | 0.0 | 222 ms | 0 |
| Thu 12 | 0 | 0.0 | 218 ms | 0 |
| Thu 14 | 0 | 0.0 | 2046 ms | 0 |
| Thu 16 | 0 | 0.0 | 166 ms | 0 |
| Thu 18 | 0 | 0.0 | 194 ms | 0 |
| Thu 20 | 0 | 0.0 | 269 ms | 0 |
| Thu 22 | 0 | 0.0 | 217 ms | 0 |
| Fri 00 | 0 | 0.0 | 136 ms | 0 |
| Fri 02 | 0 | 0.0 | 230 ms | 0 |
| Fri 04 | 0 | 0.0 | 198 ms | 0 |
| Fri 05 | 0 | 0.0 | 191 ms | 0 |
| Fri 07 | 0 | 0.0 | 252 ms | 0 |
| Fri 09 | 0 | 0.0 | 168 ms | 0 |
| Fri 10 | 0 | 0.0 | 200 ms | 0 |
| Fri 11 | 0 | 0.0 | 210 ms | 0 |
| Fri 13 | 0 | 0.0 | 223 ms | 0 |
| Fri 15 | 0 | 0.0 | 135 ms | 0 |
| Fri 17 | 0 | 0.0 | 210 ms | 0 |
| Fri 19 | 0 | 0.0 | 237 ms | 0 |
| Fri 21 | 0 | 0.0 | 225 ms | 0 |
| Fri 23 | 0 | 0.0 | 215 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for GReminders 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 GReminders goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send GReminders alerts to Slack, Discord or a webhook — free.
GReminders, at greminders.com, is one of the AI services we monitor. GReminders helps advisors save time, reduce no-shows, and stay organized with AI-powered meeting reminders, scheduling, and notetaking. Streamline workflows, integrate with your favorite tools, and get a turnkey solution that works from day one.
GReminders publishes an official status page at status.greminders.com; 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: 204 ms average, 126–252 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public GReminders incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
204 ms on average over the last 24 hours (126–252 ms).
Yes, at https://status.greminders.com.
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 GReminders here at once, the problem is on GReminders'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 GReminders. 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.