BlizzNux Status

Live status of blizznux.com and the BlizzNux Launcher services.

All services are online
99.95% overall uptime
Website
BlizzNux Operational
306090 days ago 99.951% uptime today
BlizzNux uploads Operational
306090 days ago 100% uptime today
BlizzNux compatibility API Operational
306090 days ago 99.974% uptime today
BlizzNux Launcher
BlizzNux Launcher update feed Operational
306090 days ago 99.942% uptime today
Automation
BlizzNux Updates bot Operational
306090 days ago 99.907% uptime today

Past incidents

BlizzNux Launcher update feed — Timed out 1m
  • Investigating — The site did not answer within the time limit.
  • Resolved
BlizzNux Launcher update feed — Timed out 2m
  • Investigating — The site did not answer within the time limit.
  • Resolved
BlizzNux Launcher update feed — Timed out 2m
  • Investigating — The site did not answer within the time limit.
  • Resolved
BlizzNux Launcher update feed — Timed out 36s
  • Investigating — The site did not answer within the time limit.
  • Resolved
BlizzNux Launcher update feed — Timed out 48s
  • Investigating — The site did not answer within the time limit.
  • Resolved
BlizzNux Launcher update feed — Timed out 51s
  • Investigating — The site did not answer within the time limit.
  • Resolved
BlizzNux Launcher update feed — Timed out 46s
  • Investigating — The site did not answer within the time limit.
  • Resolved
BlizzNux Launcher update feed — Timed out 2m
  • Investigating — The site did not answer within the time limit.
  • Resolved
BlizzNux Launcher update feed — Timed out 48s
  • Investigating — The site did not answer within the time limit.
  • Resolved
BlizzNux Updates bot — Heartbeat missed 23m
  • Investigating — No check-in arrived within the expected interval.
  • Resolved
BlizzNux Launcher update feed — Server error (504 Gateway Timeout) 2m
  • Investigating — The site answered with a server error (504 Gateway Timeout).
  • Resolved
BlizzNux Updates bot — Heartbeat missed -118s
  • Resolved
  • Investigating — No check-in arrived within the expected interval.
BlizzNux compatibility API — Timed out 3m
  • Investigating — The site did not answer within the time limit.
  • Resolved
BlizzNux — Timed out 3m
  • Investigating — The site did not answer within the time limit.
  • Resolved
BlizzNux Launcher update feed — Expected text missing 1m
  • Investigating — The page loaded, but the text the check looks for was not on it.
  • Resolved
BlizzNux Launcher update feed — Expected text missing 1m
  • Investigating — The page loaded, but the text the check looks for was not on it.
  • Resolved
BlizzNux Launcher update feed — Expected text missing 1m
  • Investigating — The page loaded, but the text the check looks for was not on it.
  • Resolved
BlizzNux compatibility API — Not found (404) 1m
  • Investigating — The address answered 404 Not Found.
  • Resolved
BlizzNux — Not found (404) 1m
  • Investigating — The address answered 404 Not Found.
  • Resolved
BlizzNux compatibility API — Not found (404) 1m
  • Investigating — The address answered 404 Not Found.
  • Resolved
BlizzNux — Not found (404) 1m
  • Investigating — The address answered 404 Not Found.
  • Resolved
BlizzNux — Server error (502 Bad Gateway) 1m
  • Investigating — The site answered with a server error (502 Bad Gateway).
  • Resolved
BlizzNux — Server error (500 Internal Server Error) 7m
  • Investigating — The site answered with a server error (500 Internal Server Error).
  • Resolved
BlizzNux — Not found (404) 1m
  • Investigating — The address answered 404 Not Found.
  • Resolved
BlizzNux Launcher update feed — Server error (504 Gateway Timeout) 1m
  • Investigating — The site answered with a server error (504 Gateway Timeout).
  • Resolved
BlizzNux Launcher update feed — Server error (500 Internal Server Error) 2m
  • Investigating — The site answered with a server error (500 Internal Server Error).
  • Resolved
BlizzNux Launcher update feed — Server error (500 Internal Server Error) 2m
  • Investigating — The site answered with a server error (500 Internal Server Error).
  • Resolved
BlizzNux Launcher update feed — Server error (504 Gateway Timeout) 1m
  • Investigating — The site answered with a server error (504 Gateway Timeout).
  • Resolved
BlizzNux Launcher update feed — Server error (500 Internal Server Error) 2m
  • Investigating — The site answered with a server error (500 Internal Server Error).
  • Resolved
BlizzNux — Not found (404) 1m
  • Investigating — The address answered 404 Not Found.
  • Resolved
BlizzNux compatibility API — Not found (404) 1m
  • Investigating — The address answered 404 Not Found.
  • Resolved
BlizzNux compatibility API — Not found (404) 1m
  • Investigating — The address answered 404 Not Found.
  • Resolved
BlizzNux — Not found (404) 1m
  • Investigating — The address answered 404 Not Found.
  • Resolved
BlizzNux Launcher update feed — Server error (500 Internal Server Error) 1m
  • Investigating — The site answered with a server error (500 Internal Server Error).
  • Resolved
BlizzNux Launcher update feed — Server error (500 Internal Server Error) 1m
  • Investigating — The site answered with a server error (500 Internal Server Error).
  • Resolved
BlizzNux Updates bot — Heartbeat missed 29m
  • Investigating — No check-in arrived within the expected interval.
  • Resolved
BlizzNux compatibility API — Not found (404) 1m
  • Investigating — The address answered 404 Not Found.
  • Resolved
BlizzNux — Not found (404) 1m
  • Investigating — The address answered 404 Not Found.
  • Resolved
BlizzNux — Not found (404) 1m
  • Investigating — The address answered 404 Not Found.
  • Resolved
BlizzNux compatibility API — Not found (404) 1m
  • Investigating — The address answered 404 Not Found.
  • Resolved
BlizzNux — Not found (404) 1m
  • Investigating — The address answered 404 Not Found.
  • Resolved
BlizzNux compatibility API — Not found (404) 1m
  • Investigating — The address answered 404 Not Found.
  • Resolved
BlizzNux — Server error (500 Internal Server Error) 1m
  • Investigating — The site answered with a server error (500 Internal Server Error).
  • Resolved
BlizzNux Launcher update feed — Server error (500 Internal Server Error) 1m
  • Investigating — The site answered with a server error (500 Internal Server Error).
  • Resolved
BlizzNux Launcher update feed — Server error (500 Internal Server Error) 1m
  • Investigating — The site answered with a server error (500 Internal Server Error).
  • Resolved
BlizzNux Launcher update feed — Server error (500 Internal Server Error) 1m
  • Investigating — The site answered with a server error (500 Internal Server Error).
  • Resolved
BlizzNux compatibility API — Not found (404) 3m
  • Investigating — The address answered 404 Not Found.
  • Resolved
BlizzNux — Server error (500 Internal Server Error) 5m
  • Investigating — The site answered with a server error (500 Internal Server Error).
  • Resolved
BlizzNux — Not found (404) 1m
  • Investigating — The address answered 404 Not Found.
  • Resolved
BlizzNux — Not found (404) 1m
  • Investigating — The address answered 404 Not Found.
  • Resolved