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 2 hr ago. Last stored result reached it in 244 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 14 | 0 | 0.0 | 141 ms | 0 |
| Tue 17 | 0 | 0.0 | 466 ms | 0 |
| Tue 19 | 0 | 0.0 | 70 ms | 0 |
| Tue 21 | 0 | 0.0 | 126 ms | 0 |
| Tue 23 | 0 | 0.0 | 198 ms | 0 |
| Wed 01 | 0 | 0.0 | 184 ms | 0 |
| Wed 04 | 0 | 0.0 | 138 ms | 0 |
| Wed 06 | 0 | 0.0 | 337 ms | 0 |
| Wed 08 | 0 | 0.0 | 213 ms | 0 |
| Wed 11 | 0 | 0.0 | 1061 ms | 0 |
| Wed 13 | 0 | 0.0 | 209 ms | 0 |
| Wed 15 | 0 | 0.0 | 290 ms | 0 |
| Wed 17 | 0 | 0.0 | 194 ms | 0 |
| Wed 19 | 0 | 0.0 | 122 ms | 0 |
| Wed 21 | 0 | 0.0 | 137 ms | 0 |
| Thu 00 | 0 | 0.0 | 165 ms | 0 |
| Thu 02 | 0 | 0.0 | 275 ms | 0 |
| Thu 04 | 0 | 0.0 | 253 ms | 0 |
| Thu 06 | 0 | 0.0 | 246 ms | 0 |
| Thu 08 | 0 | 0.0 | 115 ms | 0 |
| Thu 10 | 0 | 0.0 | 355 ms | 0 |
| Thu 12 | 0 | 0.0 | 166 ms | 0 |
| Thu 14 | 0 | 0.0 | 360 ms | 0 |
| Thu 16 | 0 | 0.0 | 285 ms | 0 |
| Thu 18 | 0 | 0.0 | 200 ms | 0 |
| Thu 20 | 0 | 0.0 | 72 ms | 0 |
| Thu 22 | 0 | 0.0 | 99 ms | 0 |
| Fri 00 | 0 | 0.0 | 142 ms | 0 |
| Fri 02 | 0 | 0.0 | 146 ms | 0 |
| Fri 05 | 0 | 0.0 | 410 ms | 0 |
| Fri 06 | 0 | 0.0 | 221 ms | 0 |
| Fri 08 | 0 | 0.0 | 96 ms | 0 |
| Fri 10 | 0 | 0.0 | 151 ms | 0 |
| Fri 11 | 0 | 0.0 | 108 ms | 0 |
| Fri 13 | 0 | 0.0 | 106 ms | 0 |
| Fri 15 | 0 | 0.0 | 392 ms | 0 |
| Fri 17 | 0 | 0.0 | 212 ms | 0 |
| Fri 18 | 0 | 0.0 | 103 ms | 0 |
| Fri 20 | 0 | 0.0 | 134 ms | 0 |
| Fri 23 | 0 | 0.0 | 130 ms | 0 |
| Sat 00 | 0 | 0.0 | 88 ms | 0 |
| Sat 02 | 0 | 0.0 | 228 ms | 0 |
| Sat 04 | 0 | 0.0 | 193 ms | 0 |
| Sat 07 | 0 | 0.0 | 108 ms | 0 |
| Sat 09 | 0 | 0.0 | 88 ms | 0 |
| Sat 11 | 0 | 0.0 | 113 ms | 0 |
| Sat 13 | 0 | 0.0 | 122 ms | 0 |
| Sat 16 | 0 | 0.0 | 244 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 SocialJuice 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 SocialJuice goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
We track SocialJuice (socialjuice.io) as part of the Social group. Collect, import, and share customer reviews and video testimonials with Socialjuice. Build trust with no-code website widgets and social media images.
SocialJuice publishes an official status page at status.socialjuice.io; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with social services: feeds not loading, posts or messages not sending, and login loops.
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: 141 ms average, 88–244 ms range across 11 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public SocialJuice incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
141 ms on average over the last 24 hours (88–244 ms).
Yes, at https://status.socialjuice.io.
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 SocialJuice here at once, the problem is on SocialJuice'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 SocialJuice. 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.