You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An announcement went out to the API mailing list on 17 October describing the JHU outage. The initial problem expanded to include many days of apparently-missing data. The outage ultimately had two causes: First, during geographical aggregation, we were including the population of the megacounty (=the state population) when aggregating populations from counties up to the state level, causing the apparent population of the state to be double its actual value. Second, a component of the data versioning system had become corrupted. This component tracks which issue is the most recent for each day of data. Without it, the system could not identify the most recent issues, and thus reported no data.
Remaining work:
Run the is_latest_issue fix in production - @korlaxxalrok
Uh oh!
There was an error while loading. Please reload this page.
An announcement went out to the API mailing list on 17 October describing the JHU outage. The initial problem expanded to include many days of apparently-missing data. The outage ultimately had two causes: First, during geographical aggregation, we were including the population of the megacounty (=the state population) when aggregating populations from counties up to the state level, causing the apparent population of the state to be double its actual value. Second, a component of the data versioning system had become corrupted. This component tracks which issue is the most recent for each day of data. Without it, the system could not identify the most recent issues, and thus reported no data.
Remaining work:
The text was updated successfully, but these errors were encountered: