User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
givechariot.com · Cloud & developer
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 50 min ago. Last stored result reached it in 90 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 63 ms | 0 |
| Tue 00 | 0 | 0.0 | 87 ms | 0 |
| Tue 02 | 0 | 0.0 | 107 ms | 0 |
| Tue 05 | 0 | 0.0 | 90 ms | 0 |
| Tue 07 | 0 | 0.0 | 147 ms | 0 |
| Tue 09 | 0 | 0.0 | 99 ms | 0 |
| Tue 11 | 0 | 0.0 | 140 ms | 0 |
| Tue 13 | 0 | 0.0 | 218 ms | 0 |
| Tue 15 | 0 | 0.0 | 186 ms | 0 |
| Tue 18 | 0 | 0.0 | 244 ms | 0 |
| Tue 20 | 0 | 0.0 | 140 ms | 0 |
| Tue 22 | 0 | 0.0 | 166 ms | 0 |
| Wed 00 | 0 | 0.0 | 210 ms | 0 |
| Wed 03 | 0 | 0.0 | 227 ms | 0 |
| Wed 05 | 0 | 0.0 | 156 ms | 0 |
| Wed 07 | 0 | 0.0 | 76 ms | 0 |
| Wed 09 | 0 | 0.0 | 100 ms | 0 |
| Wed 12 | 0 | 0.0 | 64 ms | 0 |
| Wed 14 | 0 | 0.0 | 257 ms | 0 |
| Wed 16 | 0 | 0.0 | 323 ms | 0 |
| Wed 18 | 0 | 0.0 | 284 ms | 0 |
| Wed 20 | 0 | 0.0 | 208 ms | 0 |
| Wed 22 | 0 | 0.0 | 119 ms | 0 |
| Thu 01 | 0 | 0.0 | 92 ms | 0 |
| Thu 03 | 0 | 0.0 | 209 ms | 0 |
| Thu 05 | 0 | 0.0 | 112 ms | 0 |
| Thu 07 | 0 | 0.0 | 174 ms | 0 |
| Thu 09 | 0 | 0.0 | 163 ms | 0 |
| Thu 11 | 0 | 0.0 | 117 ms | 0 |
| Thu 13 | 0 | 0.0 | 178 ms | 0 |
| Thu 15 | 0 | 0.0 | 221 ms | 0 |
| Thu 17 | 0 | 0.0 | 188 ms | 0 |
| Thu 19 | 0 | 0.0 | 196 ms | 0 |
| Thu 20 | 0 | 0.0 | 172 ms | 0 |
| Thu 22 | 0 | 0.0 | 188 ms | 0 |
| Fri 00 | 0 | 0.0 | 108 ms | 0 |
| Fri 02 | 0 | 0.0 | 93 ms | 0 |
| Fri 04 | 0 | 0.0 | 94 ms | 0 |
| Fri 06 | 0 | 0.0 | 153 ms | 0 |
| Fri 08 | 0 | 0.0 | 166 ms | 0 |
| Fri 10 | 0 | 0.0 | 129 ms | 0 |
| Fri 11 | 0 | 0.0 | 284 ms | 0 |
| Fri 13 | 0 | 0.0 | 135 ms | 0 |
| Fri 15 | 0 | 0.0 | 96 ms | 0 |
| Fri 17 | 0 | 0.0 | 76 ms | 0 |
| Fri 19 | 0 | 0.0 | 144 ms | 0 |
| Fri 21 | 0 | 0.0 | 75 ms | 0 |
| Fri 23 | 0 | 0.0 | 110 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 chariot 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 chariot goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send chariot alerts to Slack, Discord or a webhook — free.
chariot is listed in our Cloud & developer category and checked at givechariot.com. With Chariot, nonprofits can raise more from Donor-Advised Funds and save time on gift processing.
chariot publishes an official status page at status.givechariot.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 127 ms average, 75–284 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 chariot incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
127 ms on average over the last 24 hours (75–284 ms).
Yes, at https://status.givechariot.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report chariot here at once, the problem is on chariot'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 chariot. 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.