Iexperienced something similar during a previous service disruption. Before assuming it was an account issue, I checked the status from another network and tested with a fresh session after updating the client. That helped me rule out local configuration problems and confirmed it was a broader service issue. Hopefully the team can provide a root cause once everything is stable, as that would help users distinguish between platform outages and local configuration issues in the future.