Instabug 장애 기록

1. 2026년 9월 13일 오후 5:18 UTCidentified

   대시보드의 Elevated 오류율

2. 2026년 9월 13일 오후 5:23 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

3. 2026년 9월 13일 오후 5:44 UTCresolved

   이 사건은 해결되었습니다.

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

1. 2026년 7월 8일 오후 12:38 UTCmonitoring

   7 월 7, 2026에 13 UTC 주위에 시작, 일부 고객은 자신의 대시보드에 표시된 데이터에서 느린로드 시간과 지연을 경험할 수 있습니다. 우리는 우리의 핵심 인프라의 일부에 부하를 올리는 원인을 추적하고 영향을받는 시스템을 사기를 포함하여 완화를 적용했습니다. 서비스 성능은 크게 회복되었습니다. 우리는 적극적으로 상황을 모니터링하고 반복을 방지하기 위해 추가적인 보호기를 압연합니다. 우리는 더 많은 업데이트를 게시합니다.

2. 2026년 7월 8일 오후 1:51 UTCresolved

   해결 및 사건이 해결되었습니다.

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

1. 2026년 6월 10일 오후 7:05 UTCidentified

   We're currently experiencing delays in processing and displaying some incoming data. New crash reports, performance monitoring metrics (app launches, network requests, traces, and screen visits), and session analytics may appear with a lag or be temporarily incomplete in your dashboards. Our engineering team has identified the cause and is actively working to restore normal processing speeds. No data is being lost. Affected information will be processed and appear once the backlog clears.

2. 2026년 6월 10일 오후 7:34 UTCidentified

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

3. 2026년 6월 11일 오전 7:35 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2026년 6월 11일 오후 3:39 UTCresolved

   This incident has been resolved.

1. 2026년 6월 4일 오전 11:47 UTCresolved

   Affected: APM, Dashboard, Crashes, Chats, Surveys Start: June 4, 2026 at 10:56 UTC Resolved:June 4, 2026 at 11:08 UTC Some users experienced intermittent issues with SDK data ingestion and dashboard access during this window. The team identified the issue and restored capacity. All services are now operating normally.

1. 2025년 11월 23일 오후 5:56 UTCidentified

   There is an issue with ingesting the data into our databases, we are currently working on a fix, it has been down for the past 1.5 hours. No data loss is expected

2. 2025년 11월 23일 오후 7:02 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2025년 11월 23일 오후 8:13 UTCresolved

   This incident has been resolved.

1. 2025년 11월 6일 오후 12:56 UTCresolved

   we experienced an unexpected outage lasting around 40 minutes, causing partial unavailability and degraded performance across core services. Systems were restored after mitigation steps, and services are now operating normally.

1. 2025년 10월 20일 오후 4:54 UTCmonitoring

   Earlier today, AWS had operational issues with no effect on our APIs & Dashboards https://health.aws.amazon.com/health/status We've just started experiencing throttling to some of our infrastructure on AWS that are degrading our services

2. 2025년 10월 20일 오후 7:38 UTCresolved

   All systems are operational

1. 2025년 6월 25일 오후 3:20 UTCinvestigating

   No new events being ingested

2. 2025년 6월 25일 오후 3:24 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2025년 6월 25일 오후 3:25 UTCidentified

   Dashboard is up and running

4. 2025년 6월 25일 오후 3:26 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

5. 2025년 6월 25일 오후 3:58 UTCresolved

   This incident has been resolved.

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

   Dashboard is unstable due to configuration issues

2. 2025년 5월 19일 오후 12:27 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2025년 5월 19일 오후 12:37 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2025년 5월 19일 오후 1:29 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 2025년 5월 19일 오후 1:48 UTCresolved

   This incident has been resolved.

1. 2025년 1월 6일 오후 6:00 UTCinvestigating

   1/6/2025 4:50pm GMT: Certain crash reporting pages are experiencing performance issues or delays. Investigation started

2. 2025년 1월 6일 오후 7:23 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2025년 1월 6일 오후 8:28 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2025년 1월 7일 오후 6:24 UTCresolved

   This incident has been resolved.

1. 2024년 12월 29일 오후 4:07 UTCresolved

   12:00pm GMT: Part of the sessions processing for counts went down -for legacy versions of the SDK-. We're working on restoring it. 1:47pm GMT: Issue fixed, and new sessions are being processed normally.

1. 2024년 12월 9일 오후 4:07 UTCresolved

   3:15pm GMT: Facing delays in processing new sessions, Investigating the issue 4:20pm GMT: Issue fixed, and processing rates restored. No data loss and no backlog

1. 2024년 11월 13일 오전 9:27 UTCresolved

   2:30am GMT: Facing delays in processing crashes and non-fatals. Investigating the issue 8:40am GMT: Issue fixed, and processing rates restored. No data loss, but seeing some delays

1. 2022년 12월 12일 오후 9:38 UTCresolved

   Location data on user sessions is incorrectly shown as originating from the United States instead of the end user's location. This was caused due to a misconfiguration on Instabug's infrastructure and was resolved once detected.

1. 2022년 11월 16일 오후 12:26 UTCinvestigating

   We are currently investigating this issue.

2. 2022년 11월 16일 오후 12:27 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2022년 11월 16일 오후 12:38 UTCresolved

   This incident has been resolved.

1. 2022년 4월 18일 오후 2:41 UTCinvestigating

   The Crashes dashboard is not rendering properly for customers. We are aware of the issue and working to promptly resolve it. This does not impact any private-cluster customers.

2. 2022년 4월 18일 오후 2:43 UTCidentified

   This issue has been identified and confirmed to be caused by a deployment by our cloud provider. A restore is currently in progress

3. 2022년 4월 18일 오후 2:49 UTCmonitoring

   Restore is done. Issue should be now resolved. We're monitoring to make sure everything is working as expected

4. 2022년 4월 18일 오후 3:02 UTCresolved

   This incident has been resolved.

5. 2022년 5월 23일 오후 4:28 UTCpostmortem

   ## Summary On April 18th, 2022, between 13:36 UTC and 14:30 UTC, Instabug experienced an operational incident that caused some crashes to not be accessible.   During this time, no crashes or occurrences were lost or dropped.  This issue only impacted viewing of crashes, and our APIs were not impacted in any way. ## What Happened Amazon Web Services \(AWS\) was performing a blue/green deployment while services underlying Instabug’s infrastructure.  During this deployment, several of the indices associated with our Elasticsearch database were incorrectly deleted.  Once the issue was discovered, Instabug engineers contacted AWS support who acknowledged the issue and restored the indices from a snapshot.  Upon restoration, services were fully functional. ## What We Are Doing About This AWS has committed to notifying us before any release or migration that may impact our services.

1. 2022년 3월 15일 오후 8:41 UTCresolved

   A server-side configuration change was rolled out that resulted in our SDK crashing when caching the response of server-side payload. Since the aforementioned API request happens right after the app has finished launching, this resulted in apps using the Instabug SDK crashing right after they launch. We were alerted about this issue as soon as it started happening and we quickly changed the configuration that caused the crash. In total, it took around 40 minutes from the first alert we got till the fix rolled out to 100% of the applications using our SDK. There is no action required from your side related to this crash.