Incident IQ incident

Intermittent Login Problems [Remediated]

Notice Resolved View vendor source →

Incident IQ experienced a notice incident on August 1, 2022 affecting Platform, lasting 13h 19m. The incident has been resolved; the full update timeline is below.

Started
Aug 01, 2022, 01:41 PM UTC
Resolved
Aug 02, 2022, 03:00 AM UTC
Duration
13h 19m
Detected by Pingoru
Aug 01, 2022, 01:41 PM UTC

Affected components

Platform

Update timeline

  1. investigating Aug 01, 2022, 01:41 PM UTC

    We are aware of and actively investigating reports of intermittent login issues. Our Engineering Team is currently identifying the cause and working on a solution. We understand how critical the Incident IQ platform is in supporting school districts. Resolving this issue is our highest priority. We will provide updates here as soon as they are available. Apologies for the inconvenience and thanks for your patience.

  2. investigating Aug 01, 2022, 01:54 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Aug 01, 2022, 02:18 PM UTC

    A fix has been implemented and we are monitoring the results. We will provide more details here as we complete our investigation. Thanks for your patience.

  4. monitoring Aug 01, 2022, 10:12 PM UTC

    We experienced intermittent site login and app/integration related issues between 7:30 AM and 9:20 AM EDT this morning. During our investigation, we found that certain combinations of specific rule filters and actions caused conflicts on the servers handling those requests. This scenario could cause apps to fail to display the correct data and prevent the necessary authentication for site login. No data was lost or impacted during this period. We immediately mitigated the issue and deployed additional server capacity as a buffer. We will continue monitoring site performance and are also deploying additional optimizations to ensure that this type of issue does not reoccur. Thanks for your patience as we worked to resolve this issue.

  5. resolved Aug 02, 2022, 06:15 PM UTC

    This incident has been resolved.