User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
funraise.org · 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 44 min ago. Last stored result reached it in 226 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 303 ms | 0 |
| Mon 14 | 0 | 0.0 | 140 ms | 0 |
| Mon 16 | 0 | 0.0 | 337 ms | 0 |
| Mon 19 | 0 | 0.0 | 201 ms | 0 |
| Mon 21 | 0 | 0.0 | 159 ms | 0 |
| Mon 23 | 0 | 0.0 | 327 ms | 0 |
| Tue 01 | 0 | 0.0 | 133 ms | 0 |
| Tue 03 | 0 | 0.0 | 176 ms | 0 |
| Tue 05 | 0 | 0.0 | 149 ms | 0 |
| Tue 07 | 0 | 0.0 | 154 ms | 0 |
| Tue 09 | 0 | 0.0 | 176 ms | 0 |
| Tue 11 | 0 | 0.0 | 175 ms | 0 |
| Tue 14 | 0 | 0.0 | 136 ms | 0 |
| Tue 16 | 0 | 0.0 | 199 ms | 0 |
| Tue 18 | 0 | 0.0 | 287 ms | 0 |
| Tue 20 | 0 | 0.0 | 320 ms | 0 |
| Tue 23 | 0 | 0.0 | 400 ms | 0 |
| Wed 01 | 0 | 0.0 | 186 ms | 0 |
| Wed 03 | 0 | 0.0 | 176 ms | 0 |
| Wed 05 | 0 | 0.0 | 152 ms | 0 |
| Wed 08 | 0 | 0.0 | 386 ms | 0 |
| Wed 10 | 0 | 0.0 | 139 ms | 0 |
| Wed 12 | 0 | 0.0 | 122 ms | 0 |
| Wed 14 | 0 | 0.0 | 268 ms | 0 |
| Wed 16 | 0 | 0.0 | 236 ms | 0 |
| Wed 18 | 0 | 0.0 | 235 ms | 0 |
| Wed 21 | 0 | 0.0 | 174 ms | 0 |
| Wed 23 | 0 | 0.0 | 156 ms | 0 |
| Thu 01 | 0 | 0.0 | 149 ms | 0 |
| Thu 03 | 0 | 0.0 | 268 ms | 0 |
| Thu 05 | 0 | 0.0 | 194 ms | 0 |
| Thu 07 | 0 | 0.0 | 261 ms | 0 |
| Thu 09 | 0 | 0.0 | 286 ms | 0 |
| Thu 11 | 0 | 0.0 | 225 ms | 0 |
| Thu 13 | 0 | 0.0 | 142 ms | 0 |
| Thu 15 | 0 | 0.0 | 640 ms | 0 |
| Thu 17 | 0 | 0.0 | 316 ms | 0 |
| Thu 19 | 0 | 0.0 | 234 ms | 0 |
| Thu 22 | 0 | 0.0 | 424 ms | 0 |
| Fri 00 | 0 | 0.0 | 169 ms | 0 |
| Fri 02 | 0 | 0.0 | 173 ms | 0 |
| Fri 04 | 0 | 0.0 | 176 ms | 0 |
| Fri 06 | 0 | 0.0 | 186 ms | 0 |
| Fri 08 | 0 | 0.0 | 145 ms | 0 |
| Fri 10 | 0 | 0.0 | 195 ms | 0 |
| Fri 12 | 0 | 0.0 | 132 ms | 0 |
| Fri 14 | 0 | 0.0 | 142 ms | 0 |
| Fri 16 | 0 | 0.0 | 226 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 Funraise 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 Funraise goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Funraise alerts to Slack, Discord or a webhook — free.
Funraise is listed in our Cloud & developer category and checked at funraise.org. Funraise makes nonprofit fundraising a piece of cake. With truly innovative features and tools, fundraising is easier than ever. Power up your nonprofit.
Funraise publishes an official status page at status.funraise.org; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong 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: 204 ms average, 112–424 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 Funraise incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
204 ms on average over the last 24 hours (112–424 ms).
Yes, at https://status.funraise.org.
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 Funraise here at once, the problem is on Funraise'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 Funraise. 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.