Forum Discussion
app.powerbi not working
https://app.powerbi.com/ is not working, getting the below error:
Please try again later.
An unknown error occurred. If you continue to see this error, please provide the following information when requesting support.
14 Replies
ninajAdvocate I
Same issue here with the same error...
Same issue. Refer this: https://azure.microsoft.com/en-us/status/
The North Central US region is down.
*********************
*** Power BI Down ***
*********************
Same error I'm getting as well. Unable to log into Power BI Cloud...
Receiving error trying to log into:
https://powerbi.microsoft.com/en-us/landing/signin
-OR-
https://app.powerbi.com/groups/me/contentlist/reports
==> This site can’t be reached
==> app.powerbi.com took too long to respond.
==> Checking the connection
==> Checking the proxy and the firewall
==> Running Windows Network Diagnostics
==> Check your internet connection.they need to update the status page for power bi. The azure link says it's only pbi embedded that is down, but that's not accurate.
PowerBi online working again after refreshing the link.
yes, it has started working now ... I think it was down for 90 odd minutes ... which is not good :smileymad:
:smileysad:
Yes, good point.
90 minutes is a long time to be down for Power BI (+Azure). Not sure about the uptime for others in this space (Tableau, Qlik, Sisense, Alteryx, Domo, MicroStrategy, Looker, Dundas BI, Yellowfin, Pentaho, etc.)
However, in the past 2.5 years of using Power BI, this is the first outage I can recall.FYI...
======================================
==> AZURE STATUS HISTORY | 06-NOV-2017
======================================
==> Network Infrastructure - North Central US
==> Summary of impact: Between approximately 19:34 UTC and 21:04 UTC on 06 Nov 2017
==> Customers in North Central US may have experienced degraded performance, network drops, or timeouts when accessing Azure resources hosted in this region.
==> Engineers were aware of additional impact for customers using App Service in South Central US.
==> Engineers determined that this was caused by an underlying Network Infrastructure Event in this region which remains under investigation.
==> Preliminary root cause: Engineers identified configuration change as the potential root cause.
==> Mitigation: Engineers performed a change to the service configuration to BGP and mitigate the issue.
==> Next steps: Engineers will continue to investigate to establish the full root cause in approximately 72 hours.
