Forsta incident

Forsta Plus: German DE SaaS Site is returning to normal operation we are continuing to monitor it.

Minor Resolved View vendor source →

Forsta experienced a minor incident on June 5, 2025 affecting CATI and Task system and 1 more component, lasting 1d 7h. The incident has been resolved; the full update timeline is below.

Started
Jun 05, 2025, 08:31 AM UTC
Resolved
Jun 06, 2025, 04:21 PM UTC
Duration
1d 7h
Detected by Pingoru
Jun 05, 2025, 08:31 AM UTC

Affected components

CATITask systemSurvey designer

Update timeline

  1. investigating Jun 05, 2025, 08:31 AM UTC

    Updated status will be provided within 30 minutes.

  2. investigating Jun 05, 2025, 09:00 AM UTC

    We are continuing to investigate the issue. Updated status will be provided within 30 minutes

  3. investigating Jun 05, 2025, 09:01 AM UTC

    We are continuing to investigate this issue.

  4. investigating Jun 05, 2025, 09:53 AM UTC

    We are continuing to investigate. Updated status will be provided within 60 minutes

  5. investigating Jun 05, 2025, 10:56 AM UTC

    We are continuing to investigate. Updated status will be provided within 60 minutes

  6. investigating Jun 05, 2025, 12:01 PM UTC

    We are continuing to investigate. Updated status will be provided within 60 minutes

  7. investigating Jun 05, 2025, 12:54 PM UTC

    We are continuing to investigate. Updated status will be provided within 60 minutes

  8. investigating Jun 05, 2025, 01:54 PM UTC

    We are continuing to investigate. Updated status will be provided within 60 minutes

  9. investigating Jun 05, 2025, 03:07 PM UTC

    We are continuing to investigate. Updated status will be provided within 60 minutes

  10. monitoring Jun 05, 2025, 09:15 PM UTC

    We have been restoring functionality throughout the day/Evening, and are seeing better performance in our testing of the site. Please continue to work with Forsta Support if you run into any additional issues using the Forsta Plus DE SaaS site.

  11. monitoring Jun 05, 2025, 10:26 PM UTC

    We are continuing to monitor for any further issues.

  12. resolved Jun 06, 2025, 04:21 PM UTC

    This issue has been resolved.