Skip to main content
Qualtrics logo

Is Qualtrics Down?

No — Qualtrics is up

Reachable from all 8 checked regions

Average response time: 463ms

Last checked · checks run every 6 hours

Official status page: https://status.qualtrics.com

Qualtrics uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
463ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 1 day measured so far. A dash means we have no measurement for that window.

30-day history

Jun 29: no data
Jun 30: no data
Jul 1: no data
Jul 2: no data
Jul 3: no data
Jul 4: no data
Jul 5: no data
Jul 6: no data
Jul 7: no data
Jul 8: no data
Jul 9: no data
Jul 10: no data
Jul 11: no data
Jul 12: no data
Jul 13: no data
Jul 14: no data
Jul 15: no data
Jul 16: no data
Jul 17: no data
Jul 18: no data
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: 100.00% uptime, 8 checks
Jun 29 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
994ms
DNS 248ms TCP 92ms TLS 95ms TTFB 550ms
arn
59ms
DNS 22ms TCP 3ms TLS 4ms TTFB 48ms
nrt
1278ms
DNS 157ms TCP 156ms TLS 143ms TTFB 622ms
ord
632ms
DNS 138ms TCP 20ms TLS 45ms TTFB 394ms
sin
405ms
DNS 354ms TCP 0ms TLS 8ms TTFB 398ms
sjc
22ms
DNS 3ms TCP 0ms TLS 2ms TTFB 18ms
syd
28ms
DNS 9ms TCP 0ms TLS 2ms TTFB 24ms
yyz
289ms
DNS 64ms TCP 26ms TLS 20ms TTFB 171ms

What Qualtrics does

Qualtrics runs surveys and experience programmes for companies and universities, covering distribution, response collection, dashboards and workflows. Research studies and customer feedback programmes have fixed fielding windows, so an outage during collection costs responses that cannot be recovered by extending a deadline afterwards.

What an outage looks like

Respondents reach a survey link that fails to load, and abandon rather than retry. Surveys open but responses error on submit, so partial data is recorded without the respondent knowing. Distribution by email or SMS stalls, delaying an entire send. Dashboards and reports load stale, and workflows that create tickets from responses stop firing.

What to do about it

Check status.qualtrics.com, which reports Survey Taking and Survey Editing separately from Distributions, Logins, Dashboards, Workflows and the API, so a broken dashboard does not mean collection has stopped. Pause a scheduled distribution rather than resending it, since a partially delivered send followed by a second one produces duplicate invitations to the same panel.

Is it down for everyone, or just you?

If this page says Qualtrics is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

HubSpot
HubSpot
Salesforce
Salesforce
Zendesk
Zendesk
Jotform
Jotform

Qualtrics outage FAQ

Are responses lost if Qualtrics goes down mid-survey?
Responses Qualtrics recorded are stored, and partial responses are usually retained as incomplete rather than discarded. What is genuinely lost is the respondent who hit a failing link and left, because nothing about that attempt is captured. For time-boxed fielding, that silent loss matters more than the responses already in the dataset.
Is Qualtrics down or is my survey link expired?
Surveys can be closed, quota-full or past their end date, and each produces a specific message rather than a failure to load. An outage gives timeouts or error pages instead. Check status.qualtrics.com and then the survey's own status in the control panel before assuming the platform is at fault, since expiry is far more common.
Should I resend a distribution that failed partway?
Not without checking what was delivered. Distributions is a separate component, and a send interrupted by an incident may have reached part of the list. Resending the whole list then invites some people twice, which damages response rates and looks careless to a panel. Review the distribution history first, then send only to the remainder.
Why do dashboards show old data after an outage?
Data Processing and Dashboards are tracked separately from survey taking, so responses can be arriving correctly while the reporting layer lags. After an incident the backlog usually clears on its own within a while. Treat a stale dashboard as a reporting delay rather than as evidence that responses were lost, and re-check before raising an alarm.
Do Qualtrics workflows run for responses collected during an incident?
Workflows is its own component, and actions triggered while it was degraded may not fire retroactively. A response that should have created a support ticket or an alert can land in the data without the follow-up ever happening. After an incident, reviewing the affected window manually is the only reliable way to catch those.

How we measure this

  • We request Qualtrics's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Qualtrics publishes an official status feed we read it too, and let it override us in both directions.

Get alerted when Qualtrics goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required