Previous incidents

Most AWS services on us-east-1 have recovered and our services are now operational again.

On September 10th, D4H experienced a service degradation and intermittent downtime on Operations Center between 11:23 UTC and 16:49 UTC. Our root cause analysis showed that high CPU from an automatically updated third-party software component caused the degradation.

We have already taken preventative measures to ensure a similar issue does not happen in the future and confirm that all systems are operating normally.

Please let us know at help@d4h.com if you need any assistance and we wil...

Operations Center recovered.

We'd like to inform you that the issue was caused by an error in a code change migrating part of the equipment update view to our new API. This affected select users with updating equipment information.

The issue was first reported to us on August 4 at 8:33 AM (EST), and our team resolved it promptly the same day around 8:36 PM (EST).

Please note that this error was limited strictly to the equipment update page where all other features and products remained fully operational and unaffected ...