User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Food
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 37 min ago. Last stored result reached it in 50 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 7 | 0 | 0.0 | 42 ms | 0 |
| Nov 7 | 0 | 0.0 | 56 ms | 0 |
| Nov 8 | 0 | 0.0 | 110 ms | 0 |
| Nov 8 | 0 | 0.0 | 73 ms | 0 |
| Nov 8 | 0 | 0.0 | 81 ms | 0 |
| Nov 8 | 0 | 0.0 | 58 ms | 0 |
| Nov 9 | 0 | 0.0 | 104 ms | 0 |
| Nov 9 | 0 | 0.0 | 83 ms | 0 |
| Nov 9 | 0 | 0.0 | 109 ms | 0 |
| Nov 9 | 0 | 0.0 | 65 ms | 0 |
| Nov 10 | 0 | 0.0 | 87 ms | 0 |
| Nov 10 | 0 | 0.0 | 110 ms | 0 |
| Nov 10 | 0 | 0.0 | 73 ms | 0 |
| Nov 10 | 0 | 0.0 | 94 ms | 0 |
| Nov 11 | 0 | 0.0 | 126 ms | 0 |
| Nov 11 | 0 | 0.0 | 103 ms | 0 |
| Nov 11 | 0 | 0.0 | 111 ms | 0 |
| Nov 11 | 0 | 0.0 | 139 ms | 0 |
| Nov 12 | 0 | 0.0 | 124 ms | 0 |
| Nov 12 | 0 | 0.0 | 158 ms | 0 |
| Nov 12 | 0 | 0.0 | 92 ms | 0 |
| Nov 12 | 0 | 0.0 | 110 ms | 0 |
| Nov 13 | 0 | 0.0 | 105 ms | 0 |
| Nov 13 | 0 | 0.0 | 113 ms | 0 |
| Nov 13 | 0 | 0.0 | 96 ms | 0 |
| Nov 13 | 0 | 0.0 | 122 ms | 0 |
| Nov 14 | 0 | 0.0 | 52 ms | 0 |
| Nov 14 | 0 | 0.0 | 79 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 Per Diem 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 Per Diem goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Per Diem alerts to Slack, Discord or a webhook — free.
Per Diem, at tryperdiem.com, is one of the Food services we monitor. Launch a branded mobile app and web ordering for your restaurant, cafe, or bakery with loyalty, delivery, marketing, and Square integration.
Per Diem publishes an official status page at status.tryperdiem.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with food services: ordering and checkout failures, delivery tracking stalling, and restaurant menus not loading at peak meal times.
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: 86 ms average, 49–132 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Per Diem incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
86 ms on average over the last 24 hours (49–132 ms).
Yes, at https://status.tryperdiem.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For food services, watch for ordering and checkout failures, delivery tracking stalling, and restaurant menus not loading at peak meal times. If many people report Per Diem here at once, the problem is on Per Diem'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 Per Diem. 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.