Histórico de interrupções do Instabug

1. 8 Gouere 2026 da 12:38 UTCmonitoring

   A partir das 13:00 UTC em 7 de julho de 2026, alguns clientes podem ter experimentado tempos de carga mais lentos e atrasos nos dados que aparecem em seus painéis. Rastreamos a causa para uma carga elevada em parte de nossa infraestrutura central e aplicamos mitigação, incluindo o dimensionamento dos sistemas afetados. O desempenho do serviço recuperou em grande parte. Estamos a acompanhar activamente a situação e a estabelecer salvaguardas adicionais para evitar a recorrência. Publicaremos novas atualizações à medida que estiverem disponíveis.

2. 8 Gouere 2026 da 13:51 UTCresolved

   Conserta tudo e o incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 10 Mezheven 2026 da 19: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. 10 Mezheven 2026 da 19:34 UTCidentified

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

3. 11 Mezheven 2026 da 07:35 UTCmonitoring

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

4. 11 Mezheven 2026 da 15:39 UTCresolved

   This incident has been resolved.

1. 4 Mezheven 2026 da 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. 23 Du 2025 da 17: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. 23 Du 2025 da 19:02 UTCmonitoring

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

3. 23 Du 2025 da 20:13 UTCresolved

   This incident has been resolved.

1. 6 Du 2025 da 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. 20 Here 2025 da 16: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. 20 Here 2025 da 19:38 UTCresolved

   All systems are operational

1. 25 Mezheven 2025 da 15:20 UTCinvestigating

   No new events being ingested

2. 25 Mezheven 2025 da 15:24 UTCidentified

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

3. 25 Mezheven 2025 da 15:25 UTCidentified

   Dashboard is up and running

4. 25 Mezheven 2025 da 15:26 UTCmonitoring

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

5. 25 Mezheven 2025 da 15:58 UTCresolved

   This incident has been resolved.

1. 19 Mae 2025 da 12:26 UTCinvestigating

   Dashboard is unstable due to configuration issues

2. 19 Mae 2025 da 12:27 UTCidentified

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

3. 19 Mae 2025 da 12:37 UTCmonitoring

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

4. 19 Mae 2025 da 13:29 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 19 Mae 2025 da 13:48 UTCresolved

   This incident has been resolved.

1. 6 Genver 2025 da 18:00 UTCinvestigating

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

2. 6 Genver 2025 da 19:23 UTCidentified

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

3. 6 Genver 2025 da 20:28 UTCmonitoring

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

4. 7 Genver 2025 da 18:24 UTCresolved

   This incident has been resolved.

1. 29 Kerzu 2024 da 16: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. 9 Kerzu 2024 da 16: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. 13 Du 2024 da 09: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. 12 Kerzu 2022 da 21: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. 16 Du 2022 da 12:26 UTCinvestigating

   We are currently investigating this issue.

2. 16 Du 2022 da 12:27 UTCmonitoring

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

3. 16 Du 2022 da 12:38 UTCresolved

   This incident has been resolved.

1. 18 Ebrel 2022 da 14: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. 18 Ebrel 2022 da 14: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. 18 Ebrel 2022 da 14:49 UTCmonitoring

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

4. 18 Ebrel 2022 da 15:02 UTCresolved

   This incident has been resolved.

5. 23 Mae 2022 da 16: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. 15 Meurzh 2022 da 20: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.