All Systems Operational

Updated a few seconds ago

The SmartSurvey status page is updated when service issues are affecting multiple customers. If you are experiencing a service issue that has no status information on this page, please contact out support team by submitting a support ticket.

0

Active Incidents

0

Upcoming Maintenances

0

Days Since Last Incident

SmartSurvey Application




Operational

SmartSurvey Website




Operational

Survey Taking




Operational

Survey Taking (Custom Domains)




Operational

AI Services




Operational

API




Operational

Reports & Exports




Operational

Email Services




Operational

SMS Services




Operational

System Emails




Operational

Help Site




Operational

SmartPolls




Operational

External Services

ANS/UKFast

AWS S3

Azure

Cloudflare

Firetext

Mailjet

MessageBird

Microsoft 365

Status.io

Webflow

Zapier

History (Last 7 days)

AI Processing Degraded in USAPartial Service Disruption

Incident Status

Partial Service Disruption


Components

SmartSurvey Application, Survey Taking, AI Services


Locations

US



November 13, 2026 3:31PM GMT
November 13, 2026 3:31PM UTC
IDENTIFIED

We have seen some errors in AI Processing in the USA system and are deploying a fix.

November 13, 2026 3:45PM GMT
November 13, 2026 3:45PM UTC
MONITORING

Functionality is restored and we will continue to monitor.

November 13, 2026 4:47PM GMT
November 13, 2026 4:47PM UTC
RESOLVED

All AI functions appear to be back to normal now.
AI Processing - CivoOperational

Incident Status

Operational


Components

AI Services


Locations

UK



November 9, 2026 10:53AM GMT
November 9, 2026 10:53AM UTC
IDENTIFIED

Our external provider is currently experiencing instability issues in processing our requests. Our team are monitoring the situation and we hope to have a stable service back soon.

November 13, 2026 3:31PM GMT
November 13, 2026 3:31PM UTC
RESOLVED

All services should now be running as normal.

November 13, 2026 3:34PM GMT
November 13, 2026 3:34PM UTC
RESOLVED

This issue has now been fully resolved