StatusDetector
HTTP Status CodeDown

101 Switching Protocols

The server agrees to switch protocols as requested by the client (e.g., upgrading to WebSocket).

Service appears unreachable or completely offline.

What to do

No action needed. The protocol switch was successful.

What to do next

  1. Check DNS records with a tool like dig, nslookup, or an online DNS lookup.
  2. Verify SSL certificate expiration in your browser or with an SSL checker.
  3. Review HTTP status codes — 5xx means a server-side problem, 4xx means a client-side error.
  4. Check for redirect loops or misconfigured headers.
  5. Check your hosting provider or CDN's status page.
  6. Use our Website Down Checker to test the domain from our servers.

Decode another status

Paste any other status message, error code, or phrase to get a plain-English explanation.

Status explanations are for informational purposes only. StatusDetector is not affiliated with any government agency, carrier, bank, or service provider.

Last reviewed