The incident has been resolved. Routine maintenance unexpectedly caused an internal component to fail because of an issue with the configuration. We will review our procedures to make sure this does not happen in the future.
Posted Jun 24, 2019 - 07:23 CEST
The problem has been solved, some data may still be delayed.
Posted Jun 24, 2019 - 06:38 CEST
We have identified an issue with an internal component and are working on a fix.
Posted Jun 24, 2019 - 05:50 CEST
We are currently investigating elevated error rate with the API.