Störungsverlauf von Fossa

We are currently investigating an app wide outage

A fix has been implemented and we're monitoring the results.

All systems are now operational. The root cause was traced to a degradation in AWS services which has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified and a fix is in progress.

This incident has been resolved.

We have observed high app latency, we are currently investigating.

We are continuing to investigate this issue.

A fix has been implemented and we're monitoring the results.

This incident has been resolved.

We are currently investigating this issue.

We are continuing to investigate this issue.

This incident has been resolved.

We are seeing a large spike in DB CPU usage on our analysis service, which is causing slowness when accessing the service. We are actively investigating this

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

This incident has been resolved.

We are currently experiencing a higher than normal amount of load, which may be causing the API to be slow or unresponsive. We're investigating the cause and will provide an update as soon as possible.

Degraded API performance has been resolved.

We are investigating a service disruption that started at 4:17pm EDT

All systems are now accessible but may continue to see degraded performance while we work on full resolution.

A fix has been implemented and full functionality restored, we're monitoring performance now.

This incident has been resolved.

We are investigating the additional build slowdown from today.

Our team has implemented fixes that are beginning to stabilize the issue. We are continuing to monitor closely, and are looking into long-term solutions beyond the stabilization.

The incident is now resolved. Our engineering team continues to monitor, and we will be working to address long-term concerns going forward.

We are currently investigating this issue.

We are continuing to investigate this issue.

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

We have implemented fixes and returned to baseline level for build processing, but are continuing to monitor closely.

Thank you for your patience. This incident is resolved, and source code analysis - CLI has been restored. We apologize for any inconvenience.

Thank you for your patience. This incident is resolved, and source code analysis - CLI has been restored. We apologize for any inconvenience.

We are currently investigating an issue related to how long FOSSA issue scans are taking to complete. This also impacts the FOSSA CLI's "fossa test" command. Users may also experience slowness within the web application.

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

This incident has been resolved.

We are currently experiencing a service disruption affecting vulnerability issue scanning. Scans are failing to complete and are not generating security issues for affected projects. Impact: Projects being scanned are not receiving vulnerability issue detection results

We are continuing to investigate this issue.

We have identified the cause of the outage and are working to implement a mitigation.

We have implemented a fix and issue scans are no longer failing. There continues to be a delay in the processing of issue scans as we work through the backlog of failed scans.

This incident has been resolved.

We are currently experiencing elevated build times, we are investigating the potential cause of this.

We believe that build queues are organically back to normal at this time and will continue to monitor the situation.

This incident has been resolved.

We are currently investigating the cause of very high load times on various code analysis submissions

We believe to have identified the cause and are testing a solution.

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

We are continuing to monitor for any further issues.

This incident has been resolved.

We are seeing some temporarily degraded performance and anticipate near-term resolution

This incident has been resolved.

We are currently investigating this issue.

We believe to have identified one potential cause of the outage and are investigating further.

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

We have identified what be to be the root cause and service has been restored.

This incident has been resolved.

We are currently impacted by the publicized Cloudflare (https://www.cloudflarestatus.com/) and GCP (https://status.cloud.google.com/) outages.

We are continuing to monitor our provider's availability. It appears that Cloudflare has restored services but GCP is still experiencing issues.

This incident has been resolved.

We are investigating an impact to report generation and issue scans

We have traced an error related to issue scans, this is potentially also related to reports, will investigate that separately.

We've resolved the issue scanning issue and are working on the reporting items with high priority.

This incident has been resolved.

We are currently investigating this issue.

The issue has been identified, we are reverting a recent update

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

This incident has been resolved.

We are currently investigating a high CPU load issue which is causing UI slowness and other core services slowness

We are continuing to investigate the cause of the CPU load.

We are continuing to investigate this issue.

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

We are continuing to monitor for any further issues.

We are continuing to monitor the CPU load concerns and are incrementally testing permanent resolutions

We have concluded that CPU loads are back to sustained, nominal levels. We are therefore considering this resolved at this time.