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 1 hr ago. Last stored result reached it in 567 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 169 ms | 0 |
| Mon 17 | 0 | 0.0 | 218 ms | 0 |
| Mon 20 | 0 | 0.0 | 266 ms | 0 |
| Mon 22 | 0 | 0.0 | 139 ms | 0 |
| Tue 00 | 0 | 0.0 | 65 ms | 0 |
| Tue 02 | 0 | 0.0 | 145 ms | 0 |
| Tue 04 | 0 | 0.0 | 73 ms | 0 |
| Tue 06 | 0 | 0.0 | 261 ms | 0 |
| Tue 08 | 0 | 0.0 | 361 ms | 0 |
| Tue 10 | 0 | 0.0 | 244 ms | 0 |
| Tue 12 | 0 | 0.0 | 215 ms | 0 |
| Tue 13 | 0 | 0.0 | 146 ms | 0 |
| Tue 15 | 0 | 0.0 | 236 ms | 0 |
| Tue 17 | 0 | 0.0 | 79 ms | 0 |
| Tue 19 | 0 | 0.0 | 687 ms | 0 |
| Tue 22 | 0 | 0.0 | 342 ms | 0 |
| Wed 00 | 0 | 0.0 | 599 ms | 0 |
| Wed 02 | 0 | 0.0 | 157 ms | 0 |
| Wed 04 | 0 | 0.0 | 609 ms | 0 |
| Wed 06 | 0 | 0.0 | 224 ms | 0 |
| Wed 09 | 0 | 0.0 | 245 ms | 0 |
| Wed 11 | 0 | 0.0 | 140 ms | 0 |
| Wed 13 | 0 | 0.0 | 147 ms | 0 |
| Wed 15 | 0 | 0.0 | 141 ms | 0 |
| Wed 17 | 0 | 0.0 | 98 ms | 0 |
| Wed 20 | 0 | 0.0 | 174 ms | 0 |
| Wed 22 | 0 | 0.0 | 269 ms | 0 |
| Thu 00 | 0 | 0.0 | 395 ms | 0 |
| Thu 02 | 0 | 0.0 | 152 ms | 0 |
| Thu 04 | 0 | 0.0 | 167 ms | 0 |
| Thu 06 | 0 | 0.0 | 244 ms | 0 |
| Thu 08 | 0 | 0.0 | 150 ms | 0 |
| Thu 10 | 0 | 0.0 | 94 ms | 0 |
| Thu 12 | 0 | 0.0 | 145 ms | 0 |
| Thu 15 | 0 | 0.0 | 803 ms | 0 |
| Thu 17 | 0 | 0.0 | 184 ms | 0 |
| Thu 19 | 0 | 0.0 | 36 ms | 0 |
| Thu 21 | 0 | 0.0 | 58 ms | 0 |
| Thu 23 | 0 | 0.0 | 320 ms | 0 |
| Fri 01 | 0 | 0.0 | 592 ms | 0 |
| Fri 03 | 0 | 0.0 | 165 ms | 0 |
| Fri 05 | 0 | 0.0 | 651 ms | 0 |
| Fri 07 | 0 | 0.0 | 43 ms | 0 |
| Fri 09 | 0 | 0.0 | 60 ms | 0 |
| Fri 11 | 0 | 0.0 | 42 ms | 0 |
| Fri 13 | 0 | 0.0 | 185 ms | 0 |
| Fri 15 | 0 | 0.0 | 272 ms | 0 |
| Fri 17 | 0 | 0.0 | 346 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 Slamdot 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 Slamdot goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Slamdot alerts to Slack, Discord or a webhook — free.
Slamdot, at slamdot.com, is one of the Productivity services we monitor. Based in Knoxville, TN, Slamdot offers affordable Web Design, SEO, and Digital Marketing to small businesses nationwide since 2005.
Slamdot publishes an official status page at status.slamdot.com; when we can read it, its incident level is folded into the status shown here.
Common problems for productivity services: files not syncing, editors not loading, and sign-in problems.
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: 240 ms average, 36–651 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Slamdot incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
240 ms on average over the last 24 hours (36–651 ms).
Yes, at https://status.slamdot.com.
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 Slamdot here at once, the problem is on Slamdot'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 Slamdot. 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.