Microsoft Subscriptions page does not load for days - Something went wrong on our end. Give it a few minutes, then try again. TraceID: XLnFXFNKWECvd11K.9.79

Anonymous
2024-10-04T14:48:29+00:00

I am not able to look at my subscriptions. I have tried the past threads on this which have no resolution. I have tried talking to Microsoft support, who told me that I was required to wait 48 hours and try again. But it has been weeks, and this is not going away. Is it possible to talk to someone at Microsoft who can fix the error? This is on their server backend.

URL: https://account.microsoft.com/services

error:
Something went wrong on our end. Give it a few minutes, then try again.

TraceID: XLnFXFNKWECvd11K.9.79

Screenshot:

Microsoft 365 and Office | Subscription, account, billing | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

123 answers

Sort by: Most helpful
  1. Anonymous
    2024-11-15T05:51:01+00:00

    That's great, Ian!

    I wonder how far down I am in the Microsoft queue to get this resolved? It's been 3+ months. Microsft should give all of us waiting for this to get fixed subscription extensions as we cannot get the family-plan licenses on other devices.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-11-15T02:42:57+00:00

    Still having the issue. Checked in Edge on iOS…

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-11-15T02:32:51+00:00

    I just checked mine and I’m still in the same boat as you.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-11-15T01:08:07+00:00

    I just checked. The "Services and Subscriptions - Something went Wrong" problem still exists on my Apple devices and browsers

    Hopefully you are correct, and it is slowly being rolled out.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-11-15T00:12:07+00:00

    It's now fixed for me. I think the fix is being slowly released to all users. Good luck everyone.

    Was this answer helpful?

    0 comments No comments