Skip to content
PulseWatchOUTAGE.INTEL
CockroachDB logo

Other

Is CockroachDB down right now?

NormalOfficial status last polled Sep 27, 2026 03:24 UTCwww.cockroachlabs.comOfficial status page

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

Is CockroachDB down right now?

No. CockroachDB has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Sep 27, 2026 03:59 UTC

Normal

CockroachDB is operating normally

As of Sep 27, 2026 03:59 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

0

Last incident

Sep 17, 2026 21:45 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

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

2

Incident days

28

No recorded incident

6h 5m

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 CockroachDB. Hover a day for detail.

Aug 29Sep 3Sep 8Sep 13Sep 18Sep 2301234

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

2

Days with incidents

1 incident

Busiest day

6h 5m

Recorded duration

Report volume

0 reports in last 24H

03:45 AM07:15 AM10:45 AM02:15 PM05:45 PM09:15 PM12:45 AM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

CockroachDB outage on September 17 — 2h 19m disruption

Sep 17, 07:25 PM → Sep 17, 09:45 PM · 2h 19m · high

A high-severity incident affecting CockroachDB was reported by the vendor on their status page. This disruption began on September 17, 2026, at 19:25 UTC. The incident was resolved on September 17, 2026, at 21:45 UTC.

Peak reports
0
in 15 min
Total reports
0
during outage
Duration
2h 19m
until recovery

Impact

The CockroachDB service experienced a high-severity disruption lasting 2 hours and 19 minutes. This incident was detected via automated signals, including the vendor's own status page. No user-reported data was collected for this incident, and therefore no specific user-reported issues, regions, or affected features can be detailed.

Outage timeline

  1. Sep 17, 07:25 PM

    PulseWatch detected the incident from automated vendor and probe signals (high severity)

  2. Sep 17, 07:25 PM

    Status updated: possible issue

  3. Sep 17, 09:45 PM

    Signals cleared — incident resolved

Official updates

  1. Sep 17, 07:25 PM

    CockroachDB status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals.

Reliability

Detected by PulseWatch

30-day uptime

99.16%

90-day uptime

99.72%

Calculated from CockroachDB'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.

500 characters left

Be the first to post a report.

Incident timeline

Scrub through detection, peak, status updates, and resolution.

Full history →
ResolvedHigh

CockroachDB: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch CockroachDB or have an alert rule on it can be alerted, labelled vendor-reported.

9/17/2026, 7:25:53 PM · 2h 19m

07:25 PM09:45 PM
Detection9/17/2026, 7:25:53 PM · 9d ago

Detected — high severity

CockroachDB: the vendor reports a major-impact incident on its own status page. Single origin, not independently confirmed. Users who watch CockroachDB or have an alert rule on it can be alerted, labelled vendor-reported.

ResolvedMedium

CockroachDB incident correlated across 1 signal group: official/vendor.

9/1/2026, 4:12:10 PM · 3h 45m

04:12 PM07:57 PM
Detection9/1/2026, 4:12:10 PM · 25d ago

Detected — medium severity

CockroachDB incident correlated across 1 signal group: official/vendor.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment CockroachDB enters an incident — and again when it's resolved. No account required.

Free for anyone. Unsubscribe anytime from any email we send.

Signal quality

Live signal

Status
Normal
Monitoring
Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
Coverage
Verified against the vendor's own incident history
Reports (24h)
0
Baseline / hour
5
Open threshold
3x

Official site

www.cockroachlabs.com