InSurvey Outage History

InSurvey is up right now

InSurvey had 4 outages in the last 2 years totaling 5h 38m of downtime — averaging 0.2 incidents per month.

There were 4 InSurvey outages since April 8, 2025 totaling 5h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.insurvey.com

Major September 25, 2026

Knowledge base (docs.insurvey.com) outage

Detected by Pingoru
Sep 25, 2026, 05:03 AM UTC
Resolved
Sep 25, 2026, 05:08 AM UTC
Duration
5m
Affected: Knowledge base (docs.insurvey.com)
Timeline · 2 updates
  1. investigating Sep 25, 2026, 05:03 AM UTC

    Knowledge base (docs.insurvey.com) cannot be accessed at the moment. This incident was created by an automated monitoring service.

  2. resolved Sep 25, 2026, 05:08 AM UTC

    Knowledge base (docs.insurvey.com) is now operational! This update was created by an automated monitoring service.

Read the full incident report →

Major September 23, 2026

AI-assistant outage

Detected by Pingoru
Sep 23, 2026, 12:13 PM UTC
Resolved
Sep 23, 2026, 02:10 PM UTC
Duration
1h 57m
Affected: Core system services (AI-assistant)
Timeline · 1 update
  1. investigating Sep 23, 2026, 12:13 PM UTC

    AI-assistant cannot be accessed at the moment. This incident was created by an automated monitoring service.

Read the full incident report →

Major April 20, 2026

Blog (blogg.cloudconnected.se) outage

Detected by Pingoru
Apr 20, 2026, 10:15 AM UTC
Resolved
Apr 20, 2026, 10:20 AM UTC
Duration
5m
Timeline · 2 updates
  1. investigating Apr 20, 2026, 10:15 AM UTC

    Blog (blogg.cloudconnected.se) cannot be accessed at the moment. This incident was created by an automated monitoring service..

  2. resolved Apr 20, 2026, 10:20 AM UTC

    Blog (blogg.cloudconnected.se) is now operational! This update was created by an automated monitoring service..

Read the full incident report →

Minor April 9, 2026

Partial Service Disruption

Detected by Pingoru
Apr 09, 2026, 08:15 AM UTC
Resolved
Apr 09, 2026, 11:46 AM UTC
Duration
3h 31m
Timeline · 4 updates
  1. investigating Apr 09, 2026, 08:15 AM UTC

    We are currently investigating this incident..

  2. identified Apr 09, 2026, 08:30 AM UTC

    We are continuing to work on a fix for this incident..

  3. monitoring Apr 09, 2026, 09:23 AM UTC

    We implemented a fix and are currently monitoring the result..

  4. resolved Apr 09, 2026, 11:46 AM UTC

    This incident has been resolved..

Read the full incident report →