BigPanda had 15 outages in the last 2 years totaling 40h 44m of downtime — averaging 0.6 incidents per month.
There were 15 BigPanda outages since July 23, 2025 totaling 40h 44m of downtime. Each is summarised below — incident details, duration, and resolution information.
The issue has been identified and a fix is being implemented.
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.
This incident has been resolved.
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.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are observing Latency in Alert Enrichment services. Our team is engaged and is looking to identify the root cause
We are continuing to investigate this issue.
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.
The team are currently working to stabilise the service.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Due to a Cloudflare outage, login to the BigPanda UI is intermittently unavailable. We are investigating this issue.
Due to a Cloudflare outage, login to the BigPanda UI is intermittently unavailable, and data consumption is affected. We are investigating this issue.
We've identified the issue and applied a fix. Flushing DNS should allow users to log in to the BigPanda UI.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor the situation with the Cloudflare outage. https://www.cloudflarestatus.com/
This incident has been resolved.
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.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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.
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.
This incident has been resolved.
AWS is experiencing an outage that is affecting multiple of our services. We are still investigating the scope of impact.
We continue to investigate and work on mitigating the effect of the AWS outage. https://health.aws.amazon.com/health/status
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
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
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.
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.
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
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].
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.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
The team has identified and mitigated by re-routing services, and they are now monitoring the situation.
This incident has been successfully mitigated and resolved.
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.
The issue has been identified and a fix is being implemented.
A fix has been applied, and we are monitoring as the Cubes rebuild.
This incident has been resolved, and the cubes have updated as expected.
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
The team has identified and mitigated the issue by switching to US-WEST-1, and they are now monitoring the situation.
This incident has been successfully mitigated and resolved.
We are currently experiencing latencies in our pipeline, specifically within our Environment services. Our R&D team is actively investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.