Instabug Outage History

Instabug is up right now

Instabug had 9 outages in the last 2 years totaling 40h 30m of downtime — averaging 0.4 incidents per month.

There were 9 Instabug outages since November 13, 2024 totaling 40h 30m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://statuspage.instabug.com

Major November 23, 2025

Data ingestion is down

Detected by Pingoru
Nov 23, 2025, 05:56 PM UTC
Resolved
Nov 23, 2025, 08:13 PM UTC
Duration
2h 17m
Affected: Web AppAPM
Timeline · 3 updates
  1. identified Nov 23, 2025, 05:56 PM UTC

    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. monitoring Nov 23, 2025, 07:02 PM UTC

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

  3. resolved Nov 23, 2025, 08:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 6, 2025

Partial Service Outage

Detected by Pingoru
Nov 06, 2025, 12:56 PM UTC
Resolved
Nov 06, 2025, 12:56 PM UTC
Duration
Affected: DSYM UploadWeb AppAPM
Timeline · 1 update
  1. resolved Nov 06, 2025, 12:56 PM UTC

    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.

Read the full incident report →

Minor October 20, 2025

Resources Throttling

Detected by Pingoru
Oct 20, 2025, 04:54 PM UTC
Resolved
Oct 20, 2025, 07:38 PM UTC
Duration
2h 44m
Affected: Core
Timeline · 2 updates
  1. monitoring Oct 20, 2025, 04:54 PM UTC

    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. resolved Oct 20, 2025, 07:38 PM UTC

    All systems are operational

Read the full incident report →

Major June 25, 2025

Dashboard and SDK APIs are down for some users

Detected by Pingoru
Jun 25, 2025, 01:59 PM UTC
Resolved
Jun 25, 2025, 03:58 PM UTC
Duration
1h 59m
Affected: CoreDSYM UploadWeb AppAPM
Timeline · 5 updates
  1. investigating Jun 25, 2025, 03:20 PM UTC

    No new events being ingested

  2. identified Jun 25, 2025, 03:24 PM UTC

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

  3. identified Jun 25, 2025, 03:25 PM UTC

    Dashboard is up and running

  4. monitoring Jun 25, 2025, 03:26 PM UTC

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

  5. resolved Jun 25, 2025, 03:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 19, 2025

Dashboard is unstable due to configuration issues

Detected by Pingoru
May 19, 2025, 12:04 PM UTC
Resolved
May 19, 2025, 01:48 PM UTC
Duration
1h 43m
Affected: DSYM UploadWeb AppAPM
Timeline · 6 updates
  1. investigating May 19, 2025, 12:26 PM UTC

    Dashboard is unstable due to configuration issues

  2. identified May 19, 2025, 12:27 PM UTC

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

  3. monitoring May 19, 2025, 12:37 PM UTC

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

  4. monitoring May 19, 2025, 01:11 PM UTC

    We are continuing to monitor for any further issues.

  5. monitoring May 19, 2025, 01:29 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved May 19, 2025, 01:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 6, 2025

Certain crash reporting pages are experiencing performance issues or delays

Detected by Pingoru
Jan 06, 2025, 06:00 PM UTC
Resolved
Jan 07, 2025, 06:24 PM UTC
Duration
1d
Affected: Core
Timeline · 4 updates
  1. investigating Jan 06, 2025, 06:00 PM UTC

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

  2. identified Jan 06, 2025, 07:23 PM UTC

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

  3. monitoring Jan 06, 2025, 08:28 PM UTC

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

  4. resolved Jan 07, 2025, 06:24 PM UTC

    This incident has been resolved.

Read the full incident report →