User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
Is Litmus down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → litmus.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 25 min ago. Last stored result reached it in 55 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 50 ms | 0 |
| Mon 21 | 0 | 0.0 | 90 ms | 0 |
| Mon 23 | 0 | 0.0 | 80 ms | 0 |
| Tue 01 | 0 | 0.0 | 58 ms | 0 |
| Tue 03 | 0 | 0.0 | 136 ms | 0 |
| Tue 05 | 0 | 0.0 | 136 ms | 0 |
| Tue 07 | 0 | 0.0 | 165 ms | 0 |
| Tue 09 | 0 | 0.0 | 109 ms | 0 |
| Tue 11 | 0 | 0.0 | 77 ms | 0 |
| Tue 14 | 0 | 0.0 | 67 ms | 0 |
| Tue 16 | 0 | 0.0 | 98 ms | 0 |
| Tue 18 | 0 | 0.0 | 77 ms | 0 |
| Tue 20 | 0 | 0.0 | 97 ms | 0 |
| Tue 23 | 0 | 0.0 | 144 ms | 0 |
| Wed 01 | 0 | 0.0 | 119 ms | 0 |
| Wed 03 | 0 | 0.0 | 62 ms | 0 |
| Wed 05 | 0 | 0.0 | 138 ms | 0 |
| Wed 08 | 0 | 0.0 | 126 ms | 0 |
| Wed 10 | 0 | 0.0 | 111 ms | 0 |
| Wed 12 | 0 | 0.0 | 133 ms | 0 |
| Wed 14 | 0 | 0.0 | 97 ms | 0 |
| Wed 16 | 0 | 0.0 | 47 ms | 0 |
| Wed 18 | 0 | 0.0 | 80 ms | 0 |
| Wed 21 | 0 | 0.0 | 112 ms | 0 |
| Wed 23 | 0 | 0.0 | 79 ms | 0 |
| Thu 01 | 0 | 0.0 | 128 ms | 0 |
| Thu 03 | 0 | 0.0 | 170 ms | 0 |
| Thu 05 | 0 | 0.0 | 137 ms | 0 |
| Thu 07 | 0 | 0.0 | 171 ms | 0 |
| Thu 09 | 0 | 0.0 | 134 ms | 0 |
| Thu 11 | 0 | 0.0 | 126 ms | 0 |
| Thu 13 | 0 | 0.0 | 99 ms | 0 |
| Thu 16 | 0 | 0.0 | 135 ms | 0 |
| Thu 18 | 0 | 0.0 | 55 ms | 0 |
| Thu 20 | 0 | 0.0 | 115 ms | 0 |
| Thu 22 | 0 | 0.0 | 84 ms | 0 |
| Fri 00 | 0 | 0.0 | 96 ms | 0 |
| Fri 02 | 0 | 0.0 | 104 ms | 0 |
| Fri 04 | 0 | 0.0 | 122 ms | 0 |
| Fri 06 | 0 | 0.0 | 49 ms | 0 |
| Fri 08 | 0 | 0.0 | 55 ms | 0 |
| Fri 10 | 0 | 0.0 | 109 ms | 0 |
| Fri 11 | 0 | 0.0 | 52 ms | 0 |
| Fri 13 | 0 | 0.0 | 54 ms | 0 |
| Fri 15 | 0 | 0.0 | 58 ms | 0 |
| Fri 17 | 0 | 0.0 | 103 ms | 0 |
| Fri 18 | 0 | 0.0 | 121 ms | 0 |
| Fri 19 | 0 | 0.0 | 55 ms | 0 |
Reliability
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.
Embed this status: free live Litmus badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Litmus yet. Outages of 10 minutes or more get their own page here.
Having trouble with Litmus?
One report per service every 10 minutes from this network. No account.
Follow Litmus
Get an email when Litmus goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Litmus alerts to Slack, Discord or a webhook — free.
About Litmus
Litmus, at litmus.com, is one of the Productivity services we monitor. Litmus is the all-in-one email marketing platform that provides the tools and solutions your team needs to make every send count.
Litmus publishes an official status page at status.litmus.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: 85 ms average, 49–160 ms range across 14 successful checks.
Questions
Is Litmus down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Litmus last down?
We have not recorded a public Litmus incident since monitoring began 8 days ago.
What is Litmus's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Litmus respond?
85 ms on average over the last 24 hours (49–160 ms).
Does Litmus have an official status page?
Yes, at https://status.litmus.com.
Litmus not working for me but the status is fine. What now?
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 Litmus here at once, the problem is on Litmus'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 Litmus. 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.