Snapshot 231566
Raw (normalized text)
Scripts and page chrome removed; this is what change detection compares.
{
"incidents": [
{
"created_at": "2026-03-04T14:40:21Z",
"id": "01KJWMNVAMXSR9RK369V6AFAE1",
"impact": "major",
"incident_updates": [
{
"body": "Scans alongside with their associated tasks are running as expected.\n\nWe apologise for the inconvenience.",
"created_at": "2026-03-05T07:25:04Z",
"display_at": "2026-03-05T07:25:04Z",
"id": "01KJYE5HJ59EEG919QVHWMA5TG",
"incident_id": "01KJWMNVAMXSR9RK369V6AFAE1",
"status": "resolved",
"updated_at": "2026-03-05T07:25:37Z"
},
{
"body": "We're actively monitoring the system. The v5.19 migration and deployment completed successfully and is now available in Prowler Cloud. \n\nPreviously delayed scans are now completing normally following a reduction in database load.\n\nWe've also identified a larger queue of tasks that are still pending affecting compliance reports. Take into account these will take longer than expected to complete.\n\nWe'll continue monitoring and provide further updates as soon as they're available.",
"created_at": "2026-03-04T20:10:07Z",
"display_at": "2026-03-04T20:10:07Z",
"id": "01KJX7HNHCMHW3XKPRQWQ2QWHD",
"incident_id": "01KJWMNVAMXSR9RK369V6AFAE1",
"status": "monitoring",
"updated_at": "2026-03-04T20:20:51Z"
},
{
"body": "We're actively monitoring the system. Migrations, as part of the v5.19 release, are still running. Once completed we'll push v5.19 code. \n\nScans are still taking longer than expected and we expect a recover once migrations finish. We're working on a plan to prevent this from happening again.\n\nWe'll provide more details as soon as we have an update.",
"created_at": "2026-03-04T17:14:17Z",
"display_at": "2026-03-04T17:14:17Z",
"id": "01KJWXFQABVEM8EKZE3QFJ4VP2",
"incident_id": "01KJWMNVAMXSR9RK369V6AFAE1",
"status": "monitoring",
"updated_at": "2026-03-04T20:10:14Z"
},
{
"body": "We've identified the issue. As part of v5.19.0 release, application code was deployed before the database migration completed. Therefore application was in a partially migrated state, causing scan failures.\n\nWe've rolled back to the previous version, v5.18.3. After that, scans are running but taking longer than expected as one of the migrations is taking more than expected and increasing waits for other operations.\n\nWe'll provide more details as soon as we have an update.",
"created_at": "2026-03-04T15:49:06Z",
"display_at": "2026-03-04T15:49:06Z",
"id": "01KJWRKQV5NA70AA5NZXEZPPPP",
"incident_id": "01KJWMNVAMXSR9RK369V6AFAE1",
"status": "identified",
"updated_at": "2026-03-04T20:10:18Z"
},
{
"body": "We are currently experiencing an issue affecting all scan types across the platform. Scans are failing right after start, which means new security findings are not being generated during this time.\n\nOur team is working to identify the cause. We'll provide details as soon as possible.",
"created_at": "2026-03-04T14:40:21Z",
"display_at": "2026-03-04T10:57:00Z",
"id": "01KJWMNVAMTCFP76SW1KW3VR1B",
"incident_id": "01KJWMNVAMXSR9RK369V6AFAE1",
"status": "investigating",
"updated_at": "2026-03-04T20:51:13Z"
}
],
"name": "Regular and Attack Paths Scans are failing",
"page_id": "01JQS32GMND8652REX48S4MWGG",
"resolved_at": "2026-03-05T07:25:04Z",
"status": "resolved",
"updated_at": "2026-03-11T15:46:01Z"
},
{
"created_at": "2026-01-22T22:22:16Z",
"id": "01KFKWT5YZDMBRT8QFFMPCETP2",
"impact": "major",
"incident_updates": [
{
"body": "Attack Paths and regular scans, alongside with their associated tasks like compliance overviews and scan summaries, are running as expected.\n\nWe apologise for the inconvenience.",
"created_at": "2026-01-26T08:23:07Z",
"display_at": "2026-01-26T08:23:07Z",
"id": "01KFWPCH18RBPK0TQ4A5GWP8T4",
"incident_id": "01KFKWT5YZDMBRT8QFFMPCETP2",
"status": "resolved",
"updated_at": "2026-01-26T08:23:07Z"
},
{
"body": "Attack Paths may fail intermittently. This behavior is expected to persist through the weekend while we monitor the impact of recent changes. We have increased database capacity and adjusted memory configuration based on observed load and usage patterns.\n\nRegular scans and the rest of the API are working as expected.\n\nWe are continuing to monitor closely. We will provide another update if the situation changes.",
"created_at": "2026-01-23T15:36:04Z",
"display_at": "2026-01-23T15:36:04Z",
"id": "01KFNQZ429KY2ANCTEAPBCZVVF",
"incident_id": "01KFKWT5YZDMBRT8QFFMPCETP2",
"status": "monitoring",
"updated_at": "2026-01-23T15:36:04Z"
},
{
"body": "Regular scans and their related tasks are now running as expected without delays. Attack Paths remain operational but without guarantees, as their underlying data backend is under heavy resource consumption.\n\nWe’re continuing the investigation to identify the cause. In the meantime we’ve pushed another fix to improve the findings ingestion query performance.\n\nWe are continuing to monitor closely. We will provide another update within the next 2 hours or if the situation changes.",
"created_at": "2026-01-23T13:21:05Z",
"display_at": "2026-01-23T13:21:05Z",
"id": "01KFNG7YNNN43J5CCF7JAYQF22",
"incident_id": "01KFKWT5YZDMBRT8QFFMPCETP2",
"status": "monitoring",
"updated_at": "2026-01-23T13:41:20Z"
},
{
"body": "The system has stabilized over the past few hours and scan processing has resumed. Scans and their related tasks, compliance overviews and summaries, are currently running with some delay.\n\nWe have identified ongoing elevated resource consumption in the Neo4j cluster that supports Attack Paths visualization. We’re investigating the root cause and preparing additional mitigations in case connectivity issues reoccur.\n\nWe are continuing to monitor closely. We will provide another update within the next 2 hours or if the situation changes.",
"created_at": "2026-01-23T08:50:32Z",
"display_at": "2026-01-23T08:50:32Z",
"id": "01KFN0RJM5Z4DJB090H1B6H2PM",
"incident_id": "01KFKWT5YZDMBRT8QFFMPCETP2",
"status": "monitoring",
"updated_at": "2026-01-23T09:17:32Z"
},
{
"body": "We’ve deployed a fix and are actively monitoring the results. We see signs of recovery. Services are stabilizing and we are closely monitoring the situation.\n\nWe will provide an update as soon as we have confirmation that full functionality has been restored.",
"created_at": "2026-01-23T01:36:23Z",
"display_at": "2026-01-23T01:36:23Z",
"id": "01KFM7XKFK7HQ49531AY59RDQG",
"incident_id": "01KFKWT5YZDMBRT8QFFMPCETP2",
"status": "identified",
"updated_at": "2026-01-23T01:36:23Z"
},
{
"body": "We have identified two contributing factors:\n\n1. **Attack Paths database connectivity**: The Neo4j database is rejecting connections, causing all scans to fail during initialization. Memory usage on the instance increased gradually throughout the day until reaching 100%, at which point the instance became unresponsive. Attempts to provision replacement instances have also failed to start. We are actively investigating the root cause of the memory growth.\n\n2. **API database performance**: Attack Paths scans are retrieving findings from the primary read/write database instance instead of the read-only replica. This is causing elevated CPU usage on the Prowler API database cluster, which in turn is delaying dependent tasks (compliance overviews, scan summaries) and increasing the processing queue.\n\n \n\nOur engineering team is actively working on both issues. We will provide an update as soon as we have more information.",
"created_at": "2026-01-22T23:37:19Z",
"display_at": "2026-01-22T23:37:18Z",
"id": "01KFM13JVBKHRE73A2WRVA1066",
"incident_id": "01KFKWT5YZDMBRT8QFFMPCETP2",
"status": "investigating",
"updated_at": "2026-01-23T00:36:46Z"
},
{
"body": "We are currently experiencing an issue affecting all scan types across the platform. Scans are failing to start, which means new security findings are not being generated during this time.\n\nOur team is working to identify the cause. We'll provide details as soon as possible.",
"created_at": "2026-01-22T22:22:16Z",
"display_at": "2026-01-22T22:22:16Z",
"id": "01KFKWT5YZVTKARE5DN553YJ9A",
"incident_id": "01KFKWT5YZDMBRT8QFFMPCETP2",
"status": "investigating",
"updated_at": "2026-01-22T23:51:58Z"
}
],
"name": "Regular and Attack Paths Scans not running",
"page_id": "01JQS32GMND8652REX48S4MWGG",
"resolved_at": "2026-01-26T08:23:07Z",
"status": "resolved",
"updated_at": "2026-03-11T15:46:01Z"
},
{
"created_at": "2025-12-05T09:01:01Z",
"id": "01KBPVWHTG7KDFJNPNR046N82R",
"impact": "critical",
"incident_updates": [
{
"body": "Following continued monitoring and confirmation from our upstream provider, we’ve verified that **prowler.com** has fully recovered and is operating normally again. This incident is now resolved.\n\n\nWe appreciate your patience and understanding.",
"created_at": "2025-12-05T10:37:35Z",
"display_at": "2025-12-05T10:37:35Z",
"id": "01KBQ1DBX9PYDJ3WY45PT9X4B8",
"incident_id": "01KBPVWHTG7KDFJNPNR046N82R",
"status": "resolved",
"updated_at": "2025-12-05T10:37:35Z"
},
{
"body": "The website is back up. We will continue monitoring to ensure full stability.",
"created_at": "2025-12-05T09:17:20Z",
"display_at": "2025-12-05T09:17:20Z",
"id": "01KBPWTDRZ6SE4RH1GVQQWV0ZV",
"incident_id": "01KBPVWHTG7KDFJNPNR046N82R",
"status": "monitoring",
"updated_at": "2025-12-05T09:17:20Z"
},
{
"body": "We are currently experiencing an outage affecting **prowler.com**, which is hosted on Webflow and relies on Cloudflare. Cloudflare appears to be having an active incident and is returning **HTTP 500 Internal Server Error** responses.\n\nWe are monitoring Cloudflare’s status and will provide updates as the situation evolves.\n\nThank you for your patience.",
"created_at": "2025-12-05T09:01:01Z",
"display_at": "2025-12-05T09:01:01Z",
"id": "01KBPVWHTGMNMC2S59K7QC78WZ",
"incident_id": "01KBPVWHTG7KDFJNPNR046N82R",
"status": "monitoring",
"updated_at": "2025-12-05T09:01:01Z"
}
],
"name": "Prowler website is down",
"page_id": "01JQS32GMND8652REX48S4MWGG",
"resolved_at": "2025-12-05T10:37:35Z",
"status": "resolved",
"updated_at": "2026-03-11T15:46:01Z"
},
{
"created_at": "2025-11-27T11:34:10Z",
"id": "01KB2HF7ABA54T2G54NZXFX3QB",
"impact": "major",
"incident_updates": [
{
"body": "All scans are now running without delay. We apologise for the inconvenience.",
"created_at": "2025-11-28T15:38:41Z",
"display_at": "2025-11-28T15:38:41Z",
"id": "01KB5HVN8DVXG7XCE790KSJ9BJ",
"incident_id": "01KB2HF7ABA54T2G54NZXFX3QB",
"status": "resolved",
"updated_at": "2025-11-28T15:38:41Z"
},
{
"body": "Scan queue performance has returned to normal, and all scans are now running without delay. We will continue monitoring the system closely.",
"created_at": "2025-11-28T13:28:27Z",
"display_at": "2025-11-28T13:28:27Z",
"id": "01KB5AD6VFD40C9QVBC0X3NWQ2",
"incident_id": "01KB2HF7ABA54T2G54NZXFX3QB",
"status": "monitoring",
"updated_at": "2025-11-28T13:28:27Z"
},
{
"body": "Since yesterday, we’ve seen noticeable improvements in performance, with scans launching with much lower delay. We’ve deployed an additional fix and are gradually bringing workers back to clear the scan queue.\n\nIn parallel, we’re closely monitoring the service to minimize any further impact.",
"created_at": "2025-11-28T11:18:51Z",
"display_at": "2025-11-28T11:18:51Z",
"id": "01KB52ZX4XBRZQN8QG8VG637ST",
"incident_id": "01KB2HF7ABA54T2G54NZXFX3QB",
"status": "monitoring",
"updated_at": "2025-11-28T11:21:09Z"
},
{
"body": "We identified that scans are running with significant delays due to the issue found. We are currently applying configuration changes and closely monitoring the system to restore performance to expected levels.",
"created_at": "2025-11-27T15:45:18Z",
"display_at": "2025-11-27T15:45:18Z",
"id": "01KB2ZV2ASVM0KVNCA9Z25EQ6P",
"incident_id": "01KB2HF7ABA54T2G54NZXFX3QB",
"status": "monitoring",
"updated_at": "2025-11-27T15:45:18Z"
},
{
"body": "We’ve deployed a fix and are actively monitoring the results.\n\nIn parallel, we’re closely monitoring the service to minimize impact as much as possible.",
"created_at": "2025-11-27T13:56:25Z",
"display_at": "2025-11-27T13:56:25Z",
"id": "01KB2SKPF1YVAA8DN40VN44XX2",
"incident_id": "01KB2HF7ABA54T2G54NZXFX3QB",
"status": "monitoring",
"updated_at": "2025-11-27T13:56:25Z"
},
{
"body": "We identified an issue where ECS tasks launched for scans were not shutting down after completion. While investigating the container logs, we noticed an entry-point log line that normally appears only during container startup.\n\nAs a result, tasks that should have exited cleanly after completing the scan were instead restarted, remaining in a running state indefinitely and causing unnecessary resource consumption. As the task is restarted it keeps listening to the `scans` queue rejecting scan tasks as their assigned one was successfully completed. Therefore, it increases the number of available tasks ready to pick a scan decreasing the possibility of getting the assigned one. This is making scans not to run as the underlying task is not getting the scan that is assigned.\n\nThis was introduced by a new restart policy conflicting with the scan task lifecycle. We are updating the configuration to explicitly disable the restart policy.",
"created_at": "2025-11-27T12:57:22Z",
"display_at": "2025-11-27T12:57:22Z",
"id": "01KB2P7JHR0H1Y5NECZBKD129C",
"incident_id": "01KB2HF7ABA54T2G54NZXFX3QB",
"status": "identified",
"updated_at": "2025-11-27T13:12:25Z"
},
{
"body": "Scans are not being launched in Prowler Cloud. This currently affects **both manual and scheduled scans.**\n\nOur team is working to identify the cause. We'll provide details as soon as possible.\n\n \n\n**Update 2025/11/27**: We identified that scans are running with significant delays. ",
"created_at": "2025-11-27T11:34:10Z",
"display_at": "2025-11-27T11:34:10Z",
"id": "01KB2HF7ABYC5RY8D97JWN2KP3",
"incident_id": "01KB2HF7ABA54T2G54NZXFX3QB",
"status": "investigating",
"updated_at": "2025-11-27T15:46:24Z"
}
],
"name": "Scans running with significant delay",
"page_id": "01JQS32GMND8652REX48S4MWGG",
"resolved_at": "2025-11-28T15:38:41Z",
"status": "resolved",
"updated_at": "2026-03-11T15:46:01Z"
},
{
"created_at": "2025-11-20T09:48:24Z",
"id": "01KAGAMH9KWJCBW7B6DFWZ5FAR",
"impact": "minor",
"incident_updates": [
{
"body": "The Atlassian API is now operating normally. Jira work item creation is functioning as expected.\n\nWe’ve confirmed recovery and all services are back to normal.",
"created_at": "2025-11-20T16:19:55Z",
"display_at": "2025-11-20T16:19:55Z",
"id": "01KAH11DEF49RWTN7K1T6HXMVP",
"incident_id": "01KAGAMH9KWJCBW7B6DFWZ5FAR",
"status": "resolved",
"updated_at": "2025-11-20T16:19:55Z"
},
{
"body": "We are currently seeing inconsistent errors from the Atlassian API. In addition, the SSL/TLS certificate for `\u003chttps://home.atlassian.com.atlassian.net/\u003e` appears to be expired, causing validation failures.\n\nAs a result, some users may experience issues when creating Jira work items during this period.\n\nWe will continue to monitor the situation and provide updates as Atlassian resolves the underlying issue.",
"created_at": "2025-11-20T09:48:24Z",
"display_at": "2025-11-20T09:48:24Z",
"id": "01KAGAMH9KMGQTRYDR143H03V8",
"incident_id": "01KAGAMH9KWJCBW7B6DFWZ5FAR",
"status": "monitoring",
"updated_at": "2025-11-20T14:07:51Z"
}
],
"name": "Atlassian Jira API Expired Certificate",
"page_id": "01JQS32GMND8652REX48S4MWGG",
"resolved_at": "2025-11-20T16:19:55Z",
"status": "resolved",
"updated_at": "2026-03-11T15:46:01Z"
},
{
"created_at": "2025-10-20T07:40:48Z",
"id": "01K8090KKAD5B01VQGMQW456RH",
"impact": "none",
"incident_updates": [
{
"body": "The incident has been **resolved by AWS**. All **Prowler Cloud scans** are now operating normally and generating findings as expected.",
"created_at": "2025-10-21T06:53:09Z",
"display_at": "2025-10-21T06:53:09Z",
"id": "01K82RP20EE64P7YBQW0BDA0FB",
"incident_id": "01K8090KKAD5B01VQGMQW456RH",
"status": "resolved",
"updated_at": "2025-10-21T06:53:09Z"
},
{
"body": "There is an ongoing incident in **AWS** affecting mainly **North Virginia** (us-east-1) region. As this is one of AWS' primary regions, **some impact may extend to other regions**.\n\nThis is affecting our ability to reach AWS APIs. As a result, some scans may return incomplete data, leading to **gaps in security findings**. \n\n \n\nWe're actively monitoring to minimize the impact.",
"created_at": "2025-10-20T07:40:48Z",
"display_at": "2025-10-20T07:40:48Z",
"id": "01K8090KKAY8BZTEV9TDKNF1S3",
"incident_id": "01K8090KKAD5B01VQGMQW456RH",
"status": "monitoring",
"updated_at": "2025-10-20T07:44:20Z"
}
],
"name": "Incident in AWS North Virginia (us-east-1)",
"page_id": "01JQS32GMND8652REX48S4MWGG",
"resolved_at": "2025-10-21T06:53:09Z",
"status": "resolved",
"updated_at": "2026-03-11T15:46:01Z"
},
{
"created_at": "2025-09-23T15:20:22Z",
"id": "01K5VJJPGNWMB6W5ZQ5QFETXHE",
"impact": "minor",
"incident_updates": [
{
"body": "We’ve resolved the Task Runner issues affecting Prowler Cloud. All systems are now operating normally, and all tasks are running as expected. We’ll continue to monitor the platform to ensure stability. Thank you for your patience throughout this incident.",
"created_at": "2025-09-25T15:18:48Z",
"display_at": "2025-09-25T15:18:47Z",
"id": "01K60Q97VTP6J97A3GSHX3QFBK",
"incident_id": "01K5VJJPGNWMB6W5ZQ5QFETXHE",
"status": "resolved",
"updated_at": "2025-09-25T15:18:48Z"
},
{
"body": "We're still monitoring the service closely. Both API and Task Runner performance is within thresholds. Additionally, we’ve identified several improvements that we plan to implement soon to further enhance stability.",
"created_at": "2025-09-25T07:14:45Z",
"display_at": "2025-09-25T07:14:45Z",
"id": "01K5ZVJXWN6F1DS5QAPNXYR12T",
"incident_id": "01K5VJJPGNWMB6W5ZQ5QFETXHE",
"status": "monitoring",
"updated_at": "2025-09-25T07:14:45Z"
},
{
"body": "We have deployed a fix by introducing a new queue to ensure that scan summaries and compliance overviews are not blocked in between. The service is stable, but we continue to monitor closely. Our team is also investigating the root cause of the increase in pending tasks that led to the performance degradation.",
"created_at": "2025-09-24T16:35:59Z",
"display_at": "2025-09-24T16:35:59Z",
"id": "01K5Y99W1995P623BPH53R24KX",
"incident_id": "01K5VJJPGNWMB6W5ZQ5QFETXHE",
"status": "investigating",
"updated_at": "2025-09-24T16:35:59Z"
},
{
"body": "We’re closely monitoring the service and working to identify what caused the issue.",
"created_at": "2025-09-24T11:08:57Z",
"display_at": "2025-09-24T11:08:57Z",
"id": "01K5XPK1E61BS0GSJAHSJ68PXE",
"incident_id": "01K5VJJPGNWMB6W5ZQ5QFETXHE",
"status": "investigating",
"updated_at": "2025-09-24T11:08:57Z"
},
{
"body": "We are still investigating the causes of the pending tasks spike in the queue. This is still causing some performance degradation and delays on scan and compliance overviews. We appreciate your patience and will provide updates as soon as more information becomes available.",
"created_at": "2025-09-24T06:55:07Z",
"display_at": "2025-09-24T06:55:07Z",
"id": "01K5X828TXBAFA48K43NJK118V",
"incident_id": "01K5VJJPGNWMB6W5ZQ5QFETXHE",
"status": "investigating",
"updated_at": "2025-09-24T06:55:07Z"
},
{
"body": "Prowler Cloud API is experiencing elevated latency due to a backlog of pending tasks from increased scan volume. This currently affects **scan summaries, reports, and compliance overview**s. Therefore users may notice **delayed results**. \n\nOur team is working to reduce the queue and restore normal performance.",
"created_at": "2025-09-23T15:20:22Z",
"display_at": "2025-09-23T11:28:00Z",
"id": "01K5VJJPGNEDFPCHYDYND6PQGW",
"incident_id": "01K5VJJPGNWMB6W5ZQ5QFETXHE",
"status": "investigating",
"updated_at": "2025-09-23T15:25:54Z"
}
],
"name": "Prowler Cloud API Increasing Pending Tasks Queue",
"page_id": "01JQS32GMND8652REX48S4MWGG",
"resolved_at": "2025-09-25T15:18:47Z",
"status": "resolved",
"updated_at": "2026-03-11T15:46:01Z"
},
{
"created_at": "2025-06-06T13:12:58Z",
"id": "01JX2NZ2F0SA9CVF516RGS8WMA",
"impact": "major",
"incident_updates": [
{
"body": "We’ve resolved the database connection issues affecting Prowler Cloud. All systems are now operating normally, and scans are running as expected.\n\nWe’ll continue to monitor the platform to ensure stability. Thank you for your patience throughout this incident.",
"created_at": "2025-06-11T12:03:43Z",
"display_at": "2025-06-11T12:03:43Z",
"id": "01JXFDZW06YZ13ECNCCQYZ6ZYG",
"incident_id": "01JX2NZ2F0SA9CVF516RGS8WMA",
"status": "resolved",
"updated_at": "2025-06-11T12:03:43Z"
},
{
"body": "The deployed fix is working as intended. We continue to monitor the service closely.\n\n ",
"created_at": "2025-06-11T07:08:03Z",
"display_at": "2025-06-11T07:08:03Z",
"id": "01JXEX2FEGAWBXZMH8ZTD021AF",
"incident_id": "01JX2NZ2F0SA9CVF516RGS8WMA",
"status": "monitoring",
"updated_at": "2025-06-11T07:08:03Z"
},
{
"body": "We’ve deployed a fix and are actively monitoring the results. Additionally, we’ve identified an improvement that we plan to implement soon to further enhance stability.",
"created_at": "2025-06-10T15:37:42Z",
"display_at": "2025-06-10T15:37:42Z",
"id": "01JXD7TZ3X563MDN096M48Z158",
"incident_id": "01JX2NZ2F0SA9CVF516RGS8WMA",
"status": "monitoring",
"updated_at": "2025-06-10T15:37:42Z"
},
{
"body": "We’ve identified the cause of the issue and are actively working on a fix. In parallel, we’re closely monitoring the service to minimize impact as much as possible.",
"created_at": "2025-06-10T12:52:41Z",
"display_at": "2025-06-10T12:52:41Z",
"id": "01JXCYCT9A6GAABP602G6V2Z3G",
"incident_id": "01JX2NZ2F0SA9CVF516RGS8WMA",
"status": "identified",
"updated_at": "2025-06-10T12:52:41Z"
},
{
"body": "We are still investigating the database connection issues and working to identify the cause. We appreciate your patience and will provide updates as soon as more information becomes available.",
"created_at": "2025-06-09T06:20:15Z",
"display_at": "2025-06-09T06:20:15Z",
"id": "01JX9NHGE1R550ZMYXYTNTBMZH",
"incident_id": "01JX2NZ2F0SA9CVF516RGS8WMA",
"status": "investigating",
"updated_at": "2025-06-09T06:20:15Z"
},
{
"body": "We are currently investigating multiple database connection issues affecting both the Task Runner and the API, which are causing scan and request failures. Our team is actively working to identify the root cause and assess the impact on our services. We appreciate your patience and will share updates as soon as more information becomes available.",
"created_at": "2025-06-06T13:12:58Z",
"display_at": "2025-06-06T13:12:58Z",
"id": "01JX2NZ2F0J4CDS2GP0KSKWTZB",
"incident_id": "01JX2NZ2F0SA9CVF516RGS8WMA",
"status": "investigating",
"updated_at": "2025-06-06T13:12:58Z"
}
],
"name": "Prowler Cloud API and Task Runner Database Connection Issues",
"page_id": "01JQS32GMND8652REX48S4MWGG",
"resolved_at": "2025-06-11T12:03:43Z",
"status": "resolved",
"updated_at": "2026-03-11T15:46:01Z"
},
{
"created_at": "2025-05-20T15:18:42Z",
"id": "01JVQ4D2DRRCDCVWGZ9Z5VMW9J",
"impact": "major",
"incident_updates": [
{
"body": "We’ve resolved the performance degradation issues affecting Prowler Cloud. All systems are now operating normally, and scans are running as expected. We’ll continue to monitor the platform to ensure stability. Thank you for your patience throughout this incident.",
"created_at": "2025-05-22T16:01:39Z",
"display_at": "2025-05-22T16:01:39Z",
"id": "01JVWBN5GBN45Z6BXSCRYJA6BS",
"incident_id": "01JVQ4D2DRRCDCVWGZ9Z5VMW9J",
"status": "resolved",
"updated_at": "2025-05-22T16:01:39Z"
},
{
"body": "The fixes have been successfully deployed, and performance is now stabilizing within our expected thresholds. We’ll continue to monitor the system to ensure consistent service.",
"created_at": "2025-05-22T12:11:11Z",
"display_at": "2025-05-22T12:11:11Z",
"id": "01JVVYF4VZTFZ6AM4SY0291HJ3",
"incident_id": "01JVQ4D2DRRCDCVWGZ9Z5VMW9J",
"status": "monitoring",
"updated_at": "2025-05-22T12:11:11Z"
},
{
"body": "We’re continuing to apply new database indexes to help mitigate the ongoing performance degradation. Scan operations—both scheduled and on-demand—are still impacted during this process. We appreciate your patience as we work to restore full performance.",
"created_at": "2025-05-22T11:25:44Z",
"display_at": "2025-05-22T11:25:44Z",
"id": "01JVVVVY6E93TNTHC5ZCS8C1PX",
"incident_id": "01JVQ4D2DRRCDCVWGZ9Z5VMW9J",
"status": "identified",
"updated_at": "2025-05-22T11:25:44Z"
},
{
"body": "We’ve completed the deployment and are now actively monitoring Prowler Cloud API latencies to ensure performance is stabilizing as expected.",
"created_at": "2025-05-21T20:32:46Z",
"display_at": "2025-05-21T20:32:46Z",
"id": "01JVT8RW7M95BCM905WYEA3WYY",
"incident_id": "01JVQ4D2DRRCDCVWGZ9Z5VMW9J",
"status": "monitoring",
"updated_at": "2025-05-21T20:32:46Z"
},
{
"body": "We are still in the process of deploying changes aimed at mitigating the performance degradation. During the deployment, we encountered some issues and are actively working to resolve them to ensure the improvements are delivered successfully.",
"created_at": "2025-05-21T16:15:59Z",
"display_at": "2025-05-21T16:15:59Z",
"id": "01JVST2NZ3Q1815H92M9FB7ZKM",
"incident_id": "01JVQ4D2DRRCDCVWGZ9Z5VMW9J",
"status": "identified",
"updated_at": "2025-05-21T16:15:59Z"
},
{
"body": "We’re currently deploying a new version that includes an additional database index to help address part of the ongoing performance degradation.",
"created_at": "2025-05-21T11:52:09Z",
"display_at": "2025-05-21T11:52:09Z",
"id": "01JVSAZKB4CA8Z2FYHRXDHTF42",
"incident_id": "01JVQ4D2DRRCDCVWGZ9Z5VMW9J",
"status": "identified",
"updated_at": "2025-05-21T11:52:09Z"
},
{
"body": "We’ve identified two separate issues affecting our database and are actively working on a fix. In parallel, we’re closely monitoring the service to minimize impact as much as possible.",
"created_at": "2025-05-21T08:50:31Z",
"display_at": "2025-05-21T08:50:31Z",
"id": "01JVS0K0RJTAJV36H26AGWWN25",
"incident_id": "01JVQ4D2DRRCDCVWGZ9Z5VMW9J",
"status": "identified",
"updated_at": "2025-05-21T08:50:31Z"
},
{
"body": "We’re still investigating a database issue that is also affecting to connectivity and is causing some tasks to fail. This is affecting both scheduled and on-demand scans.",
"created_at": "2025-05-21T07:09:04Z",
"display_at": "2025-05-21T07:09:04Z",
"id": "01JVRTS7Y4S0ARWPE2X949B3YX",
"incident_id": "01JVQ4D2DRRCDCVWGZ9Z5VMW9J",
"status": "investigating",
"updated_at": "2025-05-21T07:09:04Z"
},
{
"body": "We’re currently experiencing performance degradation in the Prowler Cloud API. The service remains available, but some requests may be slower than expected. Our team is investigating potential issues in one of the databases and working to restore optimal performance.",
"created_at": "2025-05-21T06:28:02Z",
"display_at": "2025-05-21T06:28:02Z",
"id": "01JVRRE438HQSDCA06YDAK8AMX",
"incident_id": "01JVQ4D2DRRCDCVWGZ9Z5VMW9J",
"status": "investigating",
"updated_at": "2025-05-21T06:28:02Z"
},
{
"body": "We’ve deployed a fix and are actively monitoring the results. Additionally, we’ve identified an improvement that we plan to implement soon to further enhance stability.",
"created_at": "2025-05-20T16:18:42Z",
"display_at": "2025-05-20T16:18:42Z",
"id": "01JVQ7TY06E28H27SAK2FK876R",
"incident_id": "01JVQ4D2DRRCDCVWGZ9Z5VMW9J",
"status": "monitoring",
"updated_at": "2025-05-20T16:18:42Z"
},
{
"body": "We’ve identified the cause of the issue and are actively working on a fix. In the meantime, we’re continuing to monitor the performance degradation, as the impact appears to be limited to a subset of tenants.",
"created_at": "2025-05-20T15:51:38Z",
"display_at": "2025-05-20T15:51:38Z",
"id": "01JVQ69C81MNRYMVX2Q3TC78XE",
"incident_id": "01JVQ4D2DRRCDCVWGZ9Z5VMW9J",
"status": "identified",
"updated_at": "2025-05-20T15:51:38Z"
},
{
"body": "We are currently investigating high latencies in Prowler Cloud API. Our team is actively working to identify the cause and assess the impact on our services. We appreciate your patience and will provide updates as soon as more information becomes available.",
"created_at": "2025-05-20T15:18:42Z",
"display_at": "2025-05-20T15:18:42Z",
"id": "01JVQ4D2DRANBXPWECBBT92W4Z",
"incident_id": "01JVQ4D2DRRCDCVWGZ9Z5VMW9J",
"status": "investigating",
"updated_at": "2025-05-20T15:18:42Z"
}
],
"name": "Prowler Cloud API is currently experiencing high latencies",
"page_id": "01JQS32GMND8652REX48S4MWGG",
"resolved_at": "2025-05-22T16:01:39Z",
"status": "resolved",
"updated_at": "2026-03-11T15:46:01Z"
}
],
"page": {
"id": "01JQS32GMND8652REX48S4MWGG",
"name": "Prowler",
"updated_at": "2026-07-28T15:57:14Z",
"url": "https://status.prowler.com/"
}
}