InSurvey had 5 outages in the last 2 years totaling 2h 2m of downtime — averaging 0.2 incidents per month.
There were 5 InSurvey outages since April 8, 2025 totaling 2h 2m of downtime. Each is summarised below — incident details, duration, and resolution information.
Knowledge base (docs.insurvey.com) cannot be accessed at the moment. This incident was created by an automated monitoring service.
Knowledge base (docs.insurvey.com) is now operational! This update was created by an automated monitoring service.
AI-assistant cannot be accessed at the moment. This incident was created by an automated monitoring service.
Type: Maintenance Affected Components: Print and receipt API, Messaging and notification API, Report and analysis export API, Respondent interface, Content Delivery Network (CDN), Core API, Administration interface, Authentication platform May 12, 04:00:00 GMT+0 - Identified - As part of our ongoing security improvements, we will enable Multi-Factor Authentication (MFA) for all customers during the scheduled maintenance window. This change is intended to enhance account security and protect against unauthorized access. Users may be prompted to configure MFA upon their next login after the maintenance is completed.
Type: Incident Duration: 5 minutes Affected Components: Blog (blogg.cloudconnected.se) Apr 20, 10:15:41 GMT+0 - Investigating - Blog (blogg.cloudconnected.se) cannot be accessed at the moment. This incident was created by an automated monitoring service. Apr 20, 10:20:56 GMT+0 - Resolved - Blog (blogg.cloudconnected.se) is now operational! This update was created by an automated monitoring service.
Type: Incident Duration: 3 hours and 31 minutes Affected Components: Core API, Print and receipt API, Messaging and notification API, Content Delivery Network (CDN), Report and analysis export API, Respondent interface, Administration interface, Authentication platform Apr 9, 08:15:00 GMT+0 - Investigating - We are currently investigating this incident. Apr 9, 11:46:13 GMT+0 - Resolved - This incident has been resolved. Apr 9, 08:30:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Apr 9, 09:23:10 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result.