PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Litmus is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Litmus. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Litmus issues today?

As of Sep 28, 2026 10:36 UTC, 0 users had reported issues with Litmus in the previous 24 hours.

How can I report a Litmus outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Communication

Is Litmus down right now?

UnknownOfficial status last polled Sep 28, 2026 09:43 UTClitmus.com Official status page

Are you on the Litmus team and see something inaccurate? Report it to us. We respond within one business day.

Is Litmus down right now?

Vendor-reported issue. Litmus: Partial System Outage Affected scope is described in the vendor notice; service-wide impact is not established. Independent corroboration has not been established.

Status as of Sep 28, 2026 10:36 UTC

UnknownVendor-reported issue

Litmus: vendor reports an issue

As of Sep 28, 2026 10:36 UTC

Partial System Outage Affected scope is described in the vendor notice; service-wide impact is not established. Independent corroboration has not been established.

No product check is currently qualified to corroborate an incident for this service. Overall service status has not been established.

Reports 24h

Last incident

Sep 5, 2026 08:46 UTC

Trend

0/15m

Monitoring

Coverage gap

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

Vendor-reported

An official notice is available; independent agreement is unproven.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Litmus.

Incident days

No recorded incident

74h 49m

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Litmus. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

2 incidents

Busiest day

74h 49m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

Not calculated: Litmus is unknown, so there is no incident history to measure and no uptime figure is shown.

Other communication services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.