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

3

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

MS Office365

Status.io

Webflow

Zapier

History (Last 7 days)

Temporary MaintenancePlanned Maintenance

Description

We will be undertaking some system patches which will cause some momentary downtime lasting around 15-30 seconds. During that time, respondents will be held in a "please wait" screen before being allowed to continue with their response. API will return 503 error, and app may return a 500 error.


Components

SmartSurvey Application, Survey Taking, Survey Taking (Custom Domains), API, Reports & Exports, SMS Services


Locations

UK


Schedule

May 17, 2026 9:15PM - May 17, 2026 11:15PM BST
May 17, 2026 8:15PM - May 17, 2026 10:15PM UTC


May 17, 2026 9:32PM BST
May 17, 2026 8:32PM UTC
UPDATE

Started

May 17, 2026 10:46PM BST
May 17, 2026 9:46PM UTC
UPDATE

All done.
AI Processing Degraded Performance

Incident Status

Degraded Performance


Components

AI Services


Locations

UK



May 15, 2026 4:59PM BST
May 15, 2026 3:59PM UTC
IDENTIFIED

We are currently experiencing some issues with our AI worker through Civo. We have are awaiting further information and will update this incident as we learn more.

May 17, 2026 9:32PM BST
May 17, 2026 8:32PM UTC
RESOLVED

This has now been resolved