At 2018-08-17 10:30 UTC a production release caused ORCID’s replicated databases to fall behind the master copy. During the period(see timeline below) database read operations on recent writes would cause issues for users on the registry, clients using the Member API and public API. Write operations were not affected.
10:30 UTC Production release that was the root cause of the issue was pushed out.
12:40 ORCID staff diagnosed an issue based off user reports.
~14:00 UTC Issues on registry were mitigated.
~14:30 UTC Issue on Member API were mitigated.
We expect to have the public API issues mitigated around ~17:00 UTC. We’ll update this thread again when all issues are confirmed resolved.
Thanks for your patience,
Rob