История сбоев Fossa

1. 15 октября 2026 г. в 15:30 UTCmonitoring

   Реализовано исправление, и мы отслеживаем результаты.

2. 15 октября 2026 г. в 16:03 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 6 октября 2026 г. в 20:01 UTCidentified

   Наш конвейер для обновления нашего набора данных vuln испытывает ухудшение производительности. Пострадает новая информация об уязвимостях.

2. 8 октября 2026 г. в 23:37 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 5 августа 2026 г. в 20:50 UTCinvestigating

   We are currently investigating an app wide outage

2. 5 августа 2026 г. в 21:10 UTCmonitoring

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

3. 5 августа 2026 г. в 21:20 UTCresolved

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

1. 1 июня 2026 г. в 21:46 UTCinvestigating

   We are currently investigating this issue.

2. 1 июня 2026 г. в 21:47 UTCinvestigating

   We are continuing to investigate this issue.

3. 1 июня 2026 г. в 22:42 UTCresolved

   This incident has been resolved.

1. 7 мая 2026 г. в 20:01 UTCinvestigating

   We are currently investigating this issue.

2. 7 мая 2026 г. в 20:12 UTCidentified

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

3. 7 мая 2026 г. в 21:21 UTCresolved

   This incident has been resolved.

1. 6 мая 2026 г. в 15:51 UTCinvestigating

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

2. 6 мая 2026 г. в 15:55 UTCinvestigating

   We are continuing to investigate this issue.

3. 6 мая 2026 г. в 17:12 UTCmonitoring

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

4. 6 мая 2026 г. в 20:48 UTCresolved

   This incident has been resolved.

1. 21 апреля 2026 г. в 18:36 UTCinvestigating

   We are currently investigating this issue.

2. 21 апреля 2026 г. в 18:47 UTCinvestigating

   We are continuing to investigate this issue.

3. 21 апреля 2026 г. в 19:34 UTCresolved

   This incident has been resolved.

1. 16 апреля 2026 г. в 22:14 UTCinvestigating

   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

2. 16 апреля 2026 г. в 22:45 UTCidentified

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

3. 16 апреля 2026 г. в 23:28 UTCresolved

   This incident has been resolved.

1. 17 марта 2026 г. в 01:55 UTCmonitoring

   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.

2. 17 марта 2026 г. в 04:08 UTCresolved

   Degraded API performance has been resolved.

1. 12 марта 2026 г. в 20:48 UTCinvestigating

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

2. 12 марта 2026 г. в 20:49 UTCinvestigating

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

3. 12 марта 2026 г. в 21:24 UTCmonitoring

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

4. 12 марта 2026 г. в 21:33 UTCresolved

   This incident has been resolved.

1. 26 февраля 2026 г. в 14:04 UTCinvestigating

   We are investigating the additional build slowdown from today.

2. 27 февраля 2026 г. в 20:09 UTCmonitoring

   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.

3. 27 февраля 2026 г. в 20:59 UTCresolved

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

1. 25 февраля 2026 г. в 14:28 UTCinvestigating

   We are currently investigating this issue.

2. 25 февраля 2026 г. в 21:05 UTCinvestigating

   We are continuing to investigate this issue.

3. 25 февраля 2026 г. в 21:05 UTCmonitoring

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

4. 26 февраля 2026 г. в 00:35 UTCmonitoring

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

5. 26 февраля 2026 г. в 02:37 UTCmonitoring

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

6. 26 февраля 2026 г. в 02:38 UTCresolved

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

1. 16 декабря 2025 г. в 23:50 UTCinvestigating

   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.

2. 17 декабря 2025 г. в 01:37 UTCmonitoring

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

3. 17 декабря 2025 г. в 02:02 UTCresolved

   This incident has been resolved.

1. 24 ноября 2025 г. в 21:54 UTCinvestigating

   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

2. 24 ноября 2025 г. в 21:58 UTCinvestigating

   We are continuing to investigate this issue.

3. 24 ноября 2025 г. в 22:14 UTCidentified

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

4. 25 ноября 2025 г. в 01:04 UTCmonitoring

   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.

5. 25 ноября 2025 г. в 02:47 UTCresolved

   This incident has been resolved.

1. 11 сентября 2025 г. в 16:04 UTCinvestigating

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

2. 11 сентября 2025 г. в 17:31 UTCmonitoring

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

3. 11 сентября 2025 г. в 20:46 UTCresolved

   This incident has been resolved.

1. 27 августа 2025 г. в 15:23 UTCinvestigating

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

2. 27 августа 2025 г. в 15:35 UTCidentified

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

3. 27 августа 2025 г. в 16:16 UTCmonitoring

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

4. 27 августа 2025 г. в 17:17 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 27 августа 2025 г. в 21:39 UTCresolved

   This incident has been resolved.

1. 10 июля 2025 г. в 20:30 UTCidentified

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

2. 10 июля 2025 г. в 21:38 UTCresolved

   This incident has been resolved.

1. 18 июня 2025 г. в 13:25 UTCinvestigating

   We are currently investigating this issue.

2. 18 июня 2025 г. в 13:28 UTCinvestigating

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

3. 18 июня 2025 г. в 13:37 UTCidentified

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

4. 18 июня 2025 г. в 13:38 UTCmonitoring

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

5. 18 июня 2025 г. в 13:40 UTCresolved

   This incident has been resolved.

1. 12 июня 2025 г. в 20:23 UTCidentified

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

2. 12 июня 2025 г. в 22:32 UTCidentified

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

3. 13 июня 2025 г. в 11:01 UTCresolved

   This incident has been resolved.

1. 5 июня 2025 г. в 14:17 UTCinvestigating

   We are investigating an impact to report generation and issue scans

2. 5 июня 2025 г. в 14:31 UTCidentified

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

3. 5 июня 2025 г. в 15:31 UTCmonitoring

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

4. 5 июня 2025 г. в 15:52 UTCresolved

   This incident has been resolved.