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
We currently have a read-only server back up, which should allow the AutoML benchmark to function as normal (access to datasets, tasks, and benchmarking suites should work as normal).
Original Message:
OpenML has been out for a week. This is due to a cyber attack on the Eindhoven University of Technology. No data has been compromised, but the university has decided to slowly and methodically re-open its network services, which is why it takes a while.
Currently, we are unaware when the servers will be accessible again. Estimates are sometime in the last week of January, though we have some hope it may be sooner. This is a lot longer than we initially expected, so we are trying to work on a solution which allows users to access common functionality (primarily downloading datasets and tasks). We do not have a timeline for this.
We apologize for the inconvenience.
The text was updated successfully, but these errors were encountered:
Update 23 January:
The main thread for updates is here: https://github.com/orgs/openml/discussions/20
We currently have a read-only server back up, which should allow the AutoML benchmark to function as normal (access to datasets, tasks, and benchmarking suites should work as normal).
Original Message:
OpenML has been out for a week. This is due to a cyber attack on the Eindhoven University of Technology. No data has been compromised, but the university has decided to slowly and methodically re-open its network services, which is why it takes a while.
Currently, we are unaware when the servers will be accessible again. Estimates are sometime in the last week of January, though we have some hope it may be sooner. This is a lot longer than we initially expected, so we are trying to work on a solution which allows users to access common functionality (primarily downloading datasets and tasks). We do not have a timeline for this.
We apologize for the inconvenience.
The text was updated successfully, but these errors were encountered: