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

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

How many people have reported SurveyMonkey issues today?

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

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

Productivity

Is SurveyMonkey down right now?

NormalOfficial status last polled Oct 4, 2026 07:25 UTCwww.surveymonkey.com Official status page

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

Is SurveyMonkey down right now?

No. SurveyMonkey 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 4, 2026 07:36 UTC

Normal

SurveyMonkey is operating normally

As of Oct 4, 2026 07:36 UTC

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

Reports 24h

Last incident

Oct 2, 2026 23:35 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 SurveyMonkey.

Incident days

No recorded incident

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

1 incident

Busiest day

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

SurveyMonkey: vendor-reported minor incident on October 2 (tracked 5h 59m)

Oct 2, 05:36 PM → Oct 2, 11:35 PM · 5h 59m · medium

SurveyMonkey 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 5h 59m and closed tracking on 2026-10-02T23:35:36.156Z.

Duration

5h 59m

tracked by PulseWatch

Impact

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

Incident timeline

Oct 2, 05:36 PM
The vendor reported a minor-impact incident on its own status page; PulseWatch began tracking it
Oct 2, 05:36 PM
Status updated: possible issue
Oct 2, 11:35 PM
PulseWatch closed the incident

Official updates

Oct 2, 05:36 PM
SurveyMonkey reported the incident on its status page.
View official source

Reliability

Detected by PulseWatch

30-day uptime

98.7%

90-day uptime

98.9%

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

Be the first to post a report.

Incident timeline

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

Full history →

ResolvedMedium

SurveyMonkey: 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/2/2026, 5:36:02 PM · 5h 59m

05:36 PM11:35 PM

Detection10/2/2026, 5:36:02 PM · 1d ago

Detected — medium severity

ResolvedHigh

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

9/24/2026, 1:01:37 PM · 3h 0m

01:01 PM04:02 PM

Detection9/24/2026, 1:01:37 PM · 9d ago

Detected — high severity

ResolvedMedium