Incidents | Nexar Incidents reported on status page for Nexar https://status.nexar.to/ https://d1lppblt9t2x15.cloudfront.net/logos/ba548197986a441eca4cffa7c0470936.gif Incidents | Nexar https://status.nexar.to/ en nexar.to went down https://status.nexar.to/ Mon, 25 May 2026 22:13:19 +0000 https://status.nexar.to/#285abf0be0c29fca5839dc0a4a26e015b13637a13f1f12ecf5a701e541eb4264 nexar.to went down nexar.to recovered https://status.nexar.to/ Sat, 11 Apr 2026 19:57:30 +0000 https://status.nexar.to/#e4b9edee8d8f4775e371925e2a203d815425e9e4c51d52eb48acff4d590c8320 nexar.to recovered nexar.to went down https://status.nexar.to/ Sat, 11 Apr 2026 19:30:41 +0000 https://status.nexar.to/#e4b9edee8d8f4775e371925e2a203d815425e9e4c51d52eb48acff4d590c8320 nexar.to went down Some people get the “Authentication failed” error when executing the loader. https://status.nexar.to/incident/830504 Sun, 22 Feb 2026 09:39:00 -0000 https://status.nexar.to/incident/830504#c6617174d115841a94390318156e6791a3cd2acbc68bea03d0f13a7541e57cf6 The problem should now be resolved. We apologize for the inconvenience. If the problem persists, please open a ticket at discord.gg/nexar. Some people get the “Authentication failed” error when executing the loader. https://status.nexar.to/incident/830504 Sun, 22 Feb 2026 09:25:00 -0000 https://status.nexar.to/incident/830504#8807f4a09891526a4b4bbcd79632fb8917e1421423934a2fa68c9d93a2700843 We have found the problem. We are now working on fixing the error. Some people get the “Authentication failed” error when executing the loader. https://status.nexar.to/incident/830504 Sun, 22 Feb 2026 09:19:00 -0000 https://status.nexar.to/incident/830504#3b249dc105326742c41b1af75d6c823a90cf6ba574e5fb0e798206ebc919af19 We have uploaded a new version to obtain more information about this issue. Some people get the “Authentication failed” error when executing the loader. https://status.nexar.to/incident/830504 Sun, 22 Feb 2026 07:51:00 -0000 https://status.nexar.to/incident/830504#2b400e45d327093427f3e05be19d94b18258070adc0434e9a0f7dff5aac36ce0 We are aware of this error and are searching for the problem.