User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 51 min ago. Last stored result reached it in 32 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 12 | 0 | 0.0 | 30 ms | 0 |
| Tue 15 | 0 | 0.0 | 70 ms | 0 |
| Tue 17 | 0 | 0.0 | 121 ms | 0 |
| Tue 19 | 0 | 0.0 | 37 ms | 0 |
| Tue 21 | 0 | 0.0 | 48 ms | 0 |
| Wed 00 | 0 | 0.0 | 145 ms | 0 |
| Wed 02 | 0 | 0.0 | 45 ms | 0 |
| Wed 04 | 0 | 0.0 | 40 ms | 0 |
| Wed 06 | 0 | 0.0 | 67 ms | 0 |
| Wed 09 | 0 | 0.0 | 106 ms | 0 |
| Wed 11 | 0 | 0.0 | 62 ms | 0 |
| Wed 13 | 0 | 0.0 | 95 ms | 0 |
| Wed 15 | 0 | 0.0 | 45 ms | 0 |
| Wed 17 | 0 | 0.0 | 57 ms | 0 |
| Wed 19 | 0 | 0.0 | 216 ms | 0 |
| Wed 22 | 0 | 0.0 | 167 ms | 0 |
| Thu 00 | 0 | 0.0 | 79 ms | 0 |
| Thu 02 | 0 | 0.0 | 63 ms | 0 |
| Thu 04 | 0 | 0.0 | 106 ms | 0 |
| Thu 06 | 0 | 0.0 | 38 ms | 0 |
| Thu 08 | 0 | 0.0 | 49 ms | 0 |
| Thu 10 | 0 | 0.0 | 36 ms | 0 |
| Thu 12 | 0 | 0.0 | 72 ms | 0 |
| Thu 14 | 0 | 0.0 | 153 ms | 0 |
| Thu 16 | 0 | 0.0 | 96 ms | 0 |
| Thu 18 | 0 | 0.0 | 80 ms | 0 |
| Thu 21 | 0 | 0.0 | 59 ms | 0 |
| Thu 23 | 0 | 0.0 | 115 ms | 0 |
| Fri 01 | 0 | 0.0 | 84 ms | 0 |
| Fri 03 | 0 | 0.0 | 113 ms | 0 |
| Fri 05 | 0 | 0.0 | 79 ms | 0 |
| Fri 07 | 0 | 0.0 | 34 ms | 0 |
| Fri 09 | 0 | 0.0 | 57 ms | 0 |
| Fri 11 | 0 | 0.0 | 42 ms | 0 |
| Fri 13 | 0 | 0.0 | 54 ms | 0 |
| Fri 15 | 0 | 0.0 | 95 ms | 0 |
| Fri 17 | 0 | 0.0 | 63 ms | 0 |
| Fri 19 | 0 | 0.0 | 77 ms | 0 |
| Fri 21 | 0 | 0.0 | 51 ms | 0 |
| Fri 23 | 0 | 0.0 | 73 ms | 0 |
| Sat 01 | 0 | 0.0 | 51 ms | 0 |
| Sat 03 | 0 | 0.0 | 62 ms | 0 |
| Sat 05 | 0 | 0.0 | 53 ms | 0 |
| Sat 06 | 0 | 0.0 | 55 ms | 0 |
| Sat 07 | 0 | 0.0 | 39 ms | 0 |
| Sat 09 | 0 | 0.0 | 52 ms | 0 |
| Sat 11 | 0 | 0.0 | 97 ms | 0 |
| Sat 14 | 0 | 0.0 | 32 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Give Lively 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 Give Lively goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Give Lively alerts to Slack, Discord or a webhook — free.
We track Give Lively (givelively.org) as part of the Productivity group. We built and support a powerful and practical fundraising platform that is free for nonprofits and intuitively easy to use for donors. Sign up today for Fundraising Pages, Text-to-Donate, Peer-to-Peer, Event Ticketing, and more!
Give Lively publishes an official status page at status.givelively.org; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
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: 60 ms average, 32–97 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Give Lively incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
60 ms on average over the last 24 hours (32–97 ms).
Yes, at https://status.givelively.org.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Give Lively here at once, the problem is on Give Lively'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 Give Lively. 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.