Update - We are actively monitoring AWS updates. As of this time, AWS is still working on full recovery of the second AZ (me-central-1c) and is continuing to throttle S3 and other dependent services.
For customers willing to move their data permanently out of UAE and want to get their services operational in another region, please reach out to our support.
Mar 17, 2026 - 17:02 UTC
For customers willing to move their data permanently out of UAE and want to get their services operational in another region, please reach out to our support.
Mar 17, 2026 - 17:02 UTC
Update - We are actively monitoring AWS updates. As of this time, AWS is still working on recovering the second AZ to full operation and is continuing to throttle S3 and other dependent services.
For customers willing to move their data out of UAE and want to get their services operational in another region, please reach out to our support.
Mar 10, 2026 - 00:01 UTC
For customers willing to move their data out of UAE and want to get their services operational in another region, please reach out to our support.
Mar 10, 2026 - 00:01 UTC
Update - Update from Securiti:
Connectivity to our Consent backend database in the UAE has been restored. Customers who wish to back up their consent data to a region outside the UAE are encouraged to contact our support team.
Update from AWS:
We continue to prioritize recovery efforts in the ME-CENTRAL-1 Region for Availability Zone mec1-az3 and expect it to be available before Availability Zone mec1-az2.
DynamoDB partition recovery is a crucial step and we are seeing our automated and manual efforts bring more internal systems online. We are now observing recovery for Lambda invocations and SQS operations. We have also made progress recovering specific DynamoDB partitions, which will enable foundational services to provision EC2 capacity. EC2 instance launches will remain intentionally throttled as we restore capacity in a controlled manner. This is required to enable both customers and foundational AWS services to recover while protecting the stability of the service.
For Amazon S3, we have observed steady availability for PUT, GET and LIST actions for newly-written objects. We continue to work on reducing GET error rates for objects written prior to the event, but full recovery remains dependent on restoring the affected infrastructure.
Our guidance for customers with workloads running in the Middle East remains unchanged. We continue to recommend migrating your workloads, traffic and recovering your operations at alternate Region(s) as appropriate for your specific latency and data residency requirements. We recognize that using AWS Services (such as AWS Backup for EC2 Instances, EBS Volumes, RDS) to perform these migrations is currently impaired. As a result, we are intentionally prioritizing recovering these services and operations.
Mar 06, 2026 - 04:56 UTC
Connectivity to our Consent backend database in the UAE has been restored. Customers who wish to back up their consent data to a region outside the UAE are encouraged to contact our support team.
Update from AWS:
We continue to prioritize recovery efforts in the ME-CENTRAL-1 Region for Availability Zone mec1-az3 and expect it to be available before Availability Zone mec1-az2.
DynamoDB partition recovery is a crucial step and we are seeing our automated and manual efforts bring more internal systems online. We are now observing recovery for Lambda invocations and SQS operations. We have also made progress recovering specific DynamoDB partitions, which will enable foundational services to provision EC2 capacity. EC2 instance launches will remain intentionally throttled as we restore capacity in a controlled manner. This is required to enable both customers and foundational AWS services to recover while protecting the stability of the service.
For Amazon S3, we have observed steady availability for PUT, GET and LIST actions for newly-written objects. We continue to work on reducing GET error rates for objects written prior to the event, but full recovery remains dependent on restoring the affected infrastructure.
Our guidance for customers with workloads running in the Middle East remains unchanged. We continue to recommend migrating your workloads, traffic and recovering your operations at alternate Region(s) as appropriate for your specific latency and data residency requirements. We recognize that using AWS Services (such as AWS Backup for EC2 Instances, EBS Volumes, RDS) to perform these migrations is currently impaired. As a result, we are intentionally prioritizing recovering these services and operations.
Mar 06, 2026 - 04:56 UTC
Update - We are continuing to monitor the AWS updates in the region.
AWS update as of [March 4 10:09 AM PST]
We continue to prioritize recovery efforts in the ME-CENTRAL-1 Region for Availability Zone mec1-az3 and expect it to be available before Availability Zone mec1-az2.
To help preserve data that was saved prior to the event, we have taken proactive steps to suspend automated lifecycle expiration activities where possible. For example, for EBS Snapshots, we have suspended automated deletion and de-registration of snapshots and AMIs managed by lifecycle policies in the affected region. Likewise for AWS Backup, we have temporarily suspended the automatic deletion of backups per retention policies.
For Amazon S3, we have observed steady availability for PUT, GET and LIST actions for newly-written objects. We continue to work on reducing GET error rates for objects written prior to the event, but full recovery remains dependent on restoring the affected infrastructure.
DynamoDB continues to make progress on table partition recovery for foundational services. EC2 instance launches will remain intentionally throttled as we restore capacity in a controlled manner designed to enable both customers and foundational AWS services to recover as quickly as possible while protecting the stability of the service.
Our guidance for customers with workloads running in the Middle East remains unchanged. We continue to recommend migrating your workloads, traffic and recovering your operations at alternate Region(s) as appropriate for your specific latency and data residency requirements. We recognize that using AWS Services (such as AWS Backup for EC2 Instances, EBS Volumes, RDS) to perform these migrations is currently impaired. As a result, we are intentionally prioritizing recovering these services and operations.
Mar 04, 2026 - 22:45 UTC
AWS update as of [March 4 10:09 AM PST]
We continue to prioritize recovery efforts in the ME-CENTRAL-1 Region for Availability Zone mec1-az3 and expect it to be available before Availability Zone mec1-az2.
To help preserve data that was saved prior to the event, we have taken proactive steps to suspend automated lifecycle expiration activities where possible. For example, for EBS Snapshots, we have suspended automated deletion and de-registration of snapshots and AMIs managed by lifecycle policies in the affected region. Likewise for AWS Backup, we have temporarily suspended the automatic deletion of backups per retention policies.
For Amazon S3, we have observed steady availability for PUT, GET and LIST actions for newly-written objects. We continue to work on reducing GET error rates for objects written prior to the event, but full recovery remains dependent on restoring the affected infrastructure.
DynamoDB continues to make progress on table partition recovery for foundational services. EC2 instance launches will remain intentionally throttled as we restore capacity in a controlled manner designed to enable both customers and foundational AWS services to recover as quickly as possible while protecting the stability of the service.
Our guidance for customers with workloads running in the Middle East remains unchanged. We continue to recommend migrating your workloads, traffic and recovering your operations at alternate Region(s) as appropriate for your specific latency and data residency requirements. We recognize that using AWS Services (such as AWS Backup for EC2 Instances, EBS Volumes, RDS) to perform these migrations is currently impaired. As a result, we are intentionally prioritizing recovering these services and operations.
Mar 04, 2026 - 22:45 UTC
Update - Further update from AWS:
[08:14 AM PST] We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1). We continue to make progress on recovery efforts across multiple workstreams.
For Amazon S3, we are seeing continued improvement in PUT and LIST availability. Newly written objects are now able to be successfully retrieved, and we continue to work on reducing GET error rates for objects written prior to the event. Full recovery of GET operations for pre-existing data remains dependent on restoring the affected infrastructure. For Amazon DynamoDB, error rates remain elevated and our teams continue to focus on recovery; we expect to see improvement over the coming hours. As these foundational services recover, dependent services — including AWS Lambda, Amazon Kinesis, Amazon CloudWatch, and Amazon RDS — will follow. Amazon EC2 instance launches remain throttled in the ME-CENTRAL-1 Region and will be relaxed as foundational service recovery and capacity allow. The AWS Management Console is operational, though customers may continue to experience errors on certain pages as underlying services work through their recovery.
Mar 03, 2026 - 23:40 UTC
[08:14 AM PST] We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1). We continue to make progress on recovery efforts across multiple workstreams.
For Amazon S3, we are seeing continued improvement in PUT and LIST availability. Newly written objects are now able to be successfully retrieved, and we continue to work on reducing GET error rates for objects written prior to the event. Full recovery of GET operations for pre-existing data remains dependent on restoring the affected infrastructure. For Amazon DynamoDB, error rates remain elevated and our teams continue to focus on recovery; we expect to see improvement over the coming hours. As these foundational services recover, dependent services — including AWS Lambda, Amazon Kinesis, Amazon CloudWatch, and Amazon RDS — will follow. Amazon EC2 instance launches remain throttled in the ME-CENTRAL-1 Region and will be relaxed as foundational service recovery and capacity allow. The AWS Management Console is operational, though customers may continue to experience errors on certain pages as underlying services work through their recovery.
Mar 03, 2026 - 23:40 UTC
Update - This is the update further from AWS:
[04:19 PM PST] We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1) and the AWS Middle East (Bahrain) Region (ME-SOUTH-1). Due to the ongoing conflict in the Middle East, both affected regions have experienced physical impacts to infrastructure as a result of drone strikes. In the UAE, two of our facilities were directly struck, while in Bahrain, a drone strike in close proximity to one of our facilities caused physical impacts to our infrastructure. These strikes have caused structural damage, disrupted power delivery to our infrastructure, and in some cases required fire suppression activities that resulted in additional water damage. We are working closely with local authorities and prioritizing the safety of our personnel throughout our recovery efforts.
In the ME-CENTRAL-1 (UAE) Region, two of our three Availability Zones (mec1-az2 and mec1-az3) remain significantly impaired. The third Availability Zone (mec1-az1) continues to operate normally, though some services have experienced indirect impact due to dependencies on the affected zones. In the ME-SOUTH-1 (Bahrain) Region, one facility has been impacted. Across both regions, customers are experiencing elevated error rates and degraded availability for services including Amazon EC2, Amazon S3, Amazon DynamoDB, AWS Lambda, Amazon Kinesis, Amazon CloudWatch, Amazon RDS, and the AWS Management Console and CLI. We are working to restore full service availability as quickly as possible, though we expect recovery to be prolonged given the nature of the physical damage involved.
In parallel with efforts to restore the physical infrastructure at the affected sites, we are pursuing multiple software-based recovery paths that do not depend on the underlying facilities being fully brought back online. For Amazon S3 and Amazon DynamoDB, we are actively working to restore data access and service availability through software mitigations, including deploying updates to enable S3 to operate within the current infrastructure constraints and remediating impaired DynamoDB tables to restore read and write availability for dependent services. Our focus on restoring these foundational services is deliberate, as recovery of Amazon S3 and Amazon DynamoDB will in turn enable a broad range of dependent AWS services to recover. For other affected service APIs, we are deploying targeted software updates to reduce error rates and restore functionality where possible, independent of the physical recovery timeline. We are also working to restore access to the AWS Management Console and CLI through network-level changes that route traffic away from the affected infrastructure. While these software-based mitigations can address many of the service-level impacts, some recovery actions are constrained by the physical state of the affected facilities — meaning that full restoration of certain services will require the underlying infrastructure to be repaired and brought back online. Across all services, our teams are working in parallel on both the physical restoration of the affected facilities and these software-based mitigations, with the goal of restoring as much customer access as possible as quickly as possible, even ahead of full infrastructure recovery. In addition, we are prioritizing the restoration of services and tools that enable customers to back up and migrate their data and applications out of the affected regions.
Mar 03, 2026 - 00:41 UTC
[04:19 PM PST] We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1) and the AWS Middle East (Bahrain) Region (ME-SOUTH-1). Due to the ongoing conflict in the Middle East, both affected regions have experienced physical impacts to infrastructure as a result of drone strikes. In the UAE, two of our facilities were directly struck, while in Bahrain, a drone strike in close proximity to one of our facilities caused physical impacts to our infrastructure. These strikes have caused structural damage, disrupted power delivery to our infrastructure, and in some cases required fire suppression activities that resulted in additional water damage. We are working closely with local authorities and prioritizing the safety of our personnel throughout our recovery efforts.
In the ME-CENTRAL-1 (UAE) Region, two of our three Availability Zones (mec1-az2 and mec1-az3) remain significantly impaired. The third Availability Zone (mec1-az1) continues to operate normally, though some services have experienced indirect impact due to dependencies on the affected zones. In the ME-SOUTH-1 (Bahrain) Region, one facility has been impacted. Across both regions, customers are experiencing elevated error rates and degraded availability for services including Amazon EC2, Amazon S3, Amazon DynamoDB, AWS Lambda, Amazon Kinesis, Amazon CloudWatch, Amazon RDS, and the AWS Management Console and CLI. We are working to restore full service availability as quickly as possible, though we expect recovery to be prolonged given the nature of the physical damage involved.
In parallel with efforts to restore the physical infrastructure at the affected sites, we are pursuing multiple software-based recovery paths that do not depend on the underlying facilities being fully brought back online. For Amazon S3 and Amazon DynamoDB, we are actively working to restore data access and service availability through software mitigations, including deploying updates to enable S3 to operate within the current infrastructure constraints and remediating impaired DynamoDB tables to restore read and write availability for dependent services. Our focus on restoring these foundational services is deliberate, as recovery of Amazon S3 and Amazon DynamoDB will in turn enable a broad range of dependent AWS services to recover. For other affected service APIs, we are deploying targeted software updates to reduce error rates and restore functionality where possible, independent of the physical recovery timeline. We are also working to restore access to the AWS Management Console and CLI through network-level changes that route traffic away from the affected infrastructure. While these software-based mitigations can address many of the service-level impacts, some recovery actions are constrained by the physical state of the affected facilities — meaning that full restoration of certain services will require the underlying infrastructure to be repaired and brought back online. Across all services, our teams are working in parallel on both the physical restoration of the affected facilities and these software-based mitigations, with the goal of restoring as much customer access as possible as quickly as possible, even ahead of full infrastructure recovery. In addition, we are prioritizing the restoration of services and tools that enable customers to back up and migrate their data and applications out of the affected regions.
Mar 03, 2026 - 00:41 UTC
Update - Due to escalating tensions in the Middle East, AWS is experiencing a significant regional outage affecting UAE. What began as a single AZ disruption yesterday morning has expanded overnight to multiple AZs, with impact now extending to Bahrain as well. As a result, our services in UAE are currently down. We are actively monitoring the AWS outage and will restore our services as soon as AWS infrastructure recovers.
Mar 02, 2026 - 14:44 UTC
Mar 02, 2026 - 14:44 UTC
Monitoring - We are currently experiencing service disruption due to a confirmed infrastructure issue in the AWS Middle East Region(UAE).
Users may face errors, login issues, or temporary unavailability. We are actively monitoring the situation and working on mitigation while recovery is underway.
Due to escalating tensions in the Middle East, AWS is experiencing a significant regional outage affecting UAE. What began as a single AZ disruption yesterday morning has expanded overnight to multiple AZs, with impact now extending to Bahrain as well. As a result, our services in UAE are currently down. We are actively monitoring the AWS outage and will restore our services as soon as AWS infrastructure recovers.
Mar 02, 2026 - 10:11 UTC
Users may face errors, login issues, or temporary unavailability. We are actively monitoring the situation and working on mitigation while recovery is underway.
Due to escalating tensions in the Middle East, AWS is experiencing a significant regional outage affecting UAE. What began as a single AZ disruption yesterday morning has expanded overnight to multiple AZs, with impact now extending to Bahrain as well. As a result, our services in UAE are currently down. We are actively monitoring the AWS outage and will restore our services as soon as AWS infrastructure recovers.
Mar 02, 2026 - 10:11 UTC
About This Site
Welcome to the status page of Securiti's App5 cloud. Please click on "subscribe to updates" button to get notifications about upcoming maintenances, incidents or changes to our sub-processors.
Data Intelligence & Protection
Major Outage
Data Controls Cloud
Major Outage
Data Intelligence
Major Outage
Data Access Intelligence
Major Outage
Data Access Governance
Major Outage
Data Security Posture Management
Major Outage
Data Catalog
Major Outage
Privacy Ops
Major Outage
Privacy OpsCenter
Major Outage
Consent Management
Major Outage
Assessments
Major Outage
Data Mapping Automation
Major Outage
Data Subject Portal
Major Outage
Data Subject Requests
Major Outage
Data Breach Management
Major Outage
Privacy Notices
Major Outage
Privacy Center
Major Outage
Self Service Portal
Major Outage
Platform
Major Outage
Workflow Orchestration
Major Outage
Policy Engine
Major Outage
Services
Major Outage
Management Portal
Operational
Management API
Major Outage
Reporting Service
Major Outage
Pod Management Service
Major Outage
Consent Recording Service
Major Outage
Privacy Central Portal
Major Outage
Privacy Central API
Major Outage
Background Workers
Major Outage
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
Maintenance: Release 1.144 Upgrade Apr 16, 2026 18:00-22:00 UTC
Securiti will be upgraded to Release 1.144. This is an in-service upgrade and is designed to not cause any disruption. Once the upgrade is complete, please log into the portal and navigate to Knowledge Center -> Release Notes for more information about the release content. Please note that pod updates are made available a day later.
Posted on Feb 23, 2026 - 19:49 UTC
Posted on Feb 23, 2026 - 19:49 UTC
Maintenance: Release 1.145 Upgrade May 7, 2026 18:00-22:00 UTC
Securiti will be upgraded to Release 1.145. This is an in-service upgrade and is designed to not cause any disruption. Once the upgrade is complete, please log into the portal and navigate to Knowledge Center -> Release Notes for more information about the release content. Please note that pod updates are made available a day later.
Posted on Mar 21, 2026 - 06:32 UTC
Posted on Mar 21, 2026 - 06:32 UTC
Maintenance: Release 1.146 Upgrade May 28, 2026 18:00-22:00 UTC
Securiti will be upgraded to Release 1.146. This is an in-service upgrade and is designed to not cause any disruption. Once the upgrade is complete, please log into the portal and navigate to Knowledge Center -> Release Notes for more information about the release content. Please note that pod updates are made available a day later.
Posted on Mar 21, 2026 - 06:34 UTC
Posted on Mar 21, 2026 - 06:34 UTC