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 Clerk is down?

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

How many people have reported Clerk issues today?

As of Oct 4, 2026 07:35 UTC, 0 users had reported issues with Clerk in the previous 24 hours.

How can I report a Clerk 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.

Other

Is Clerk down right now?

Vendor-reported issueOfficial status last polled Oct 4, 2026 06:13 UTCclerk.com Official status page

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

Is Clerk down right now?

Vendor-reported issue. Clerk: Development instances only - Apple rejecting emails Affected scope is described in the vendor notice; service-wide impact is not established. Independent corroboration has not been established.

Status as of Oct 4, 2026 07:35 UTC

Vendor-reported issueVendor-reported issue

Clerk: vendor reports an issue

As of Oct 4, 2026 07:35 UTC

Development instances only - Apple rejecting emails 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

Oct 1, 2026 16:33 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 Clerk.

Incident days

No recorded incident

132h 16m

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 Clerk. 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

132h 16m

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Clerk: vendor-reported minor incident on September 28 (tracked 3d 0h)

Sep 28, 04:31 PM → Oct 1, 04:33 PM · 3d 0h · medium

Clerk reported a minor-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 3d 0h, from Mon, 28 Sep 2026 16:31:57 GMT to Thu, 01 Oct 2026 16:33:32 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.

Duration

3d 0h

tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The vendor's own status page is the only source PulseWatch has for it.

Incident timeline

Sep 28, 04:31 PM
The vendor reported a minor-impact incident on its own status page; PulseWatch began tracking it
Sep 28, 04:31 PM
Status updated: possible issue
Oct 1, 04:33 PM
PulseWatch closed the incident

Official updates

Sep 28, 04:31 PM
Clerk reported the incident on its status page.
View official source

Reliability

Detected by PulseWatch

30-day uptime

81.1%

90-day uptime

93.6%

Calculated from Clerk's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other other 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.