BigPanda Outage History

BigPanda is up right now

BigPanda had 17 outages in the last 2 years totaling 55h 25m of downtime — averaging 0.7 incidents per month.

There were 17 BigPanda outages since August 21, 2025 totaling 55h 25m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.bigpanda.io

Major July 22, 2026

BigPanda OIM Processing Errors (US)

Detected by Pingoru
Jul 22, 2026, 03:17 PM UTC
Resolved
Jul 22, 2026, 03:49 PM UTC
Duration
32m
Affected: Data Consumption
Timeline · 3 updates
  1. investigating Jul 22, 2026, 03:17 PM UTC

    There is a current issue with OIM processing. Our teams are engaged and investigating. We are working to mitigate impacts to our customers as quickly as possible. Additional updates will be shared every 30 minutes or less as more details become available. We apologize for any inconvenience that this may be causing.

  2. monitoring Jul 22, 2026, 03:23 PM UTC

    A fix has been implemented and we are monitoring. All events sent have been queued and are processing now.

  3. resolved Jul 22, 2026, 03:49 PM UTC

    The incident has been resolved. Systems are functioning nominally.

Read the full incident report →

Minor July 15, 2026

Big Panda Console Incident Search misbehaving- Prod Us-West-1

Detected by Pingoru
Jul 15, 2026, 02:41 PM UTC
Resolved
Jul 16, 2026, 02:35 AM UTC
Duration
11h 54m
Affected: Incident Feed Search
Timeline · 5 updates
  1. investigating Jul 15, 2026, 02:41 PM UTC

    This is a notice that we are aware of an issue affecting the Incident Search functionality in the BigPanda Console. Our R&D team is engaged and is investigating this issue with Priority. We will provide an update once we know more. Thank you for your patience, and apologies for the inconvenience.

  2. identified Jul 15, 2026, 03:18 PM UTC

    Engineering is actively investigating. Leading theory points to a backend infrastructure issue tied to a recent update; a fix is being validated now. Thank you for your patience, and we apologize for the inconvenience.

  3. monitoring Jul 15, 2026, 04:20 PM UTC

    The team has identified the issue and applied a fix to the service affecting the incident search. They are monitoring to ensure everything is working as expected.

  4. monitoring Jul 15, 2026, 05:43 PM UTC

    The team continues to monitor the services as the data backlog is processed. We anticipate everything to be resolved within an hour.

  5. resolved Jul 16, 2026, 02:35 AM UTC

    Our team has resolved the incident, and all services have returned to normal operation. We apologize for any inconvenience this may have caused. If you continue to experience any issues, please reach out to us via our in-app chat or at [email protected].

Read the full incident report →

Minor July 12, 2026

Issues updating Incident Tags

Detected by Pingoru
Jul 12, 2026, 03:08 PM UTC
Resolved
Jul 12, 2026, 06:09 PM UTC
Duration
3h 1m
Affected: Incident Enrichment & Environments Population
Timeline · 3 updates
  1. investigating Jul 12, 2026, 03:08 PM UTC

    Some users may be experiencing issues with updating Incident Tags via API/manually. Our teams are engaged and investigating. We will share updates here as soon as possible.

  2. monitoring Jul 12, 2026, 05:46 PM UTC

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

  3. resolved Jul 12, 2026, 06:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 24, 2026

Biggy Login

Detected by Pingoru
Jun 24, 2026, 12:38 PM UTC
Resolved
Jun 24, 2026, 01:05 PM UTC
Duration
27m
Affected: Biggy Services
Timeline · 3 updates
  1. identified Jun 24, 2026, 12:38 PM UTC

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

  2. identified Jun 24, 2026, 12:46 PM UTC

    SSO logins at https://app.biggy.io/login is currently redirecting users to a staging url. Other login methods are unaffected. Our teams are engaged and a fix is being deployed.

  3. resolved Jun 24, 2026, 01:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 3, 2026

API Service Disruption

Detected by Pingoru
Jun 03, 2026, 02:40 PM UTC
Resolved
Jun 03, 2026, 03:47 PM UTC
Duration
1h 7m
Affected: Tier 1 APIs: Automation & Event ProcessingTier 2 APIs: SupplementalTier 3 APIs: Tertiary
Timeline · 5 updates
  1. investigating Jun 03, 2026, 02:40 PM UTC

    Some users may be experiencing issues with BigPanda APIs. Our teams are engaged and investigating. We are working to mitigate impacts to our customers as quickly as possible. Additional updates will be shared every 30 minutes or less as more details become available. We apologize for any inconvenience that this may be causing.

  2. investigating Jun 03, 2026, 03:25 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jun 03, 2026, 03:35 PM UTC

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

  4. identified Jun 03, 2026, 03:37 PM UTC

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

  5. resolved Jun 03, 2026, 03:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 30, 2026

Biggy Web Application UI - Degraded Performance

Detected by Pingoru
Apr 30, 2026, 08:40 PM UTC
Resolved
Apr 30, 2026, 10:16 PM UTC
Duration
1h 35m
Affected: Biggy Services
Timeline · 3 updates
  1. investigating Apr 30, 2026, 08:40 PM UTC

    Greetings, Users may currently experience sluggish load times while navigating through pages in the Biggy Web Application UI. Our R&D team is actively engaged and is investigating the issue.

  2. monitoring Apr 30, 2026, 09:15 PM UTC

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

  3. resolved Apr 30, 2026, 10:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 8, 2026

Intermittent UI Latency

Detected by Pingoru
Apr 08, 2026, 11:01 AM UTC
Resolved
Apr 08, 2026, 11:32 AM UTC
Duration
31m
Affected: Incident FeedIncident Feed Search
Timeline · 3 updates
  1. identified Apr 08, 2026, 11:01 AM UTC

    Some users may be intermittently experiencing UI issues at this time due to a deployment. Our teams have identified the cause and have rolled back the change. We are now monitoring the results.

  2. monitoring Apr 08, 2026, 11:08 AM UTC

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

  3. resolved Apr 08, 2026, 11:32 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 24, 2026

Biggy Call Transcription experiencing issues

Detected by Pingoru
Mar 24, 2026, 04:23 PM UTC
Resolved
Mar 24, 2026, 07:34 PM UTC
Duration
3h 10m
Affected: Call Transcription
Timeline · 4 updates
  1. investigating Mar 24, 2026, 04:23 PM UTC

    Due to an issue with a third-party vendor, customers might experience issues with Call Transcriptions. We are checking with our vendor and will update this page with more information.

  2. monitoring Mar 24, 2026, 07:12 PM UTC

    A fix has been deployed by our third-party vendor, and we are actively monitoring our Biggy services, with a focus on the Call Transcriptions service. We will provide the next update in 30 minutes.

  3. monitoring Mar 24, 2026, 07:14 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Mar 24, 2026, 07:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 9, 2026

Latency in Alert Enrichment services

Detected by Pingoru
Feb 09, 2026, 03:37 PM UTC
Resolved
Feb 09, 2026, 06:23 PM UTC
Duration
2h 46m
Affected: Alert Enrichment
Timeline · 7 updates
  1. investigating Feb 09, 2026, 03:37 PM UTC

    We are observing Latency in Alert Enrichment services. Our team is engaged and is looking to identify the root cause

  2. investigating Feb 09, 2026, 04:06 PM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 09, 2026, 04:46 PM UTC

    We are working to mitigate impacts to our customers as quickly as possible. Additional updates will be shared every 30 minutes as more details become available. We apologize for any inconvenience that this may be causing.

  4. investigating Feb 09, 2026, 05:16 PM UTC

    The team are currently working to stabilise the service.

  5. identified Feb 09, 2026, 05:44 PM UTC

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

  6. monitoring Feb 09, 2026, 05:48 PM UTC

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

  7. resolved Feb 09, 2026, 06:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 18, 2025

CloudFlare Outage Affecting Services

Detected by Pingoru
Nov 18, 2025, 11:58 AM UTC
Resolved
Nov 18, 2025, 01:28 PM UTC
Duration
1h 29m
Affected: Data ConsumptionLoginTier 1 APIs: Automation & Event Processing
Timeline · 6 updates
  1. investigating Nov 18, 2025, 11:58 AM UTC

    Due to a Cloudflare outage, login to the BigPanda UI is intermittently unavailable. We are investigating this issue.

  2. investigating Nov 18, 2025, 12:05 PM UTC

    Due to a Cloudflare outage, login to the BigPanda UI is intermittently unavailable, and data consumption is affected. We are investigating this issue.

  3. identified Nov 18, 2025, 12:32 PM UTC

    We've identified the issue and applied a fix. Flushing DNS should allow users to log in to the BigPanda UI.

  4. monitoring Nov 18, 2025, 12:46 PM UTC

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

  5. monitoring Nov 18, 2025, 01:13 PM UTC

    We are continuing to monitor the situation with the Cloudflare outage. https://www.cloudflarestatus.com/

  6. resolved Nov 18, 2025, 01:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 6, 2025

BigPanda -Outbound Sharing Latencies

Detected by Pingoru
Nov 06, 2025, 09:28 PM UTC
Resolved
Nov 06, 2025, 10:16 PM UTC
Duration
47m
Affected: Incident Sharing
Timeline · 5 updates
  1. investigating Nov 06, 2025, 09:28 PM UTC

    We are currently encountering delays in sharing incidents from BigPanda to our Outbound Sharing services. We are investigating the issue. What's impacted? • Incident Sharing We are working to mitigate impacts to our customers as quickly as possible. Additional updates will be shared every 30 minutes or less as more details become available. We apologize for any inconvenience that this may be causing.

  2. investigating Nov 06, 2025, 09:30 PM UTC

    We are continuing to investigate this issue.

  3. identified Nov 06, 2025, 09:49 PM UTC

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

  4. monitoring Nov 06, 2025, 09:53 PM UTC

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

  5. resolved Nov 06, 2025, 10:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 20, 2025

BigPanda - AWS Service Outage [3rd Party]

Detected by Pingoru
Oct 20, 2025, 06:25 PM UTC
Resolved
Oct 21, 2025, 03:24 AM UTC
Duration
8h 59m
Affected: Data ConsumptionIncident SharingOutbound IntegrationsThird Party
Timeline · 4 updates
  1. investigating Oct 20, 2025, 06:25 PM UTC

    AWS is currently experiencing an outage. In effect, BigPanda users may be experiencing issues with BigPanda's Inbound and Outbound services. Our R&D teams are currently engaged and investigating. What's impacted? Outbound Integrations Inbound Integrations We are working to mitigate impacts to our customers as quickly as possible. Additional updates will be shared every 30 minutes or less as more details become available. We apologize for any inconvenience that this may be causing.

  2. identified Oct 20, 2025, 08:08 PM UTC

    AWS continues to recover. All AWS services and instance launches are succeeding across multiple Availability Zones in the US-EAST-1 Regions. To mitigate the impact for our customers, BigPanda migrated most of our inbound and outbound standard integrations and will continue to monitor the situation.

  3. monitoring Oct 20, 2025, 09:09 PM UTC

    AWS continues to recover. All AWS services and instance launches are succeeding across multiple Availability Zones in the US-EAST-1 Regions. We are continuing to monitor BigPanda services and the situation.

  4. resolved Oct 21, 2025, 03:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Major October 20, 2025

AWS outage affecting multiple services

Detected by Pingoru
Oct 20, 2025, 07:47 AM UTC
Resolved
Oct 20, 2025, 02:27 PM UTC
Duration
6h 39m
Affected: Data ConsumptionIncident SharingTier 1 APIs: Automation & Event ProcessingAlert EnrichmentOutbound IntegrationsIncident FeedTier 2 APIs: SupplementalAlert Filtering & Maintenance PlansETL PipelineIncident Feed SearchTier 3 APIs: TertiaryIncident Enrichment & Environments PopulationAutomatic Incident TriageCorrelationRoot Cause ChangesAdministrator ScreensIncident ActionsIncident Activity FeedThird PartyUnified SearchIntegration Diagnostics / Troubleshooting
Timeline · 8 updates
  1. investigating Oct 20, 2025, 07:47 AM UTC

    AWS is experiencing an outage that is affecting multiple of our services. We are still investigating the scope of impact.

  2. investigating Oct 20, 2025, 08:17 AM UTC

    We continue to investigate and work on mitigating the effect of the AWS outage. https://health.aws.amazon.com/health/status

  3. identified Oct 20, 2025, 08:55 AM UTC

    AWS continues to investigate the outage on its end in the US-EAST-1 Region. Custom solutions are still affected, as well as some of the Standard integrations. We are seeing the main pipeline and OIM (Open Integration Manager) services return to normal operation. https://health.aws.amazon.com/health/status

  4. monitoring Oct 20, 2025, 09:41 AM UTC

    AWS applied a fix in the US-EAST-1 Region, and we are seeing services starting to work. Inbound Integrations and Event Processing, outbound integrations are returning to full operation. Custom solutions are still affected to a degree, and we are investigating. We are monitoring the health of other impacted services. https://health.aws.amazon.com/health/status

  5. monitoring Oct 20, 2025, 10:13 AM UTC

    Currently, the AWS outage has affected Standard Integrations (non-OIM integrations), Custom solutions, and our ServiceNow outbound services. AWS reported improvements to services. We continue to investigate this and monitor other services.

  6. monitoring Oct 20, 2025, 11:38 AM UTC

    We are redirecting traffic from the affected AWS region to mitigate the effect on custom solutions and ServiceNow services, and seeing improvements in traffic for ServiceNow shares. We continue to monitor all services.

  7. monitoring Oct 20, 2025, 12:01 PM UTC

    We are seeing that all services based in the US-East-1 AWS region are going back to normal operation. We continue to monitor the situation

  8. resolved Oct 20, 2025, 02:27 PM UTC

    This incident has been resolved. We rolled back any redirections made to mitigate this incident, and the pipeline is operating as expected If you encounter any issues, please reach out to BigPanda Support via our live in-app chat or via [email protected].

Read the full incident report →

Minor September 26, 2025

BigPanda Support Portal Performance Degradation

Detected by Pingoru
Sep 26, 2025, 11:53 AM UTC
Resolved
Sep 26, 2025, 12:38 PM UTC
Duration
44m
Affected: Third Party
Timeline · 3 updates
  1. investigating Sep 26, 2025, 11:53 AM UTC

    Some users might experience delays or UI issues in our Support Portal while our ticketing vendor is working to resolve an incident. We are keeping an eye out for urgent matters, and for now it is advisable to reach out to us via chat if you do experience any issue in the BigPanda Support Portal.

  2. monitoring Sep 26, 2025, 12:18 PM UTC

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

  3. resolved Sep 26, 2025, 12:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 27, 2025

5xx OIM Ingestion Errors

Detected by Pingoru
Aug 27, 2025, 06:16 PM UTC
Resolved
Aug 27, 2025, 07:50 PM UTC
Duration
1h 33m
Affected: Data Consumption
Timeline · 3 updates
  1. investigating Aug 27, 2025, 06:16 PM UTC

    We are observing 5xx OIM Ingestion Errors. Our teams are engaged and investigating. We are actively working to mitigate the impact on our customers as quickly as possible. At this time, the US and EU regions are affected. We will share additional updates as soon as more information becomes available. We sincerely apologize for any inconvenience this may cause.

  2. monitoring Aug 27, 2025, 06:48 PM UTC

    The team has identified and mitigated by re-routing services, and they are now monitoring the situation.

  3. resolved Aug 27, 2025, 07:50 PM UTC

    This incident has been successfully mitigated and resolved.

Read the full incident report →

Minor August 26, 2025

Unified Analytics - Showing Stale Data

Detected by Pingoru
Aug 26, 2025, 12:46 PM UTC
Resolved
Aug 26, 2025, 06:04 PM UTC
Duration
5h 18m
Affected: Unified Analytics
Timeline · 4 updates
  1. investigating Aug 26, 2025, 12:46 PM UTC

    Currently, the Unified Analytics page is operational, but is displaying data from 24 hours ago or older. We are actively investigating what is preventing the data refresh.

  2. identified Aug 26, 2025, 12:55 PM UTC

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

  3. monitoring Aug 26, 2025, 03:46 PM UTC

    A fix has been applied, and we are monitoring as the Cubes rebuild.

  4. resolved Aug 26, 2025, 06:04 PM UTC

    This incident has been resolved, and the cubes have updated as expected.

Read the full incident report →

Minor August 21, 2025

5xx OIM Errors

Detected by Pingoru
Aug 21, 2025, 06:48 PM UTC
Resolved
Aug 21, 2025, 11:35 PM UTC
Duration
4h 46m
Affected: Data ConsumptionTier 1 APIs: Automation & Event Processing
Timeline · 3 updates
  1. identified Aug 21, 2025, 06:48 PM UTC

    We are observing 5xx OIM errors. Our teams are engaged and investigating. We are working to mitigate impacts to our customers as quickly as possible. We have migrated the services traffic to process in the region US-WEST-1 to mitigate the issue. We will provide more details as it become available. We apologize for any inconvenience that this may be causing. Thank you, BigPanda

  2. monitoring Aug 21, 2025, 07:03 PM UTC

    The team has identified and mitigated the issue by switching to US-WEST-1, and they are now monitoring the situation.

  3. resolved Aug 21, 2025, 11:35 PM UTC

    This incident has been successfully mitigated and resolved.

Read the full incident report →