What is happening?

Many Android users are opening YouTube and seeing this message instead of their videos:

“There was a problem with the server [400]”

Some people also see it as “Server Error 400”, and it sometimes appears when the app is loading the home feed, subscriptions, or a video.

YouTube has said it knows about the problem and is working on it. Reports so far point mainly to Android devices.

What does “Error 400” mean?

An error with the number 400 is a “Bad Request.” In plain language, your phone asked YouTube for something, and YouTube’s server could not understand or accept the request.

There are two main reasons this happens:

  1. The problem is on YouTube’s side. A bug or outage in YouTube’s systems can break requests that were fine before. Nothing you do on your phone will fix this, and you have to wait for YouTube to repair it.
  2. The problem is on your phone. A temporary glitch or a weak connection can produce the same error.

Because you can’t tell which one you have, it is worth trying the quick fixes below. They take only a few minutes.

Quick fixes to try

1. Restart your phone

Hold the power button and tap Restart. This clears small glitches in the system and the network connection, and it fixes more problems than you might expect.

2. Check your internet connection

A weak or unstable connection can cause a “bad request.”

  • Open a website in your browser to confirm the internet works.
  • Turn Airplane mode on for 10 seconds, then turn it off.
  • Switch between Wi-Fi and mobile data to see if one works better.

What if these don’t work?

If you have tried both fixes and the error is still there, the problem is most likely on YouTube’s side. In that case:

  • Wait. Fixes for server-side problems usually roll out within hours or a few days.
  • Use YouTube in your browser. Open youtube.com in Chrome or another browser on your phone as a temporary way to keep watching.

Note: YouTube has acknowledged the problem on its Community page and says its teams are investigating. We will update this article when a fix is confirmed.

Write a comment