Incidents reported on status page for Nexar https://status.nexar.to/ https://d1lppblt9t2x15.cloudfront.net/logos/ba548197986a441eca4cffa7c0470936.gif https://status.nexar.to/ en https://status.nexar.to/ Sat, 07 Mar 2026 23:48:37 +0000 https://status.nexar.to/#b9343dc430427d9c95f8f83f0e76519b91dfd64295ca68921c07d3cd120bfbd9 nexar.to recovered https://status.nexar.to/ Sat, 07 Mar 2026 23:33:31 +0000 https://status.nexar.to/#b9343dc430427d9c95f8f83f0e76519b91dfd64295ca68921c07d3cd120bfbd9 nexar.to went down 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. 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. 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. 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. https://status.nexar.to/ Sun, 15 Feb 2026 23:38:59 +0000 https://status.nexar.to/#2cd9878a1ca79107f7b8c16d3ce6007b6880392359725f5dec0ccba1faaa354d nexar.to recovered https://status.nexar.to/ Sun, 15 Feb 2026 23:36:32 +0000 https://status.nexar.to/#2cd9878a1ca79107f7b8c16d3ce6007b6880392359725f5dec0ccba1faaa354d nexar.to went down https://status.nexar.to/ Wed, 11 Feb 2026 16:00:40 +0000 https://status.nexar.to/#8cbbc19fb91e3e67ce0d153d20197ab27aa98b209fd6c73aede02efc8c3601ff nexar.to recovered https://status.nexar.to/ Wed, 11 Feb 2026 15:57:39 +0000 https://status.nexar.to/#8cbbc19fb91e3e67ce0d153d20197ab27aa98b209fd6c73aede02efc8c3601ff nexar.to went down https://status.nexar.to/ Sun, 08 Feb 2026 17:24:47 +0000 https://status.nexar.to/#7d19a900c11799355c1b8276bf1650155bdd7ed17670a3c61939dcdedf6542be nexar.to recovered https://status.nexar.to/ Sun, 08 Feb 2026 17:21:41 +0000 https://status.nexar.to/#7d19a900c11799355c1b8276bf1650155bdd7ed17670a3c61939dcdedf6542be nexar.to went down https://status.nexar.to/ Sat, 07 Feb 2026 18:06:44 +0000 https://status.nexar.to/#6dbf3d09c6b9b80dc7aa2ff30dab54517490574f5948855d03022b4c8b9dc56a nexar.to recovered https://status.nexar.to/ Sat, 07 Feb 2026 18:03:40 +0000 https://status.nexar.to/#6dbf3d09c6b9b80dc7aa2ff30dab54517490574f5948855d03022b4c8b9dc56a nexar.to went down https://status.nexar.to/ Wed, 04 Feb 2026 12:24:37 +0000 https://status.nexar.to/#10a0895fb51c27870cfc8faed26cd2c16b9dc2c4060567478e5b417530009dae nexar.to recovered https://status.nexar.to/ Wed, 04 Feb 2026 12:18:52 +0000 https://status.nexar.to/#10a0895fb51c27870cfc8faed26cd2c16b9dc2c4060567478e5b417530009dae nexar.to went down https://status.nexar.to/ Sat, 24 Jan 2026 21:57:37 +0000 https://status.nexar.to/#dda853d13dd4aee3723d8452e0625b2c9046db8f6eb30c46c7b9d2153e2ca466 nexar.to recovered https://status.nexar.to/ Sat, 24 Jan 2026 21:21:34 +0000 https://status.nexar.to/#dda853d13dd4aee3723d8452e0625b2c9046db8f6eb30c46c7b9d2153e2ca466 nexar.to went down https://status.nexar.to/ Tue, 13 Jan 2026 09:09:39 +0000 https://status.nexar.to/#498498638f5467f06a005d796459a4c2c1672d0da54c4ac89186d12a57933376 nexar.to recovered https://status.nexar.to/ Tue, 13 Jan 2026 09:06:33 +0000 https://status.nexar.to/#498498638f5467f06a005d796459a4c2c1672d0da54c4ac89186d12a57933376 nexar.to went down