Services fully restored

Dr. Pal is now fully operational. All core services are back online and functioning normally. Historical attachments and logos are still undergoing recovery as we work with AWS ME during their restoration of facilities. New uploads and all other features are fully functional.

Dr. Pal is now operational in read-only mode. We have fully migrated away from Middle East servers. The web app is accessible and all data is available. Some features remain impacted: historical attachments are partially available with recovery in progress (AWS ME is still down and we are waiting on their recovery for gradual data migration), logos are not showing yet, and email/WhatsApp notifications are not active. We continue working to restore full functionality.

We were able to fully recover our database and stabilize it. We are still working on restoring all our services, but we expect a partial restoration soon.

We have recovered our database, but our service provider is having technical difficulties stabilizing it. We are working on restoring the database through different means for a quicker resolution and to get back online sooner. Thank you for your patience.

We were able to recover our database and migrate it to a stable region. The database is still stabilizing and we are actively working on getting our services back online, without waiting for AWS to recover. Our database provider is also facing unusual loads due to the issues happening in the Middle East, and we are working closely with them to complete the migration process as fast as possible. We are still expecting hours of work before we are fully back online. Thank you for your patience as we work tirelessly to restore our services.

AWS reported that the overall state of the affected region remains largely unchanged. Some services are seeing partial improvement but most remain disrupted. AWS continues to strongly recommend that customers migrate workloads to alternate regions — which is exactly what we have been doing.

We are actively working on migrating our data into a stable region. We are seeing some positive signs, but we are still not out of the woods yet. We will send an update as soon as we have one.

AWS is still not functional. We have been working with our database partners since the start of the outage to migrate Dr. Pal to a different region, but the process is proving complex and is taking longer than we'd like. We are actively working on it and will update this page as soon as there is meaningful progress.

AWS reported small steps forward on restoring core services behind the scenes. These are not yet visible to users but are necessary before broader recovery can begin. Full restoration is still estimated at least a day away.

AWS officially confirmed that facilities in the UAE and Bahrain were physically damaged by drone strikes as part of the ongoing conflict in the Middle East. The damage includes structural damage, power disruption, and water damage from fire suppression. Two out of three data center zones in the UAE remain completely impaired, and the third — while operational — has limited capacity and is not fully accessible, making recovery efforts more complex than a simple failover. AWS is pursuing both physical repairs and software-based workarounds to restore services, but expects recovery to be prolonged.

AWS has partially restored some management tools, but core services and power are still being recovered. There is no updated timeline — full restoration is still expected to take at least a day. We continue working on alternate solutions to bring Dr. Pal back sooner.

AWS confirmed that recovery efforts are continuing and reiterated that it will take at least a full day. All services remain unavailable. In the meantime, we are actively working on finding alternate solutions to move Dr. Pal away from the affected region and get things back up and running sooner.

AWS confirmed that the affected infrastructure requires physical repairs before services can be restored. Recovery is expected to take at least a full day. Services remain unavailable and we are actively exploring all options to restore Dr. Pal as quickly as possible.

AWS confirmed that multiple core services — including file storage, management tools, and databases — are still not working. Recovery is actively underway and our team is closely monitoring every step.

AWS reported a power issue affecting large parts of their infrastructure in the region that hosts Dr. Pal. Most services are currently unavailable, and launching new resources is not possible. Full recovery is expected to take many hours.

We detected widespread failures across Dr. Pal systems and initiated incident response and mitigations.