Resolved -
This issue is now resolved. Thank you for your patience and understanding.
Aug 12, 14:15 EDT
Update -
We have implemented a fix for this issue and are monitoring to ensure stability.
Aug 12, 12:58 EDT
Update -
We have identified a solution and are working to resolve this issue. Thank you for your continued patience.
Aug 12, 12:31 EDT
Update -
We have identified a solution and are working to resolve this issue. Thank you for your continued patience.
Aug 12, 12:10 EDT
Update -
We have identified a solution and are working to resolve this issue. Thank you for your continued patience.
Aug 12, 11:42 EDT
Update -
We have identified a solution and are working to resolve this issue. Thank you for your continued patience.
Aug 12, 09:52 EDT
Update -
We have identified an additional issue and are working to implement a solution.
Aug 12, 09:23 EDT
Update -
We have identified an additional issue and are working to implement a solution.
Aug 12, 09:02 EDT
Monitoring -
We have corrected the issue and are monitoring to ensure stability.
Aug 12, 07:07 EDT
Update -
We have identified the root cause of this issue and our team is working to implement a solution.
Aug 12, 06:54 EDT
Update -
We have identified the root cause of this issue and our team is working to implement a solution.
Aug 12, 06:36 EDT
Identified -
We have identified the root cause of this issue and our team is working to implement a solution.
Aug 12, 06:22 EDT
Update -
Our team is investigating this issue and we will continue to provide updates as our investigation continues.
Aug 12, 06:15 EDT
Investigating -
We’re investigating an issue where some user may be experiencing issues with positions data.
Aug 12, 05:39 EDT