Auvik 장애 기록

1. 2026년 10월 24일 오전 2:59 UTCinvestigating

   우리는 Auvik 구름을 격상시킬 것입니다. 세션은 3 시간 정도 걸립니다. 이 시간 동안, 당신은 Auvik로 로그인 할 수 없습니다. 네트워크 모니터링에도 방해가 될 수 있습니다. 궁금한 점이 있으시면 Auvik에서 아래쪽에 지원 버튼을 사용하십시오.

2. 2026년 10월 24일 오전 5:09 UTCresolved

   사건은 완전히 해결되었습니다. 일정한 서비스는 복원되고, 모든 시스템은 예상대로 작동합니다. 충격: 사용자는 서비스 중단과 관련된 문제가 더 이상 경험할 수 없습니다. 아직 문제가 발생하면 지원 팀에 도달하고 티켓을 업데이트하거나 아직보고하지 않은 문제가있는지 확인하십시오. 서비스는 완전히 복원되었습니다. 우리는 우리의 서비스에 어떤 혼란든지를 위해 apologize. 우리는 당신의 이해에 감사드립니다. 문제가 계속되면 지원 팀에 연락하는 것을 망설이지 마십시오. 내부 조사 후 RCA를 게시합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 10월 21일 오후 3:06 UTCidentified

   우리는 최근 공개 된 PHP 취약점 CVE-2026-109618 및 CVE-2026-109619의 인식입니다. AUVIK 제품은 PHP를 사용하지 않습니다. 우리는 잠재적 인 노출에 대한 우리의 더 넓은 환경을 검토하고 더 많은 정보를 사용할 수로 업데이트를 공유합니다.

2. 2026년 10월 22일 오후 12:33 UTCresolved

   우리는 최근 공개 된 PHP 취약점 CVE-2026-109618 및 CVE-2026-109619의 인식입니다. AUVIK 제품은 PHP를 사용하지 않습니다. 우리는 우리의 넓은 환경의 우리의 검토를 완료하고 다른 잠재적인 노출을 해결했습니다. 더 이상 업데이트가 예상되지 않습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 9월 3일 오전 11:12 UTCinvestigating

   우리는 현재 미국4 클러스터에 영향을 미치는 outage 보고서를 조사하고 있습니다. 충격: 고객은 이러한 사이트의 서비스 손실을 경험할 수 있습니다. 다른 모든 클러스터는 제대로 작용합니다. 다음 단계: 우리의 팀은 기여 요인을 식별하기 위해 노력하고 있습니다. 더 많은 정보로 업데이트를 공유합니다.

2. 2026년 9월 3일 오전 11:21 UTCidentified

   고객 충격: US4 클러스터의 고객은 시스템 복구 동안 사이트에 액세스 할 수 없습니다. 다른 모든 클러스터는 일반적으로 작동합니다. 현재 상태: 우리의 팀은 정전의 잠재적 인 원인을 확인하고 완화 조치를 취합니다. 다음 단계: 우리는 시스템의 복구를 모니터링하고 더 많은 정보로 다른 업데이트를 제공 할 것입니다. 문제가 계속되면 Auvik Support에 연락하여 충격을 추적하고 도움을 줄 수 있습니다.

3. 2026년 9월 3일 오전 11:52 UTCidentified

   고객 충격: US4 클러스터의 고객은 시스템 복구 동안 사이트에 액세스 할 수 없습니다. 다른 모든 클러스터는 일반적으로 작동합니다. 현재 상태: 사이트가 제대로 회복하고 사용할 수 있습니다. 다음 단계: 우리는 시스템의 복구를 모니터링하고 더 많은 정보로 다른 업데이트를 제공 할 것입니다. 문제가 계속되면 Auvik Support에 연락하여 충격을 추적하고 도움을 줄 수 있습니다.

4. 2026년 9월 3일 오후 12:04 UTCmonitoring

   우리는 문제를 해결하기 위해 변경 사항을 적용했습니다. 서비스는 일반적으로 운영 될 것으로 보인다, 나머지 사이트 복구. 우리는 안정성을 위해 바싹 감시하고 있습니다. 충격: 서비스는 정상적으로 작동되어야 합니다; 그러나, 당신이 문제를 직면하는 경우에, Auvik 지원에 보고하십시오. 다음 단계: 우리는 우리가 해결책을 확인 한 번 최종 업데이트를 게시합니다.

5. 2026년 9월 3일 오후 12:18 UTCresolved

   사건은 완전히 해결되고, 모든 서비스는 일반적으로 운영됩니다. 고객은 더 이상 관련 문제가 없습니다. 문제가 계속되면 Auvik Support에 연락하는 것을 망설이지 마십시오. 뿌리 원인 분석 (RCA)을 한 번 사용할 수 있습니다.

6. 2026년 9월 17일 오후 1:32 UTCpostmortem

   # 서비스 중단 - US4 서비스 중단 ## 뿌리 원인 분석 ### 사건의 기간 발견: 9월 03, 2026 07:05 UTC 해결: 9월 03, 2026 12:20 UTC ### 고객 충격 US4 환경에서 호스팅되는 고객은 시스템의 불안정한 운영 가용성을 경험했습니다. 충격에 의하여 포함되는 어려움 접근 위치 및 사용자 공용영역은, 시정을 감시하기 위하여 중단과 더불어. ### 원인 US4 환경에 있는 핵심 성분은 사용할 수 없습니다. 플랫폼의 자동화된 회복 과정은 완전히 재연결 및 회복 활동을 반복하기 위하여 지도되는 환경을 안정시키지 않았습니다. US4 환경의 전체 재시작은 정상 작동을 복원해야합니다. ### 효과 instability는 reliably communicating에서 US4 환경의 부분을 막습니다. 환경 재시작 및 고객 사이트 복구까지 많은 고객을 위한 서비스 중단이 발생했습니다. ### 미래 고려사항(s\) * 환경 복구에 관련된 중요한 구성 요소에 대한 탄력 및 중복 개선. * 자동화된 감시 및 paging를 강화하십시오 그래서 이 실패 본은 확인되고 더 빨리 escalated. * 유사한 구성 요소 실패가 전체 환경 재시작을 필요로하는 likelihood를 감소시키는 회복 행동을 검토하십시오.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 27일 오후 12:46 UTCinvestigating

   AU1 클러스터에서 호스팅되는 사이트에 영향을 미치는 가용성 문제의 보고서를 조사하고 있습니다. 고객 영향 AU1 클러스터의 고객은 서비스 중단을 경험할 수 있습니다. 다른 모든 클러스터는 불완전합니다. 다음 단계 우리의 팀은 기여 요인을 확인하기 위해 노력하고 있습니다. 우리는 더 많은 것을 배우기로 또 다른 업데이트를 공유 할 것입니다.

2. 2026년 8월 27일 오후 12:52 UTCidentified

   우리의 팀은 AU1 클러스터에서 호스팅되는 사이트에 영향을 미치는 가용성 문제의 의심스러운 원인을 확인하고 해결하기 위해 단계를 수행해야합니다. 제품 정보 AU1 클러스터의 고객은 서비스 중단을 경험할 수 있습니다. 다른 모든 클러스터는 불완전하게 남아있다. Auvik Support 관련 문제들을 보고해주셔서 더 많은 도움을 드릴 수 있습니다. 다음 단계 우리는 완화 조치를 적용하고 우리의 발전에 대한 업데이트를 제공합니다.

3. 2026년 8월 27일 오후 1:03 UTCmonitoring

   우리의 팀은 완화 조치를 적용하고, AU1 클러스터에서 호스팅되는 사이트에 대한 가용성을 복원했습니다. 일부 사이트는 계속 회복. 지속적인 안정성을 확인하기 위해 환경을 모니터링하고 있습니다. 제품 정보 고객은 더 이상 서비스 중단이 없습니다. 다른 모든 클러스터는 불완전하게 남아있다. Auvik Support 관련 문제들을 보고해주셔서 더 많은 도움을 드릴 수 있습니다. 다음 단계 우리는 계속 감시하고 우리가 문제점을 확인한 후에 또 다른 갱신을 완전히 해결할 것입니다.

4. 2026년 8월 27일 오후 1:30 UTCresolved

   사건은 완전히 해결되고, 모든 서비스는 일반적으로 운영됩니다. 고객은 더 이상 관련 문제가 없습니다. 문제가 계속되면 Auvik Support에 연락하는 것을 망설이지 마십시오. 뿌리 원인 분석 (RCA)을 한 번 사용할 수 있습니다.

5. 2026년 8월 28일 오후 3:21 UTCpostmortem

   # 서비스 중단 - AU1 클러스터의 가용성 문제 ## 뿌리 원인 분석 ### 사건의 기간 발견: 8월 27, 2026 12:20 - UTC 해결: 8월 27, 2026 13:15 - UTC ### 고객 충격 AU1 지역에 호스팅되는 고객은 Auvik 서비스의 임시 중단을 경험했습니다. 클라이언트에 따라 모니터링, 경고, 수집가 연결, 웹 인터페이스에 액세스는 약 1 시간 동안 사용할 수 없습니다. ### 원인 핵심 플랫폼 서비스에 있는 캐스케이드 실패는 중앙 코디네이테이션 성분을 포함하여 재시작하기 위하여 다수 서비스 성분을 기인했습니다. 이것은 AU1 지역 전체에 걸쳐 광범위하게 클라이언트 환경 재시작에서 유래했습니다. ### 효과 서비스 재시작 동안 클라이언트 환경이 일시적으로 사용할 수 없습니다. 플랫폼은 자동으로 회복됩니다. Post-recovery 검증은 정상적인 서비스 가동을 확인했습니다. ### 미래 고려사항(s\) * Continue evaluating resiliency 향상을 위한 핵심 서비스 조정 및 대규모 재시작 뒤에 복구 행동. * Continue using post-recovery validation checks to 확인 클라이언트 서비스 반환에 예상된 운영 후 넓은 서비스 재시작.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 17일 오후 5:53 UTCinvestigating

   우리는 inaccurate 통보의 높은 양의 보고입니다. 충격: 고객은 improper 경고 및 알림을 경험할 수 있습니다. 다음 서비스는 영향을받지 않습니다. V2 경고 알림. 다음 단계: 우리의 팀은 기여 요인을 식별하기 위해 노력하고 있습니다. 더 많은 정보로 업데이트를 공유합니다.

2. 2026년 8월 17일 오후 7:04 UTCinvestigating

   우리는 잘못된 알림으로 문제를 조사하기 위해 계속됩니다. 충격: 고객은 improper 경고 및 알림을 경험할 수 있습니다. 다음 서비스는 영향을받지 않습니다. V2 경고 알림. 다음 단계: 우리의 팀은 기여 요인을 식별하기 위해 노력하고 있습니다. 더 많은 정보로 업데이트를 공유합니다.

3. 2026년 8월 17일 오후 7:45 UTCidentified

   우리의 팀은 잘못된 알림의 의심스러운 원인을 확인하고 문제를 해결하기 위해 조치를 취합니다. 충격: 고객은 false paused 알림을 계속 경험할 수 있습니다. 다음 서비스는 영향을받지 않습니다. V2 경고 Auvik Support에 관한 모든 문제점을 보고하십시오. 다음 단계: 우리는 완화 조치를 적용하고 진행 상황을 제공합니다.

4. 2026년 8월 17일 오후 8:31 UTCmonitoring

   우리는 문제를 해결하기 위해 변경 사항을 적용했습니다. 경고 알림은 더 이상 사용자에게 전송되지 않아야 합니다. 우리는 안정성을 위한 긴밀한 모니터링 서비스입니다. 충격: 서비스는 정상적으로 작동되어야 합니다, 새로운 경고는 서비스 잡음까지 UI에서 연기될지도 모르다; 당신이 문제를 만나기 위하여 계속하면, Auvik 지원에 보고하십시오. 다음 단계: 우리는 우리가 해결책을 확인 한 번 최종 업데이트를 게시합니다.

5. 2026년 8월 17일 오후 11:15 UTCmonitoring

   우리는 UI에 표시되지 않는 알림을 일으키는 문제를 해결하기 위해 추가 변경 사항을 적용했습니다. 우리는 경고를 점차적으로 회복하고 가득 차있는 회복을 지키는 바싹 감시자 서비스를 계속하고 있습니다. 충격: 경고 알림은 더 이상 의도되지 않은 사용자에게 보내서는 안됩니다. Alerts는 여전히 UI에 표시되어 계속 복구 할 수 있습니다. 문제가 발생하면 Auvik Support에 신고하십시오. 다음 단계: 우리는 경고 복구 및 서비스 안정성을 계속 모니터링하고 문제가 완전히 해결되면 최종 업데이트를 제공합니다.

6. 2026년 8월 18일 오전 1:47 UTCmonitoring

   우리는 영향을받는 서비스의 전체 복구를 관찰하고 경고는 이제 모든 클러스터에 걸쳐 예상대로 UI에 나타납니다. 우리는 안정성을 보장하기 위해 긴밀한 모니터링 서비스를 계속하고 있습니다.

7. 2026년 8월 18일 오전 8:31 UTCmonitoring

   우리는 더 많은 문제를 모니터링하고 있습니다.

8. 2026년 8월 18일 오후 2:09 UTCidentified

   우리는 법적 경고에 의해 전송 예기치 않은 이메일의 보고서를 계속. 우리의 팀은 적극적으로 문제를 조사하고 있습니다. 다음 단계: 우리는 더 많은 정보로 또 다른 업데이트를 제공 할 것입니다.

9. 2026년 8월 18일 오후 3:35 UTCidentified

   우리는 예상치 못한 이메일 알림을 일으키는 법적 경고 문제를 계속 조사합니다. 우리의 조사는 진행을하고, 우리는 우리가 해결책을 향해 움직이는 것을 믿습니다. 우리는 우리의 발견을 검증하고 나머지 단계를 통해 작동합니다. 다음 단계: 우리는 우리가 해결책을 확인하거나 추가 정보로 다른 갱신을 제공할 것입니다

10. 2026년 8월 18일 오후 6:46 UTCidentified

    우리는 예상치 못한 이메일 알림을 일으키는 법적 경고 문제를 계속 조사합니다. 우리는 우리의 발견을 검증하고 나머지 단계를 통해 작동합니다. 다음 단계: 우리는 우리가 해결책을 확인하거나 추가 정보로 다른 갱신을 제공할 것입니다

11. 2026년 8월 18일 오후 9:30 UTCidentified

    우리는 이전의 변화에 따라 안정적인 경고 행동을보고 계속하고 서비스 경고는 완전히 회복됩니다. 우리는 지속적으로 안정성을 보장하기 위해 밀접하게 감시하고 있습니다. 충격: 서비스는 일반적으로 운영됩니다. 예기치 않은 경고 행동 또는 기타 아웃렛을 경험하면 Auvik Support에 신고하여 팀 조사 할 수 있습니다. 다음 단계: 우리는 계속 감시 서비스를 제공하고 우리가 완전히 해결된 문제점을 confident 한 번 마지막 갱신을 제공할 것입니다.

12. 2026년 8월 19일 오전 9:31 UTCmonitoring

    우리는 안정적인 경고 행동을보고 계속하고, 경고 서비스는 완전히 회복됩니다. 우리는 지속적으로 안정성을 보장하기 위해 밀접하게 감시하고 있습니다. 충격: 서비스는 일반적으로 운영됩니다. 예기치 않은 경고 행동 또는 기타 아웃렛을 경험하면 Auvik Support에 신고하여 팀 조사 할 수 있습니다.

13. 2026년 8월 19일 오후 2:33 UTCmonitoring

    우리는 안정적인 경고 행동을 계속 볼 수 있습니다. 우리는 지속적으로 안정성을 보장하기 위해 밀접하게 감시하고 있습니다. 충격: 서비스는 일반적으로 운영됩니다. 예기치 않은 경고 행동 또는 기타 아웃렛을 경험하면 Auvik Support에 신고하여 팀 조사 할 수 있습니다.

14. 2026년 8월 19일 오후 7:23 UTCmonitoring

    모든 시스템에서 안정적인 경고 행동을 관찰하는 것을 계속했습니다. 우리의 엔지니어링 팀은 지속적인 성능을 보장하기 위해 하루를 통해 적극적인 모니터링을 계속합니다. 현재 충격: 모든 서비스는 일반적으로 운영됩니다. 중요한 알림: 예기치 않은 경고 행위를 경험하거나 다른 outlier를 식별하는 경우, 조사를 위해 Auvik 지원에 즉시보고하십시오.

15. 2026년 8월 20일 오전 11:18 UTCmonitoring

    모든 시스템에서 안정적인 경고 행동을 관찰하는 것을 계속했습니다. 우리의 엔지니어링 팀은 적극적인 모니터링과 보고된 문제들을 해결합니다. 현재 충격: 모든 서비스는 일반적으로 운영됩니다. 중요한 알림: 예기치 않은 경고 행위를 경험하거나 다른 outlier를 식별하는 경우, 조사를 위해 Auvik 지원에 즉시보고하십시오.

16. 2026년 8월 20일 오후 2:11 UTCresolved

    사건은 완전히 해결되고, 모든 서비스는 일반적으로 운영됩니다. 고객은 더 이상 관련 문제가 없습니다. 문제가 계속되면 Auvik Support에 연락하는 것을 망설이지 마십시오. 뿌리 원인 분석 (RCA)을 한 번 사용할 수 있습니다.

17. 2026년 8월 24일 오후 5:54 UTCpostmortem

    # 서비스 등급 - Legacy Alerts 알림 ## 뿌리 원인 분석 ### 사건의 기간 발견: 8월 17, 2026 13:15 - UTC 해결: 8월 21, 2026 14:12 - UTC ### 고객 충격 레거시 Alerts를 사용하여 일부 고객은 false-positive alerts 및 unintended email notifications를 포함하여 inaccurate alert 알림을 경험했습니다. 재약 중, 일부 레거시 알림 처리가 지연되고, 사용자 인터페이스의 알림 가시성을 일시적으로 삭제했습니다. V2 Alerts는 사건 전체에 남아 있습니다. ### 원인 제품 출시는 새로운 환경에 대한 이전 기본 레거시 Alert 구성을 은퇴 할 예정이며 사용자 정의 레거시 Alerts와 함께 기존 고객에 의해 여전히 필요한 지원 경고 조건을 제거했습니다. 완전한 조건 없이, 특정 Legacy Alerts는 inaccurately 방아쇠를 수 있었습니다. 의약은 일시적으로 처리 하중을 증가시키고 경고 가시성을 지연시키는 데 기여하는 영향을받는 경고를 처리해야하며 과도한 알림을 경고합니다. ### 효과 법적인 유산 경고는 조건이 제시되지 않았을 때 트리거 할 수 있습니다, 일시 중지 후 다시 트리거, 또는 알림을 더 광범위하게 전달. 결과 in-service lag도 일시적으로 경고 표시를 지연. 엔지니어링은 필수 경고 구성을 복원, 무인화 된 넓은 이메일 협회를 제거, 처리 용량 증가, 과도하게 영향을받는 고객 환경을 수정. ### 미래 고려사항(s\) • Legacy Alerts의 이상적 볼륨에 대한 모니터링을 추가하여 예기치 않은 경고 활동이 일찍 감지 될 수 있습니다. • 경고 트리거, 알림 전달 및 포스트 교환 복구 동작을 포함하여 기존 사용자 정의 레거시 Alert에 대한 사전 릴리스 및 최종 테스트 확장. • Strengthen canary-release 검토 그래서 anomalies를 경고하고 더 넓은 배포 전에 이해.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 17일 오후 3:00 UTCinvestigating

   우리는 현재 유산 경고의 홍수에 대한 조사 보고서입니다. 제품 정보 기본 레거시 경고는 우리가 조사하는 동안 예상대로 일시적으로 작용하지 않습니다. 사용자 정의 레거시 경고도 영향을 미칠 수 있습니다. V2 경고는 현재 예상대로 일하고 있습니다. 다음 단계 우리의 팀은 적극적인 기여 요인을 식별 할 수 있습니다. 더 많은 정보로 추가 업데이트를 제공할 것입니다.

2. 2026년 8월 17일 오후 3:24 UTCidentified

   우리의 팀은 레거시 경고의 의심스러운 원인을 제대로 작동하지 않고 그것을 해결하기 위해 단계를 복용. 충격: 고객은 기존 경보를 계속 경험할 수 있습니다. 다음 서비스는 영향을받지 않습니다. V2 경고 Auvik Support에 관한 모든 문제점을 보고하십시오. 다음 단계: 우리는 완화 조치를 적용하고 진행 상황을 제공합니다.

3. 2026년 8월 17일 오후 4:24 UTCidentified

   우리의 팀은 레거시 경고의 의심스러운 원인을 제대로 작동하지 않고 그것을 해결하기 위해 단계를 복용. 충격: 고객은 기존 경보를 계속 경험할 수 있습니다. 다음 서비스는 영향을받지 않습니다. V2 경고 Auvik Support에 관한 모든 문제점을 보고하십시오. 다음 단계: 우리는 현재 EU1 클러스터링 클라이언트에 대한 수정을 적용하고 있습니다

4. 2026년 8월 17일 오후 4:38 UTCmonitoring

   우리는 문제를 해결하기 위해 변경 사항을 적용했습니다. 우리는 이제 서비스 수정을 압연하고 안정성을 위해 긴밀하게 모니터링합니다. 충격: 서비스는 정상적으로 작동되어야 합니다; 그러나, 당신이 문제를 직면하는 경우에, Auvik 지원에 보고하십시오. 다음 단계: 우리는 우리가 해결책을 확인 한 번 최종 업데이트를 게시합니다.

5. 2026년 8월 17일 오후 4:42 UTCresolved

   사건은 완전히 해결되고, 모든 서비스는 일반적으로 운영됩니다. 고객은 더 이상 관련 문제가 없습니다. 문제가 계속되면 Auvik Support에 연락하는 것을 망설이지 마십시오. 뿌리 원인 분석 (RCA)을 한 번 사용할 수 있습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 4월 14일 오전 12:32 UTCinvestigating

   We are currently investigating reports of a collector affecting monitoring. Impact: Customers may experience issues with the SNMP monitoring protocol. Other services are not affected. Auvik will be performing an emergency rollback of the collector upgrade this weekend. Next Steps: Our team is working to identify contributing factors. Updates will follow as more information becomes available.

2. 2026년 4월 14일 오전 1:10 UTCidentified

   Our team has identified a suspected cause of the Collector SNMP monitoring issue and is taking steps to remediate. Impact: Customers may continue to experience collector SNMP monitoring issues We will be having cluster maintenance windows as we roll back the collector upgrade on each cluster. We are rolling back the EU2 cluster currently. Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are implementing mitigation measures and will provide progress updates.

3. 2026년 4월 14일 오전 1:55 UTCidentified

   We are continuing to rollback collector versions on each cluster. Impact: Customers may continue to experience collector SNMP monitoring issues We will be having cluster maintenance windows as we roll back the collector upgrade on each cluster. We are rolling back the remaining clusters currently. Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are implementing mitigation measures and will provide progress updates.

4. 2026년 4월 14일 오전 2:33 UTCresolved

   The incident has been fully resolved. Regular service has been restored, and all systems are operating as expected. Impact: Users should no longer experience any issues related to this incident. If you are still experiencing issues, please do not hesitate to reach out to the support team and update your ticket or report any problems you haven't reported yet. Service has been fully restored. We apologize for the degradation in services. We thank you for your understanding. If you continue to experience issues, please don't hesitate to contact our support team. We will post an RCA after an internal investigation.

5. 2026년 4월 16일 오후 10:12 UTCpostmortem

   # Service Disruption - SNMPv3 Monitoring Loss Following Collector Upgrade ## Root Cause Analysis ### Duration of the incident Discovered: Apr 13, 2026 20:00 - UTC Resolved: Apr 13, 2026 22:32 - UTC ### Customer impact Customers experienced a loss of monitoring data from only devices using specific SNMPv3 configurations. While devices remained online and reachable, monitoring data was not collected, resulting in reduced visibility across environments. ### Cause A recent collector upgrade introduced changes to encryption handling that affected support for certain legacy SNMPv3 configurations. This resulted in failures when attempting to collect data from devices configured that way. ### Effect Monitoring data collection failed for affected devices across multiple clusters. This led to a noticeable drop in available device metrics and visibility, despite no loss of connectivity to the devices themselves. ### Future consideation\(s\) * Expand test coverage to include a broader range of SNMP configurations * Improve monitoring to detect drops in data collection more proactively * Strengthen validation processes for major upgrades and dependency changes * Implement additional safeguards to identify compatibility issues prior to release

1. 2026년 3월 8일 오후 7:10 UTCinvestigating

   Description: During our recent maintenance window, a subset of user accounts were inadvertently disabled. We are actively working to identify affected users and restore access as quickly as possible. Impact: Some customers may experience login issues when accessing their sites. Monitoring and alerting capabilities remain fully operational and are not impacted. Next Steps: Restoration efforts are ongoing. Updates will follow as more information becomes available. We appreciate your patience as we work to restore full functionality.

2. 2026년 3월 9일 오후 1:13 UTCidentified

   Our team has identified a suspected cause of the interruption of user authorization to sites and is taking steps to remediate the issue. Impact: A significant number of customers are receiving errors when they log into Auvik The following services are not affected: Monitoring, alerting, or PSA integrations Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are implementing mitigation measures and will provide progress updates as they become available.

3. 2026년 3월 9일 오후 3:04 UTCidentified

   Our team has identified a suspected cause of the interruption of user authorization to sites and is taking steps to remediate the issue. Impact: A significant number of customers are encountering errors when they log in to Auvik. Access for these users is currently being restored. The following services are not affected: Monitoring, alerting, or PSA integrations Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are implementing mitigation measures and will provide progress updates as they become available.

4. 2026년 3월 9일 오후 5:27 UTCidentified

   Our team has identified a suspected cause of the interruption of user authorization to sites and is taking steps to remediate the issue. Impact: A significant number of customers are encountering errors when they log in to Auvik. Access for users on the US1, US3, and US5 clusters has been restored. We are working our way through the remaining clusters The following services are not affected: Monitoring, alerting, or PSA integrations Please report any related issues to Auvik Support so we can track and assist further.

5. 2026년 3월 9일 오후 7:03 UTCidentified

   Our team has identified a suspected cause of the interruption of user authorization to sites and is taking steps to remediate the issue. Impact: A significant number of customers are encountering errors when they log in to Auvik. Access for users on the US1, US2, US3, US5, AU1, CA1, EU1, EU2 clusters has been restored. We are working our way through the remaining clusters US4 and US6 The following services are not affected: Monitoring, alerting, or PSA integrations Please report any related issues to Auvik Support so we can track and assist further.

6. 2026년 3월 9일 오후 7:43 UTCidentified

   Our team has identified a suspected cause of the interruption of user authorization to sites and is taking steps to remediate the issue. Impact: A significant number of customers are encountering errors when they log in to Auvik. Access for users on the US1, US2, US3, US4, US5, AU1, CA1, EU1, EU2 clusters has been restored. We are working our way through the remaining cluster, US6. The following services are not affected: Monitoring, alerting, or PSA integrations Please report any related issues to Auvik Support so we can track and assist further.

7. 2026년 3월 9일 오후 9:26 UTCresolved

   The incident has been fully resolved, and all services are operating normally. Customers should no longer experience any login issues. If you continue to experience problems, please don't hesitate to contact Auvik Support. We will provide a Root Cause Analysis (RCA) once it is available.

8. 2026년 3월 17일 오후 2:49 UTCpostmortem

   # Service Degraded - Some Customers Experiencing Login Issues After Maintenance ## Root Cause Analysis ### Duration of the incident Discovered: Mar 7, 2026 18:42 - UTC Resolved: Mar 9, 2026 21:10 - UTC ### Cause Following a platform upgrade, an internal reconciliation process incorrectly identified a subset of user records as deleted. This occurred due to an error condition in a synchronization component that failed to process all expected user data during reconciliation. ### Effect Affected users were able to log in to the platform but were unable to access their expected sites or tenants due to missing user authorizations. In some cases, API access using previously generated API keys was also affected. Monitoring, alerting, and data collection services continued to function normally throughout the incident. ### Action taken Engineering paused the process that spreads the changes across the platform to prevent further impact. User access was then restored using backup data taken prior to the upgrade. This allowed the team to recover user access, permissions, and related access keys. After restoration was completed and access was verified across all environments, the incident was declared resolved. ### Future consideration\(s\) * Implement additional monitoring to detect unexpected changes in user or authorization records. * Add safeguards within reconciliation processes to prevent large-scale unintended deletions. * Improve post-upgrade validation checks to identify abnormal record changes earlier. * Enhance disaster recovery tooling and backup retrieval processes to speed up restoration efforts.

1. 2025년 12월 15일 오후 11:28 UTCinvestigating

   Affected Services: Access Cluster(s): EU2 We are currently performing emergency maintenance, which requires a restart of the EU2 cluster. Impact: During this time, users in the EU2 region may experience login issues or intermittent service disruptions. Next Steps: We will provide updates as we learn more. We appreciate your patience as we work to resolve this issue.

2. 2025년 12월 16일 오전 1:40 UTCmonitoring

   A restart of the EU2 cluster has resolved the issue. We will monitor the situation to ensure stability and confirm that the service remains fully functional. Impact: Services should be operating normally; however, we continue monitoring for irregularities. If you are still experiencing issues, please do not hesitate to reach out to the support team and update your ticket or report any problems you haven't reported yet. Next Steps: We will provide a final update once the issue is resolved. We appreciate your patience as we work through this issue.

3. 2025년 12월 16일 오전 1:57 UTCresolved

   The incident has been fully resolved. Regular service has been restored, and all systems operate as expected. Impact: Users should no longer experience any issues related to this service disruption. If you are still experiencing issues, please do not hesitate to reach out to the support team and update your ticket or report any problems you haven't reported yet. Service has been fully restored. We apologize for any disruption to our services. We thank you for your understanding. If you continue to experience issues, please don't hesitate to contact our support team. We will post an RCA after an internal investigation.

4. 2025년 12월 22일 오전 8:49 UTCpostmortem

   # Service Disruption - The EU2 cluster was unavailable ## Root Cause Analysis ### Duration of the incident Discovered: Dec 15, 2025 20:00 – UTC Resolved: Dec 16, 2025 02:00 – UTC ### Customer impact During the incident window, customers hosted in the EU2 region experienced intermittent service degradation. This included slower system responsiveness, temporary inconsistencies in monitoring data, and brief periods where alerts may have been delayed or inaccurate. Most customers regained access as services were progressively restored, and complete stability was confirmed before the incident was closed. ### Cause The incident was caused by an elevated load in the EU2 service environment, resulting in an uneven workload distribution across backend resources. As the load increased, automated recovery mechanisms were unable to stabilize the environment fully, necessitating a controlled restart of the regional service to restore normal operations. ### Effect The imbalance led to reduced service performance and temporary unavailability for some customers until recovery actions were completed. Engineering teams were required to intervene to safely restart the affected region and validate service health before returning operations to normal. ### Future consideation\(s\) * Improve automated workload balancing to absorb regional load increases. * Strengthen early indicators for backend saturation to enable earlier intervention. * Refine operational procedures to further reduce recovery time in similar scenarios.

1. 2025년 12월 15일 오후 2:35 UTCinvestigating

   We are currently investigating reports of Meraki switch stacks creating duplicates. Impact: Customers may see duplicate inventory in the Meraki stacks. The following services are not affected: Alerting and all other Device inventory. Next Steps: Our team is working to identify contributing factors. Updates will follow as more information becomes available.

2. 2025년 12월 15일 오후 3:02 UTCinvestigating

   We are currently investigating reports of Meraki switch stacks creating duplicates. Impact: Customers may see duplicate inventory in the Meraki stacks. No new devices are currently being created. Devices that have been duplicated cannot yet be deleted. The following services are not affected: Alerting and all other Device inventory. Next Steps: Our team is working to identify contributing factors. Updates will follow as more information becomes available.

3. 2025년 12월 15일 오후 4:52 UTCidentified

   Our team has identified a suspected cause of the Meraki duplicate Stack switches and is taking steps to remediate the issue. Impact: Customers may continue to experience duplicated Meraki Stack switches The following services are not affected: Alerting and all other Device inventory. Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are applying mitigation measures and will provide updates on progress.

4. 2025년 12월 15일 오후 5:35 UTCmonitoring

   We have applied changes to address the issue. You'll now see the duplicate begin to be removed. Impact: Services should be operating normally; however, if you continue to encounter problems, please report them to Auvik Support. Next Steps: A final update will be posted once we confirm the resolution.

5. 2025년 12월 15일 오후 6:23 UTCresolved

   The incident has been fully resolved, and all services are operating normally. Customers should no longer experience any related issues. If you continue to experience problems, please don't hesitate to contact Auvik Support. We will provide a Root Cause Analysis (RCA) once it is available.

6. 2025년 12월 19일 오후 4:24 UTCpostmortem

   # Service Degraded - Duplicated Devices for Meraki Switch Stacks ## Root Cause Analysis ### Duration of the incident Discovered: Dec 15, 2025 08:34 – UTC Resolved: Dec 15, 2025 13:20 – UTC ### Customer impact Customers with Meraki switch stacks across all clusters experienced: Duplicate Meraki switches are appearing in the device inventory, including entries without management IP addresses. Inability to manually delete duplicates, as they were automatically recreated. Confusing or inaccurate device and stack representations. Temporary inflation of billable device counts for some tenants \(billing data captured and under review\). No other device types were affected. ### Cause A configuration update intended to improve how Meraki switch stacks are represented in the platform caused unintended behavior. For tenants already using Meraki stacking, the system was unable to match newly processed stack data to existing switches consistently. This caused already-stacked switches to be incorrectly interpreted as new devices, generating duplicate inventory entries. Because the underlying synchronization logic reinforced these entries, any customer deletion of duplicates did not persist, and duplicates reappeared. ### Effect The issue led to inaccurate device inventories and misleading switch-stack views for customers using Meraki stacking, causing confusion in device management and increasing support tickets. Internal teams experienced additional operational overhead as they investigated the duplication patterns and validated safe removal procedures. Complete remediation required coordinated cleanup across all clusters to restore accurate device records and ensure no further duplicates were generated. ### Future consideration\(s\) * Strengthen validation of device and stack metadata before inventory updates. * Improve testing coverage using a production-like stacked device configuration. * Add monitoring and alerting for abnormal changes in device counts. * Use safer rollout controls and feature flags for changes affecting device inventory logic.

1. 2025년 12월 11일 오후 2:30 UTCinvestigating

   We are currently investigating reports of duplicate devices being created, which could cause alert flooding. Impact: Customers may experience a high false alert definitions The following services are not affected by all other clusters and monitoring. Next Steps: Our team is working to identify contributing factors. Updates will follow as more information becomes available.

2. 2025년 12월 11일 오후 2:43 UTCidentified

   Our team has identified a suspected cause of the Fortinet firewall duplication and is taking steps to remediate the issue. Impact: Customers may continue to receive some excessive resolved alerts while duplicates are cleared from the system. The following services are not affected: Any other devices or clusters. Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are implementing mitigation measures and will provide progress updates.

3. 2025년 12월 11일 오후 3:48 UTCidentified

   Our team has begun deleting duplicate Fortinet firewalls. Impact: Customers may continue to receive excessive resolved alerts while duplicates are cleared from the system. The following services are not affected: Any other devices or clusters. Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are implementing mitigation measures and will provide progress updates.

4. 2025년 12월 11일 오후 5:01 UTCmonitoring

   We have applied changes to address the issue. Services are beginning to revert to normal, and we are monitoring closely for stability. Impact: Extraneous Fortinet firewalls will continue to be flushed from affected tenants; however, if you continue to encounter problems, please report them to Auvik Support. Next Steps: A final update will be posted once we confirm the resolution.

5. 2025년 12월 11일 오후 8:00 UTCidentified

   Our team continues to investigate the suspected cause of the duplicate Fortinet firewalls and is taking steps to remediate the issue. Impact: Customers may continue to experience alerts from duplicate Fortinet firewalls. The following services are not affected: All other clusters and vendors. Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are applying new mitigation measures and will provide updates on progress.

6. 2025년 12월 11일 오후 8:37 UTCidentified

   Our team continues to investigate the suspected cause of the duplicate Fortinet firewalls and is taking steps to remediate the issue. Auvik will place the EU2 cluster in maintenance mode to continue working on the issue and prevent further false alerts. Impact: All alerting for the EU2 cluster has been placed in maintenance mode. The following services are not affected: All other clusters. Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are applying new mitigation measures and will provide updates on progress.

7. 2025년 12월 11일 오후 9:54 UTCidentified

   Our team has begun isolating the devices requiring correction. Auvik has placed the EU2 cluster in maintenance mode to continue working on the issue and prevent further false alerts. Impact: All alerting for the EU2 cluster has been placed in maintenance mode. The following services are not affected: All other clusters. Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are applying new mitigation measures and will provide updates on progress.

8. 2025년 12월 11일 오후 10:48 UTCidentified

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

9. 2025년 12월 11일 오후 11:46 UTCresolved

   The incident has been fully resolved, and all services are operating normally. Customers should no longer experience any related issues. If you continue to experience problems, please don't hesitate to contact Auvik Support. We will provide a Root Cause Analysis (RCA) once it is available.

10. 2025년 12월 19일 오후 4:15 UTCpostmortem

    # Service Degraded - FortiGate firewalls duplicated in the EU2 cluster, causing a flood of alerts. ## Root Cause Analysis ### Duration of the incident Discovered: Dec 11, 2025 14:00 – UTC Resolved: Dec 17, 2025 06:45 – UTC ### Customer impact Clients with FortiGate firewalls in the EU2 region experienced: * A significant increase in “device offline” alerts due to status flapping between duplicate and original device entries. * Duplicate firewalls appear in inventory views, leading to confusion in device management. * Inaccurate device statistics and monitoring gaps. * In some cases, customers attempted to delete duplicates, which resulted in the loss of historical data on the original device. No other device types or regions were affected. ### Cause A system change intended to improve how high-availability firewall configurations were processed introduced unexpected behavior. Under certain conditions, the platform was unable to detect when multiple records referenced the same firewall device consistently. As a result, some firewalls were incorrectly detected as new devices, causing duplicate entries and inconsistent operational status reporting. ### Effect The issue resulted in elevated alert volumes across impacted tenants and caused instability in device-status reporting for the affected firewalls. Customers experienced increased operational overhead as they reviewed unexpected alerts and duplicate device entries, and engineering teams were required to intervene to restore accurate device associations and remove the duplicated records.fFuture consideration\(s\) * Strengthen validation of device-supplied information before it affects inventory or monitoring. * Implement alerting for sudden spikes in offline/online transitions to detect similar issues earlier. * Improve observability of device lifecycle behavior to identify anomalies proactively. * Use feature-flagged or staged rollouts for changes that affect device processing logic. * Incorporate production-like data into pre-deployment testing to better anticipate unexpected device behaviors.

1. 2025년 12월 5일 오후 12:50 UTCinvestigating

   We are currently investigating reports of the Auvik chatbot not transferring the session to a live agent. Impact: Customers will not be able to reach a live agent until the service is restored. The following services are not affected: The Knowledge Base, Support Portal, and Auvik site. Please submit a web form ticket from the Support site in the meantime, if needed to contact support. Next Steps: Our team is working to identify contributing factors. Updates will follow as more information becomes available.

2. 2025년 12월 5일 오후 1:17 UTCidentified

   Our team has identified a suspected cause of the Auvik chatbot not transferring the session to a live agent. Impact: Customers will not be able to reach a live agent until the service is restored. The following services are not affected: The Knowledge Base, Support Portal, and Auvik site. Please submit a web form ticket from the Support site in the meantime, if needed to contact support. Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are applying mitigation measures and will provide updates on progress.

3. 2025년 12월 5일 오후 1:32 UTCresolved

   The incident has been fully resolved, and all services are operating normally. Customers should no longer experience any related issues. If you continue to experience problems, please don't hesitate to contact Auvik Support. We appreciate your understanding and patience.

1. 2025년 12월 3일 오후 2:21 UTCidentified

   Affected Services: Login We’re aware that an issue with Okta caused login failures for many users accessing Auvik. Okta has reported that the problem is resolved, but some users may still experience difficulties signing in. You can follow their updates here: https://status.okta.com/#incident/a9CWR00000012Cg2AI Recent status information is also available at: https://status.okta.com/#recent Impact: While we work on the resolution, users may continue to experience login issues Next Steps: Our team is actively working to resolve the issue and will provide updates as progress is made. Your patience is greatly appreciated, and we regret any inconvenience you may have experienced.

2. 2025년 12월 3일 오후 3:54 UTCmonitoring

   Latest update from Okta December 3, 2025 at 7:50am PST Our service is seeing recovery following successful mitigation efforts with our provider. We continue to closely monitor system stability. Our next update will be in 30 minutes, or sooner if new information is available. We are watching our systems for recovery and performance.

3. 2025년 12월 3일 오후 5:28 UTCresolved

   Latest update from Okta Incident Resolved December 3, 2025 at 8:58am PST An issue impacting the core authentication service for customers in Okta Cell US7 has been resolved. Additional root cause information will be available within five business days. We will close the status page for Auvik's sites.

1. 2025년 11월 21일 오후 6:29 UTCidentified

   Affected Services: Hierarchy and permissions Cluster(s): All Our team has identified the root cause of the service disruption and is currently investigating a solution to restore normal service levels. Impact: While we work on the resolution, users may continue to experience reduced functionality in the product. Next Steps: Our team is actively working to resolve the issue and will provide updates as progress is made. Your patience is greatly appreciated, and we regret any inconvenience you may have experienced.

2. 2025년 11월 21일 오후 6:38 UTCidentified

   We are aware of an issue where customers can log in successfully but may be unable to view certain data, including maps, inventory, site lists, and a few other areas. Our team has identified the root cause and compiled a fix. The estimated time to full recovery is approximately 30–60 minutes. Thank you for your patience.

3. 2025년 11월 21일 오후 7:26 UTCresolved

   The incident has been fully resolved. Regular service has been restored, and all systems operate as expected. Impact: Users should no longer experience any issues related to this service disruption. If you are still experiencing issues, please do not hesitate to reach out to the support team and update your ticket or report any problems you haven't reported yet. Service has been fully restored. We apologize for any disruption to our services. We thank you for your understanding. If you continue to experience issues, please don't hesitate to contact our support team. We will post an RCA after an internal investigation.

4. 2025년 12월 4일 오후 4:35 UTCpostmortem

   # Service Degraded - Data Not Loading Across All Clusters ## Root Cause Analysis ### Duration of the incident Discovered: Nov 21, 2025 17:43 – UTC Resolved: Nov 21, 2025 19:18 – UTC ### Customer impact Customers across all regions were able to log in, but many were unable to view key data within the platform. This included features such as: * Network maps * Inventory and site lists * Dashboards * Other views are dependent on permissions and hierarchical data. This resulted in degraded usability and limited visibility into managed environments. ### Cause During a routine maintenance task intended to clean up older data records, an incorrect piece of information was unintentionally added to the system. This faulty data prevented a core component—responsible for organizing how customer information is displayed in the platform—from functioning correctly. Because this component could not run as expected, many areas of the product that rely on structured data \(such as maps, dashboards, and inventory views\) were unable to load. This led to widespread service degradation across all clusters. ### Effect Because the system could not correctly load the information needed to display customer environments, several parts of the platform were unable to show data. As a result, many users could log in but were unable to see maps, inventory details, site lists, dashboards, or other information they usually rely on. This created a degraded experience across all regions, limiting visibility and making it difficult for customers to perform routine monitoring and management tasks until the issue was resolved. ### Future consideation\(s\) * Introduce stronger validation and safeguards to prevent malformed data from being accepted into critical systems. * Improve the resilience of backend services so they fail gracefully rather than entering repeated restart cycles. * Implement additional monitoring to provide earlier detection of issues affecting data-loading functions. * Enhance internal tools used during maintenance and cleanup activities to reduce the risk of unintentional data corruption.

1. 2025년 10월 20일 오전 9:51 UTCidentified

   Auvik is currently being impacted by today’s AWS outage. Some pages and APIs may be slow or have errors. No data loss is expected. We will update here as we receive more information

2. 2025년 10월 20일 오전 10:11 UTCmonitoring

   AWS services are recovering. Services appear to be operating normally, and we are monitoring closely for stability. Impact: Services should be operating normally; however, if you continue to encounter problems, please report them to Auvik Support. Next Steps: A final update will be posted once we confirm the resolution.

3. 2025년 10월 20일 오전 10:42 UTCmonitoring

   AWS services are recovering. Services appear to be operating normally, and we are monitoring closely for stability. Amazon is recommending flushing your DNS cache if you are still experiencing issues. Impact: Services should be operating normally; however, if you continue to encounter problems, please report them to Auvik Support. Next Steps: A final update will be posted once we confirm the resolution.

4. 2025년 10월 20일 오전 10:57 UTCresolved

   The incident has been fully resolved, and all services are operating normally. Customers should no longer experience any related issues. If you continue to experience problems, please don't hesitate to contact Auvik Support.

1. 2025년 10월 15일 오후 3:22 UTCinvestigating

   We are currently investigating reports of 500 errors affecting access to clients on the US4 cluster. Impact: Customers may experience access issues to their tenants. Alerts and monitoring are not affected The other clusters are not affected. Next Steps: Our team is working to identify contributing factors. Updates will follow as more information becomes available.

2. 2025년 10월 15일 오후 4:39 UTCinvestigating

   We are continuing to investigate HTTP 500 errors affecting access to clients on the US4 cluster. Impact: Customers will experience access issues to their tenants. Alerts and monitoring are not affected. The other clusters are not affected. Next Steps: Our team is working to identify contributing factors. Updates will follow as more information becomes available.

3. 2025년 10월 15일 오후 5:04 UTCidentified

   Our team has identified a suspected cause of the HTTP 500 site access issue and is taking steps to remediate it. Impact: Customers should now be able to access their sites without encountering an HTTP 500 error. Maps and site inventories are not rendering correctly in the UI. The following services are not affected: Monitoring and Alerting. Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are applying mitigation measures and will provide updates on progress.

4. 2025년 10월 15일 오후 5:22 UTCmonitoring

   We have applied changes to address the issues. Services appear to be operating normally, and we are monitoring closely for stability. Impact: Services should be operating normally; however, if you continue to encounter problems, please report them to Auvik Support. Next Steps: A final update will be posted once we confirm the resolution.

5. 2025년 10월 15일 오후 5:33 UTCresolved

   The incident has been fully resolved, and all services are operating normally. Customers should no longer experience any related issues. If you continue to experience problems, please don't hesitate to contact Auvik Support. We will provide a Root Cause Analysis (RCA) once it is available.

6. 2025년 10월 31일 오후 2:27 UTCpostmortem

   # Service Degraded - Sites have lost settings after maintenance ## Root Cause Analysis ### Duration of the incident Discovered: Oct 11, 2025 – 12:00 UTC Resolved: Oct 15, 2025 – 22:00 UTC ### Cause During a scheduled system update, a background maintenance process unintentionally removed reference files used to identify stored site configurations. When affected systems restarted after the update, they were unable to locate those configuration files and temporarily appeared as new, empty sites. This occurred because the maintenance process was using outdated information when determining which data to clean up safely. The underlying data remained securely stored, but the missing reference files prevented normal access until they were restored. ### Effect A subset of tenants across multiple clusters temporarily lost access to their site configurations and appeared as newly created environments. Customers observed missing data and configurations, including previously defined network settings and device details. ### Action taken _All times are in UTC_ **10/11/2025** **12:00** – A scheduled system upgrade began across all clusters. **15:25** – The support team received reports from customers that some sites appeared empty or missing data. **16:00** – Engineering immediately began investigating and determined this was not related to normal data processing delays. **10/12/2025** Additional reports confirmed that several sites were missing configuration information. The engineering team confirmed that the original data was still securely stored, but was not being correctly loaded by the system. **10/13/2025** The issue was traced to missing metadata files that help identify stored configurations. The engineering team began restoring affected sites using the most recent valid configuration data. Automated recovery tools were developed to safely restore additional sites and ensure consistent recovery across all clusters. **10/14/2025** Engineering verified that configuration data was fully restored and synchronized across supporting services. The recovery process was extended to all remaining sites, with validation steps confirming successful restoration. **10/15/2025** Final recovery efforts for the remaining affected clusters were completed.. **22:00** – All affected sites were confirmed operational with their configurations restored and verified. ### Future consideration\(s\) * Remove dependency of cleanup processes on outdated cluster data sources. * Validate all automated cleanup jobs to ensure they do not operate on production clusters. * Implement monitoring for missing or corrupted metadata files before deployments. * Enhance post-deployment validation to verify the integrity of configuration data across all clusters.

1. 2025년 9월 23일 오후 5:45 UTCinvestigating

   We are currently investigating reports of a clients not being able to access their tenants on the CA1 cluster. Impact: Customers may experience an interruption of access to their sites. The following services are not affected: Other clusters are not affected by this Next Steps: Our team is working to identify contributing factors. Updates will follow as more information becomes available.

2. 2025년 9월 23일 오후 7:16 UTCinvestigating

   We are continuing to investigate tenants on the CA1 cluster that are not accessible. Impact: Customers are experiencing an interruption of access to their sites. The following services are not affected: Other clusters are not affected by this outage. Next Steps: Our team is working to identify contributing factors. Updates will follow as more information becomes available.

3. 2025년 9월 23일 오후 8:30 UTCidentified

   Our team has identified a suspected cause of the sites on the CA1 cluster being inaccessible and is taking steps to remediate the issue. There have also been reports of some users experiencing issues accessing Auvik using their Okta setup. This is also being investigated. Impact: Customers may continue to experience their site being inaccessible on the CA1 cluster. Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are applying mitigation measures and will provide updates on progress.

4. 2025년 9월 23일 오후 8:58 UTCidentified

   Our team has identified a suspected cause of the sites on the CA1 cluster being inaccessible and is taking steps to remediate the issue. There have also been reports of some users experiencing issues accessing Auvik using their Okta setup. This is also being investigated. Additionally, any new tenants or users created since 17:15 UTC (1:15 PM ET) are currently not functioning or accessible. Impact: Customers may continue to experience inaccessibility to their site on the CA1 cluster as the cluster comes back up. Clients or clusters created since the incident began are not accessible. Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are applying mitigation measures and will provide updates on progress.

5. 2025년 9월 23일 오후 10:16 UTCidentified

   Our team has identified a suspected cause of the sites on the CA1 cluster being inaccessible and is taking steps to remediate the issue. Sites have been restored to yesterday. We are working to restore data that was present at the time of this incident. There have also been reports of some users experiencing issues accessing Auvik using their Okta setup. We are working to restore access. Additionally, any new tenants or users created since 17:15 UTC (1:15 PM ET) are currently not functioning or accessible. Tenant restoration is occurring. Impact: Customers should now be able to access their sites on the CA1 cluster, with the exceptions noted above. Data restoration is being worked on. Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are applying mitigation measures and will provide updates on progress.

6. 2025년 9월 24일 오전 12:06 UTCmonitoring

   We have implemented changes to address the issue with services for clients on the CA1 clusters, and these clusters are now operating normally. We are monitoring closely for stability. Impact: Services should be operating normally for the tenants in the CA1 cluster. Tenants created have also been restored. There are still issues with some clients who use Okta to access Auvik. We are looking to remediate these. If you continue to encounter problems, please report them to Auvik Support. Next Steps: We will be monitoring the situation during the evening and will report updates in the morning. A final update will be posted once we confirm the resolution.

7. 2025년 9월 24일 오후 12:58 UTCinvestigating

   We are currently investigating reports of not being able to access new sites after they are created. This is under all clusters. Impact: All other services should be operating normally for the tenants in the CA1 cluster. We are continuing to experience issues with a small percentage of Okta-enabled accounts that lack access. We are looking to remediate these. If you continue to encounter problems, please report them to Auvik Support. Next Steps: We will be monitoring the situation during the evening and will report updates in the morning. A final update will be posted once we confirm the resolution.

8. 2025년 9월 24일 오후 2:11 UTCmonitoring

   We have applied changes to address the issue with new site creation. We continue to experience issues with some cases of child site creations and are working to rectify them. Other services appear to be operating normally, and sites are becoming visible in the UI. We are monitoring closely for stability. Impact: All other services should be operating normally for the tenants in the CA1 cluster. We are continuing to experience issues with a small percentage of Okta-enabled accounts that lack access. We are remediating these. If you continue to encounter problems, please report them to Auvik Support. Next Steps: A final update will be posted once we confirm the resolution.

9. 2025년 9월 24일 오후 4:27 UTCmonitoring

   We have applied changes to address the issue with new site creation. We continue to experience issues with sites not being visible promptly. We are continuing to work on this issue. This is also contributing to a site redirection issue where sites are not accessible via xxx.my.auvik.com, but are accessible via xxx.us1.my.auvik.com, where us1 is the cluster on which the site is located. Other services appear to be operating normally, and sites are becoming visible in the UI. We are monitoring closely for stability. Impact: We are continuing to experience issues with a small percentage of Okta-enabled accounts that lack access. We are remediating these accounts. If you continue to encounter problems, please report them to Auvik Support. Next Steps: A final update will be posted once we confirm the resolution.

10. 2025년 9월 24일 오후 7:48 UTCmonitoring

    We are currently experiencing some system slowness on clusters outside of CA1. This is related to residual cleanup from earlier issues on the CA1 cluster. Our team is actively addressing this to ensure ongoing platform stability. Additionally, the cleanup contributed to a site redirection issue, where sites may not be accessible via xxx.my.auvik.com. These sites are accessible when using the fully qualified URL (e.g., xxx.us1.my.auvik.com), where us1 reflects the cluster hosting the site. In some cases, newly created sites may not display correctly. A small percentage of clients using Okta authentication were also impacted. If you encounter a denied login message, you may need to reset your password by following the provided instructions. Impact Some clients may see slower performance. Site access via xxx.my.auvik.com may fail; use the direct cluster URL (xxx.[cluster].my.auvik.com) as a workaround. Limited Okta users may experience authentication issues requiring a password reset. Next Steps Our engineering team is continuing remediation efforts. A final update will be provided once the issues are fully resolved. If you continue to encounter problems, don't hesitate to get in touch with Auvik Support .

11. 2025년 9월 24일 오후 11:41 UTCmonitoring

    We continue to experience system slowness on clusters outside of CA1, which is attributed to residual cleanup efforts related to earlier issues in the CA1 cluster. Although our team has made progress, some symptoms persist, and we continue to work on resolving them. Impact: Performance: Some clients may still see slower performance. Site Access: Accessing sites via xxx.my.auvik.com may fail. Sites remain accessible using the fully qualified URL format (xxx.[cluster].my.auvik.com). Login Issues: Some sites are still experiencing login issues. Okta Authentication: A small subset of clients using Okta may continue to see denied login attempts. A password reset may be required. Next Steps We are focused on restoring full login functionality and addressing the residual impacts of the cleanup. A final update will be provided once all issues are fully resolved. If you continue to experience problems, please contact Auvik Support.

12. 2025년 9월 25일 오전 2:45 UTCmonitoring

    We are continuing to monitor for any further issues.

13. 2025년 9월 25일 오전 3:13 UTCidentified

    Our team has identified a suspected cause of the slowness on the EU1 cluster and is taking steps to remediate the issue by performing an out-of-band maintenance on the EU1 cluster. Impact: Customers may experience issues accessing their sites on the EU1 cluster over the next two hours while this maintenance is in progress. Sites on the other clusters are not affected by the action. Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are applying mitigation measures and will provide updates on progress.

14. 2025년 9월 25일 오전 5:25 UTCmonitoring

    Our team has successfully completed the out-of-band maintenance on the EU1 cluster. We will continue to monitor EU1 closely throughout the evening to ensure stability. The earlier slowness affecting clusters outside of CA1 now appears to be resolved. We will continue to validate system performance and client connections across all clusters. Impact: EU1: Sites remain stable following maintenance; we are monitoring for any recurrence. Other Clusters: No ongoing slowness observed. Login / Okta: A small subset of clients using Okta may still experience denied login attempts; a password reset may be required. Next Steps: Continue overnight monitoring of EU1 and client connection stability. Perform additional validation tomorrow on site performance and login flows. If you encounter related issues, please contact Auvik Support so we can track and assist further. Next Steps: A final update will be posted once we confirm the resolution.

15. 2025년 9월 25일 오후 1:18 UTCmonitoring

    Services appear to be operating normally, and we are continuing to monitor closely for stability. We are still receiving periodic reports of site slowness. This seems especially pertinent with the new discovery scans. We are currently investigating. A small percentage of clients using Okta authentication were impacted. If you encounter a denied login message, you may need to reset your password by following the vendor's instructions. You will also need to re-enable your MFA. Impact: Services should be operating normally; however, if you continue to encounter problems, please report them to Auvik Support. Next Steps: A final update will be posted once we confirm the resolution.

16. 2025년 9월 25일 오후 1:42 UTCinvestigating

    We are currently investigating reports of 500 errors that occur periodically when accessing pages on sites. We are still receiving periodic reports of site slowness. This seems especially pertinent with the new discovery scans. We are currently investigating. A small percentage of clients using Okta authentication were impacted. If you encounter a denied login message, you may need to reset your password by following the vendor's instructions. You will also need to re-enable your MFA. Impact: Customers may experience intermittent issues with their sites Next Steps: Our team is working to identify contributing factors. Updates will follow as more information becomes available.

17. 2025년 9월 25일 오후 4:05 UTCinvestigating

    We are continuing to investigate this issue.

18. 2025년 9월 25일 오후 4:57 UTCmonitoring

    We identified and addressed the root causes behind intermittent 500 errors, map loading issues for new tenants, and isolated EU1 access failures. Fixes have been implemented, including updates to API rate-limit handling, permissions validation, and service restarts. Impacted services are recovering as expected. We are closely monitoring system stability and completing a sweep of collectors across clusters to confirm full health. No further impact is expected at this time. Next Steps: A final update will be posted once we confirm the resolution.

19. 2025년 9월 25일 오후 11:46 UTCmonitoring

    We’ve resolved the issues that caused errors, map loading problems for new tenants, and access interruptions in EU1. Services are recovering and performing as usual. We will be monitoring the platform closely throughout the evening, focusing on overall stability and conducting a comprehensive sweep of collectors across clusters to confirm their health. No further customer impact is expected at this time. If you continue to encounter problems, please don't hesitate to contact Auvik Support. Next Steps: A final update will be posted once the resolution is confirmed.

20. 2025년 9월 26일 오후 1:58 UTCresolved

    The incident has been fully resolved, and all services are operating normally. Customers should no longer experience any related issues. If you continue to experience problems, please don't hesitate to contact Auvik Support. We will provide a Root Cause Analysis (RCA) once it is available.

21. 2025년 10월 15일 오후 5:49 UTCpostmortem

    # Service Disruption - Platform Availability and Login Access ## Root Cause Analysis ### Duration of the incident Discovered: Sep 23, 2025 – 17:45- UTC Resolved: Sep 26, 2025 – 13:58 - UTC ### Customer impact Tenants on the CA1 cluster lost their settings, and Auvik was inaccessible for a time. Intermittent platform errors and degraded performance for some customers. A temporary issue prevented certain users from logging in via Okta. Delays in data synchronization in the EU1 region necessitate restarting the cluster. ### Cause A configuration update intended for specific tenants was applied globally due to a missing query constraint. This caused the deletion of tenant and user records in one cluster, leading to cascading synchronization and workload impacts across other clusters. As a result, user data was propagated as deletions to the identity provider, temporarily removing affected user accounts. ### Effect The CA1 cluster required restoration from a backup, resulting in the temporary unavailability of some tenant data. 43 tenants and 22 user accounts required manual recreation and verification. Authentication failures occurred for affected users due to the removal of identity records. The EU1 cluster experienced performance degradation as it processed a large data synchronization backlog. Increased load briefly impacted the responsiveness of other clusters’ regional services. ### Future consideration\(s\) * Implement a dry-run and confirmation step in internal tooling to validate production commands before execution. * Reinforce the change-management process for improved peer visibility and validation. * Expand resource and capacity monitoring to identify anomalies earlier and respond proactively. * Revisit release control lifecycle practices to remove obsolete configurations after rollout completion.

1. 2025년 9월 17일 오후 1:53 UTCinvestigating

   We are currently investigating reports of login issues affecting access to Auvik for its users. Impact: Customers may be unable to access their tenants. Next Steps: Our team is working to identify contributing factors. Updates will follow as more information becomes available.

2. 2025년 9월 17일 오후 2:09 UTCinvestigating

   We are currently investigating reports of login issues affecting access to Auvik for its users. Impact: Customers may experience the inability to access their sites when using redirects to their site URL. The following services are not affected: Monitoring and Alerting. Next Steps: Our team is working to identify contributing factors. Updates will follow as more information becomes available.

3. 2025년 9월 17일 오후 2:15 UTCidentified

   Our team has identified a suspected cause of the login access and is taking steps to remediate the issue. Impact: Customers may continue to experience login issues if using URL redirects to access their site(s). The following services are not affected: Monitoring and Alerting. Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are applying mitigation measures and will provide updates on progress.

4. 2025년 9월 17일 오후 4:20 UTCidentified

   Our team has identified a suspected cause of the login access and is taking steps to remediate the issue. Impact: Customers may continue to experience login issues if using URL redirects to access their site(s). The following services are not affected: Monitoring and Alerting. Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We continue applying mitigation measures and will provide updates on progress.

5. 2025년 9월 17일 오후 4:35 UTCmonitoring

   We have applied changes to address the issue. Services appear to be operating normally, and we are monitoring closely for stability. Impact: Services should be operating normally; however, if you continue to encounter problems, please report them to Auvik Support. Next Steps: A final update will be posted once we confirm the resolution.

6. 2025년 9월 18일 오후 1:55 UTCmonitoring

   The changes were applied to address the issue.. Services appear to be operating normally, and we are continuing to monitor closely for stability. Impact: Services should be operating normally; however, if you continue to encounter problems, please report them to Auvik Support. Next Steps: A final update will be posted once we confirm the resolution.

7. 2025년 9월 18일 오후 7:02 UTCmonitoring

   Monitoring The changes were applied to address the issue.. Services appear to be operating normally, and we are continuing to monitor closely for stability. Impact: We recently experienced a short disruption with URL redirects. This has been resolved, and services are working as expected. Services should be operating normally; however, if you continue to encounter problems, please report them to Auvik Support. Next Steps: A final update will be posted once we confirm the resolution.

8. 2025년 9월 18일 오후 9:00 UTCresolved

   The incident has been fully resolved. Regular service has been restored, and all systems operate as expected. Impact: Users should no longer experience any issues related to this service disruption. If you are still experiencing issues, please do not hesitate to reach out to the support team and update your ticket or report any problems you haven't reported yet. Service has been fully restored. We apologize for any disruption to our services. We thank you for your understanding. If you continue to experience issues, please don't hesitate to contact our support team. We will post an RCA after an internal investigation.

9. 2025년 9월 29일 오후 1:49 UTCpostmortem

   # Service Degraded - Clients experienced login issues to their site because the URL redirect was not working. ## Root Cause Analysis A recent update led to more traffic than expected, resulting in simultaneous overload of the same systems. This overloaded them, leading to delays and occasional failures when customers tried to log in. Some customers also experienced issues when trying to start new trials. ### Duration of the incident Discovered: Sep 17, 2025 13:50 - UTC Resolved: Sep 18, 2025 21:00 - UTC ### Cause The update unintentionally created extra demand on shared systems. As a result, the login process and new trial creation sometimes failed or responded slowly. ### Effect * Some customers could not log in after entering their password or completing MFA. * Occasional slow responses and error messages \(404/500/502/504\). * New trial sign-ups sometimes failed or were delayed. * Internal tools that rely on the same login process also saw intermittent issues. ### Action taken * Adjusted system settings to reduce pressure on overloaded services. * Closely monitored traffic while making changes to keep the service stable. * Applied a temporary workaround to allow new trials to be created reliably. * Released a fix to stabilize the login redirect process. * Made further tuning changes to spread out demand and reduce load. * Continued monitoring until the login and sign-up flows were confirmed to be stable. ### Future consideration\(s\) * Reduce reliance on a single system for login and trial flows by distributing the workload across multiple systems.. * Enhance monitoring to identify login errors and trial creation issues more promptly. * Add safeguards to prevent overload, including traffic limits and fallback options. * Test updates under heavier load conditions to catch these issues earlier.

1. 2025년 9월 10일 오후 4:43 UTCinvestigating

   We are currently investigating reports of sites receiving 500 errors affecting site access. Impact: Customers may experience an inability to connect to their site(s)or have collectors connect. Next Steps: Our team is working to identify contributing factors. Updates will follow as more information becomes available.

2. 2025년 9월 10일 오후 5:00 UTCidentified

   Our team has identified a suspected cause of the connection issues and is taking steps to remediate the issue. Impact: Customers who experienced the 500 errors are now remedied. Connection issues after installing a Windows collector are still being investigated. Users may continue to experience the collector not connecting to the site. The following services are not affected: monitoring and alerting. Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are applying mitigation measures and will provide updates on progress.

3. 2025년 9월 10일 오후 5:07 UTCmonitoring

   We have applied changes to address the issue. Services appear to be operating normally, and we are monitoring closely for stability. Impact: Collector connection services should be operating normally; however, if you continue to encounter problems, please report them to Auvik Support. Next Steps: A final update will be posted once we confirm the resolution.

4. 2025년 9월 10일 오후 5:26 UTCresolved

   The connectivity issues with the site and collectors have been fully resolved, and services are operating as expected. Impact: Customers should no longer experience any related issues. If you continue to experience issues, please report them to Auvik Support.

5. 2025년 9월 25일 오전 12:13 UTCpostmortem

   # Service Degraded - Login and Collector Installation Issues on US3 Cluster ## Root Cause Analysis ### Duration of the incident Discovered: Sep 10, 2025 13:17 UTC Resolved: Sep 12, 2025 15:08 UTC ### Cause Two separate but overlapping issues contributed to this incident: * Collector Installation Failures – Windows collectors were unable to install due to missing service principal credentials on the backend agent server, which prevented successful API calls for subscription data. * Login and Redirect Failures – Following a restart of the US3 frontend, requests for user and tenant data from secondary clusters intermittently failed. This caused login attempts through Okta to hang and product redirects to fail. ### Effect * Users attempting to log in via Okta were unable to complete authentication and access tenants. * Some sites experienced 500 errors when attempting to access dashboards. * Windows collector installations via GUI and CLI failed, preventing the deployment of new collectors. ### Action taken _All times are in UTC_ **09/10/2025** **13:17** – Users report inability to log in to Auvik Production through Okta. **13:28** – Errors in US3 frontend logs identified relating to user/tenant data queries. **13:37** – Engineering suspends frontend deployment in the US3 cluster. **13:39** – Issues confirmed across secondary clusters; logs analyzed for root cause. **14:54** – Identified that the frontend redirect service could not fetch required tenant data; feature flag disabled to restore functionality. **15:01** – Engineering confirms that the workaround restores login functionality while monitoring tenant recovery. The incident is resolved on the status page. **09/12/2025** **15:08** – Feature flag re-enabled after system recovery; frontend services reconciled successfully. Incident fully resolved. ### Future consideration\(s\) * Improve validation of service principal credentials to prevent collector installation failures. * Enhance monitoring and alerting around login and redirect workflows to detect tenant query failures earlier. * Review and refine feature flag rollout procedures to minimize dependency risks and ensure optimal deployment. * Continue improving how customer data is distributed across clusters so that queries run more efficiently and reliably, even during high system load or maintenance events.

1. 2025년 8월 27일 오후 9:30 UTCinvestigating

   We are currently investigating reports of an outage affecting clients on US4. Impact: Customers may experience an inability to log in to their site The following services are not affected: Other clusters, including alerting and monitoring. Next Steps: Our team is working to identify contributing factors. Updates will follow as more information becomes available.

2. 2025년 8월 27일 오후 9:38 UTCidentified

   Our team has identified a suspected cause of the outage on the US4 cluster and is taking steps to remediate the issue. Impact: Customers will not have access to the sites on the US4 cluster for the next two hours while we bring them online. Some sites on the US4 may become operational before that time. The following services are not affected: Sites on other clusters.. Please report any related issues to Auvik Support so we can track and assist further. Next Steps: We are applying mitigation measures and will provide updates on progress.

3. 2025년 8월 27일 오후 10:38 UTCmonitoring

   We have applied changes to address the issue. Services appear to be starting up normally, and we are monitoring closely for stability. Impact: Services should be becoming available. The site will continue to come online over the next hour. If you encounter problems, please report them to Auvik Support. Next Steps: A final update will be posted once we confirm the resolution.

4. 2025년 8월 27일 오후 11:06 UTCresolved

   The access issues for clients on the US4 cluster have been fully resolved, and services are operating as expected. Impact: Customers should no longer experience any related issues. If you continue to experience issues, please report them to Auvik Support.