Is Qualtrics Down?

No — Qualtrics is up

Reachable from all 8 checked regions

Average response time: 286ms

Last checked 29 minutes ago · 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

309ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 55 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

55-day clean streak

Aug 22 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

189ms

DNS 140ms TCP 2ms TLS 17ms TTFB 176ms

lhr

346ms

DNS 283ms TCP 1ms TLS 4ms TTFB 336ms

nrt

283ms

DNS 235ms TCP 1ms TLS 4ms TTFB 275ms

ord

157ms

DNS 58ms TCP 1ms TLS 7ms TTFB 137ms

sin

330ms

DNS 231ms TCP 2ms TLS 40ms TTFB 315ms

sjc

573ms

DNS 110ms TCP 45ms TLS 91ms TTFB 348ms

syd

221ms

DNS 177ms TCP 1ms TLS 4ms TTFB 208ms

yyz

193ms

DNS 147ms TCP 0ms TLS 3ms TTFB 173ms

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 up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

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 — the most recent check ran from 8 of them.
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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Qualtrics goes down

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

Start Free Monitoring

Free plan available No credit card required