This is probably because AMO is currently in read-only mode as part of a planned server migration.
We’ll post an announcement once the migration is complete; you might want to try logging in again at that time and let us know if you encounter any issues.