User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
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 184 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 289 ms | 0 |
| Nov 7 | 0 | 0.0 | 346 ms | 0 |
| Nov 7 | 0 | 0.0 | 157 ms | 0 |
| Nov 7 | 0 | 0.0 | 72 ms | 0 |
| Nov 8 | 0 | 0.0 | 213 ms | 0 |
| Nov 8 | 0 | 0.0 | 150 ms | 0 |
| Nov 8 | 0 | 0.0 | 192 ms | 0 |
| Nov 8 | 0 | 0.0 | 217 ms | 0 |
| Nov 9 | 0 | 0.0 | 184 ms | 0 |
| Nov 9 | 0 | 0.0 | 158 ms | 0 |
| Nov 9 | 0 | 0.0 | 173 ms | 0 |
| Nov 9 | 0 | 0.0 | 185 ms | 0 |
| Nov 10 | 0 | 0.0 | 171 ms | 0 |
| Nov 10 | 0 | 0.0 | 163 ms | 0 |
| Nov 10 | 0 | 0.0 | 129 ms | 0 |
| Nov 10 | 0 | 0.0 | 201 ms | 0 |
| Nov 11 | 0 | 0.0 | 245 ms | 0 |
| Nov 11 | 0 | 0.0 | 162 ms | 0 |
| Nov 11 | 0 | 0.0 | 214 ms | 0 |
| Nov 11 | 0 | 0.0 | 190 ms | 0 |
| Nov 12 | 0 | 0.0 | 165 ms | 0 |
| Nov 12 | 0 | 0.0 | 190 ms | 0 |
| Nov 12 | 0 | 0.0 | 166 ms | 0 |
| Nov 12 | 0 | 0.0 | 200 ms | 0 |
| Nov 13 | 0 | 0.0 | 190 ms | 0 |
| Nov 13 | 0 | 0.0 | 181 ms | 0 |
| Nov 13 | 0 | 0.0 | 147 ms | 0 |
| Nov 13 | 0 | 0.0 | 252 ms | 0 |
| Nov 14 | 0 | 0.0 | 203 ms | 0 |
| Nov 14 | 0 | 0.0 | 190 ms | 0 |
| Nov 14 | 0 | 0.0 | 184 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Plan to Eat 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 Plan to Eat 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.
Plan to Eat, at plantoeat.com, is one of the Money services we monitor. The meal planner app that saves recipes from any site, plans your week, and builds your grocery list for you. Free 14-day trial, no card needed.
Plan to Eat publishes an official status page at status.plantoeat.com; when we can read it, its incident level is folded into the status shown here.
Common problems for money services: login and two-factor problems, payments or transfers failing, and app errors.
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: 174 ms average, 40–252 ms range across 11 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Plan to Eat incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
174 ms on average over the last 24 hours (40–252 ms).
Yes, at https://status.plantoeat.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For money services, watch for login and two-factor problems, payments or transfers failing, and app errors. If many people report Plan to Eat here at once, the problem is on Plan to Eat'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 Plan to Eat. 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.