Power BI Server access failed

[Guo]

Since the beginning of the week, there have been frequent failures in accessing the workspace. Last Friday, I waited for a while and was able to access it again. Today, this problem occurred again. Is it our server being upgraded?

[v-prasare]

May I ask if you have resolved this issue? If so, Can you please share the resolution steps here. This will be helpful for other community members who have similar problems to solve it faster. For any further discussions or questions, please post in the Microsoft Fabric Community Forum we’ll be happy to assist.
Thank you for being part of the Microsoft Fabric Community.

[Guo]

The problem has been temporarily resolved. I understand that it was caused by the instability of the server, as I checked my identity verification and account and found no issues. Usually, I can access it normally after waiting for a refresh. However, this situation has been occurring slightly more frequently recently. I don't understand if it was an official upgrade to the backend service

[v-prasare]

Thanks for the update @Guo.

[v-prasare]

In this scenario i suggest you to raise a support ticket here. so, that they can assit you in addressing the issue you are facing. please follow below link on how to raise a support ticket:

How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

[rohit1991]

Hii @Guo 

This issue is usually caused by temporary service instability, authentication/session token expiry, or capacity-related throttling in Power BI Service, not a permanent server failure. Since access works again after some time, it indicates a transient backend or service refresh issue (e.g., maintenance or load balancing). The recommended approach is to check Service Health, refresh login/session, and monitor if the issue correlates with peak usage or tenant capacity limits.

[Guo]

Indeed, waiting for a while and trying to refresh can indeed solve this problem, but my curiosity is whether the server has been very unstable recently. I thought I had not encountered this problem so frequently in my previous use