Skip to content
PulseWatchOUTAGE.INTEL
Cursor logo

Productivity

Is Cursor down right now?

NormalOfficial status last polled Oct 9, 2026 09:14 UTCcursor.comOfficial status page

AI code editor and developer productivity platform

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

Is Cursor down right now?

No. Cursor 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 Oct 9, 2026 10:35 UTC

Normal

Cursor is operating normally

As of Oct 9, 2026 10:35 UTC

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

Reports 24h

0

Last incident

Oct 8, 2026 16: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 Cursor.

12

Incident days

18

No recorded incident

46h 36m

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

Sep 10Sep 15Sep 20Sep 25Sep 30Oct 501234

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

12

Days with incidents

2 incidents

Busiest day

46h 36m

Recorded duration

Report volume

0 reports in last 24H

10:30 AM02:00 PM05:30 PM09:00 PM12:30 AM04:00 AM07:30 AM00.511.52baseline 1

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Cursor: vendor-reported minor incident on October 8 (tracked 1h 26m)

Oct 8, 03:19 PM → Oct 8, 04:45 PM · 1h 26m · medium

Cursor 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 this incident for 1h 26m, closing it on 2026-10-08T16:45:42.221Z.

Duration
1h 26m
tracked by PulseWatch

Impact

PulseWatch recorded no user reports for this incident, so it cannot describe what users experienced. The incident is known from Cursor's own status page.

Incident timeline

  1. Oct 8, 03:19 PM

    The vendor reported a minor-impact incident on its own status page; PulseWatch began tracking it

  2. Oct 8, 03:19 PM

    Status updated: possible issue

  3. Oct 8, 04:45 PM

    PulseWatch closed the incident

Official updates

  1. Oct 8, 03:19 PM

    Cursor reported the incident on its status page.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on the vendor's own status page.

Reliability

Detected by PulseWatch

30-day uptime

93.5%

90-day uptime

95.9%

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

Other productivity 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 →
ResolvedMedium

Cursor: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

10/8/2026, 3:19:21 PM · 1h 26m

03:19 PM04:45 PM
Detection10/8/2026, 3:19:21 PM · 19h ago

Detected — medium severity

Cursor: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

Cursor: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

10/7/2026, 4:46:14 PM · 1h 29m

04:46 PM06:16 PM
Detection10/7/2026, 4:46:14 PM · 1d ago

Detected — medium severity

Cursor: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedHigh

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

10/6/2026, 9:19:34 PM · 2h 56m

09:19 PM12:15 AM
Detection10/6/2026, 9:19:34 PM · 2d ago

Detected — high severity

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

ResolvedMedium

Cursor: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

10/6/2026, 3:19:33 PM · 5h 58m

03:19 PM09:18 PM
Detection10/6/2026, 3:19:33 PM · 2d ago

Detected — medium severity

Cursor: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

ResolvedMedium

Cursor: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

9/29/2026, 4:45:30 PM · 4h 33m

04:45 PM09:19 PM
Detection9/29/2026, 4:45:30 PM · 9d ago

Detected — medium severity

Cursor: the vendor reports a minor-impact incident on its own status page. Single origin, not independently confirmed. At this stated impact it alerts no one until a second independent source agrees.

DetectionPeakStatus updateResolvedCrowd warning

Subscribe to updates

Get an email the moment Cursor 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

cursor.com