Update: Friday, 22 January 2016 21:53 UTC
Root cause has been isolated to an issue within one of our backend services which was impacting which is causing periods of latency over 2 hours. Current data is no longer latent. To address this issue we have re-deployed our backend service. Current data for multiple data types is now working as expected. Some customers may experience period of data over 2 hours latency and we estimate 3 before all data is no longer latent.
Root cause has been isolated to an issue within one of our backend services which was impacting which is causing periods of latency over 2 hours. Current data is no longer latent. To address this issue we have re-deployed our backend service. Current data for multiple data types is now working as expected. Some customers may experience period of data over 2 hours latency and we estimate 3 before all data is no longer latent.
- Next Update: Before 01/23 02:00 UTC