User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Social
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 38 min ago. Last stored result reached it in 68 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 01 | 0 | 0.0 | 81 ms | 0 |
| Tue 03 | 0 | 0.0 | 141 ms | 0 |
| Tue 06 | 0 | 0.0 | 116 ms | 0 |
| Tue 08 | 0 | 0.0 | 50 ms | 0 |
| Tue 10 | 0 | 0.0 | 63 ms | 0 |
| Tue 12 | 0 | 0.0 | 85 ms | 0 |
| Tue 14 | 0 | 0.0 | 88 ms | 0 |
| Tue 17 | 0 | 0.0 | 99 ms | 0 |
| Tue 19 | 0 | 0.0 | 93 ms | 0 |
| Tue 21 | 0 | 0.0 | 104 ms | 0 |
| Tue 23 | 0 | 0.0 | 115 ms | 0 |
| Wed 01 | 0 | 0.0 | 57 ms | 0 |
| Wed 04 | 0 | 0.0 | 142 ms | 0 |
| Wed 06 | 0 | 0.0 | 57 ms | 0 |
| Wed 08 | 0 | 0.0 | 128 ms | 0 |
| Wed 11 | 0 | 0.0 | 95 ms | 0 |
| Wed 13 | 0 | 0.0 | 158 ms | 0 |
| Wed 15 | 0 | 0.0 | 192 ms | 0 |
| Wed 17 | 0 | 0.0 | 100 ms | 0 |
| Wed 19 | 0 | 0.0 | 170 ms | 0 |
| Wed 21 | 0 | 0.0 | 182 ms | 0 |
| Wed 23 | 0 | 0.0 | 121 ms | 0 |
| Thu 02 | 0 | 0.0 | 170 ms | 0 |
| Thu 04 | 0 | 0.0 | 135 ms | 0 |
| Thu 06 | 0 | 0.0 | 182 ms | 0 |
| Thu 08 | 0 | 0.0 | 95 ms | 0 |
| Thu 10 | 0 | 0.0 | 104 ms | 0 |
| Thu 12 | 0 | 0.0 | 85 ms | 0 |
| Thu 14 | 0 | 0.0 | 76 ms | 0 |
| Thu 16 | 0 | 0.0 | 56 ms | 0 |
| Thu 18 | 0 | 0.0 | 127 ms | 0 |
| Thu 20 | 0 | 0.0 | 153 ms | 0 |
| Thu 22 | 0 | 0.0 | 81 ms | 0 |
| Fri 00 | 0 | 0.0 | 212 ms | 0 |
| Fri 02 | 0 | 0.0 | 109 ms | 0 |
| Fri 04 | 0 | 0.0 | 59 ms | 0 |
| Fri 07 | 0 | 0.0 | 139 ms | 0 |
| Fri 09 | 0 | 0.0 | 201 ms | 0 |
| Fri 10 | 0 | 0.0 | 46 ms | 0 |
| Fri 11 | 0 | 0.0 | 96 ms | 0 |
| Fri 12 | 0 | 0.0 | 104 ms | 0 |
| Fri 14 | 0 | 0.0 | 68 ms | 0 |
| Fri 16 | 0 | 0.0 | 148 ms | 0 |
| Fri 18 | 0 | 0.0 | 101 ms | 0 |
| Fri 20 | 0 | 0.0 | 117 ms | 0 |
| Fri 22 | 0 | 0.0 | 133 ms | 0 |
| Sat 00 | 0 | 0.0 | 58 ms | 0 |
| Sat 01 | 0 | 0.0 | 68 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for reportgarden 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 reportgarden goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send reportgarden alerts to Slack, Discord or a webhook — free.
reportgarden, at reportgarden.com, is one of the Social services we monitor. ReportGarden is the go-to tool for marketing agencies to generate custom dashboards and visualize date-driven metrics for SEO, Social Media, PPC, and more.
reportgarden publishes an official status page at status.reportgarden.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with social services: feeds not loading, posts or messages not sending, and login loops.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 103 ms average, 46–201 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public reportgarden incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
103 ms on average over the last 24 hours (46–201 ms).
Yes, at https://status.reportgarden.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For social services, watch for feeds not loading, posts or messages not sending, and login loops. If many people report reportgarden here at once, the problem is on reportgarden'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 reportgarden. 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.