Incidents | Synvaria Incidents reported on status page for Synvaria https://status.synvaria.com/ https://d1lppblt9t2x15.cloudfront.net/logos/bd5f17d09d75966ac1b1d7a4b0e00a2d.png Incidents | Synvaria https://status.synvaria.com/ en Node01 down due to hypervisor change https://status.synvaria.com/incident/392386 Sat, 20 Jul 2024 00:15:00 -0000 https://status.synvaria.com/incident/392386#cf9a64907c8d94d0f2ae9e06bf04a4be14d40addf3df70ae5be026014add23f4 We have fully recovered from the outage. Node01 down due to hypervisor change https://status.synvaria.com/incident/392386 Thu, 18 Jul 2024 14:25:00 -0000 https://status.synvaria.com/incident/392386#a741887a26b58f23f61200f3a24daa374ce7d67926f23c67724bd5275b633c4c We have recovered from the server downtime. We are now working on restoring the data to the Nexus server. Node01 down due to hypervisor change https://status.synvaria.com/incident/392386 Mon, 01 Jul 2024 08:12:00 -0000 https://status.synvaria.com/incident/392386#dd4227aa5a91d2d52207ab640e021d869bfe1064b90ee1ed50c81e46432f91fb Node01 is currently down and under maintenance due to our datacenter provider moving our data to a USA location. Node01 affected by DDoS attack https://status.synvaria.com/incident/350320 Wed, 03 Apr 2024 20:27:00 -0000 https://status.synvaria.com/incident/350320#cbb1b4405b198a232cac18d0ca6e5170c3e7a98a13650d789be2bca2bb989331 We have resolved the issue. Node01 affected by DDoS attack https://status.synvaria.com/incident/350320 Wed, 03 Apr 2024 16:28:00 -0000 https://status.synvaria.com/incident/350320#4334caa038dc23a0d6a63f20f210d48d11f7ad47c7889bc4dba5e8850bc70586 One of our primary servers, Node01 was recently attacked by a DDoS attack. We have mitigated the attack and are now working on recovery. IP change on Synvaria Node 01 https://status.synvaria.com/incident/342566 Tue, 19 Mar 2024 20:00:00 +0000 https://status.synvaria.com/incident/342566#53afe4cfac3993fec0ae13234b70cc8b2692a253fc0a6cadca934a793585d17f Maintenance completed IP change on Synvaria Node 01 https://status.synvaria.com/incident/342566 Mon, 18 Mar 2024 21:59:00 -0000 https://status.synvaria.com/incident/342566#77abcae42a51cd83228570e628dccebd88aa34f4fc7a40257b52815449226643 We are changing our server IP for node01. All services connected to this server set will be unavailable for a short period of time. Node01 down due to server overload https://status.synvaria.com/incident/318459 Sun, 28 Jan 2024 17:10:00 -0000 https://status.synvaria.com/incident/318459#4b3d6a95c341baf955b42a1a18549fcaa30168a7ca3646cdc5a99f7a3fd2113e We have successfully updated the network and the server and its nodes are back online. Node01 down due to server overload https://status.synvaria.com/incident/318459 Sun, 28 Jan 2024 15:07:00 -0000 https://status.synvaria.com/incident/318459#4d4a58399d6c6e41a37a10ad0e98b52dc098c05c99facc31ad3214430115f275 We have idenitifed the cause of this issue and looking for a fix. In the meantime, we will be changing the networking settings for node01. Node01 down due to server overload https://status.synvaria.com/incident/318459 Fri, 26 Jan 2024 17:30:00 -0000 https://status.synvaria.com/incident/318459#90b726f7ca9aeec061e56928467d8f3cd7d16389ecddedd443127f3b4d060aa3 We have detected a server crash while booting node01. This turns out to be an overload issue due to an uncontrolled backup generation. We are now scaling the server capacity and undergoing a DNS/network change. Database server offline https://status.synvaria.com/incident/313118 Tue, 16 Jan 2024 07:17:00 -0000 https://status.synvaria.com/incident/313118#a571dc725eae6d31567a90748f9625782505e85486694d3451bbdfaee1e29033 Situation was resolved. Database server offline https://status.synvaria.com/incident/313118 Tue, 16 Jan 2024 07:17:00 -0000 https://status.synvaria.com/incident/313118#a571dc725eae6d31567a90748f9625782505e85486694d3451bbdfaee1e29033 Situation was resolved. Database server offline https://status.synvaria.com/incident/313118 Tue, 16 Jan 2024 07:17:00 -0000 https://status.synvaria.com/incident/313118#a571dc725eae6d31567a90748f9625782505e85486694d3451bbdfaee1e29033 Situation was resolved. Database server offline https://status.synvaria.com/incident/313118 Mon, 15 Jan 2024 19:16:00 -0000 https://status.synvaria.com/incident/313118#27479fdf905077cfc95ff0cc8ae25a7b2bf494a55778bb9c33fb48f93b7d9583 Main server, synvaria.com, went down unexpectedly. Currently investigating the issue. Database server offline https://status.synvaria.com/incident/313118 Mon, 15 Jan 2024 19:16:00 -0000 https://status.synvaria.com/incident/313118#27479fdf905077cfc95ff0cc8ae25a7b2bf494a55778bb9c33fb48f93b7d9583 Main server, synvaria.com, went down unexpectedly. Currently investigating the issue. Database server offline https://status.synvaria.com/incident/313118 Mon, 15 Jan 2024 19:16:00 -0000 https://status.synvaria.com/incident/313118#27479fdf905077cfc95ff0cc8ae25a7b2bf494a55778bb9c33fb48f93b7d9583 Main server, synvaria.com, went down unexpectedly. Currently investigating the issue. Database server offline https://status.synvaria.com/incident/313118 Mon, 15 Jan 2024 18:43:00 -0000 https://status.synvaria.com/incident/313118#0266b4d1ae3f0fd75ba664539421aca39e342f6edaad63c5f6312524b7557217 During a routine maintenance cycle, the organization experienced a temporary disruption as the database server unexpectedly went offline. This incident resulted in a brief interruption to internal workflows and external services. The IT team promptly identified and resolved the issue, minimizing downtime. A post-incident analysis was conducted to strengthen future preventive measures and improve overall system resilience. Communication efforts kept stakeholders informed throughout the incident, contributing to a swift and transparent resolution. Database server offline https://status.synvaria.com/incident/313118 Mon, 15 Jan 2024 18:43:00 -0000 https://status.synvaria.com/incident/313118#0266b4d1ae3f0fd75ba664539421aca39e342f6edaad63c5f6312524b7557217 During a routine maintenance cycle, the organization experienced a temporary disruption as the database server unexpectedly went offline. This incident resulted in a brief interruption to internal workflows and external services. The IT team promptly identified and resolved the issue, minimizing downtime. A post-incident analysis was conducted to strengthen future preventive measures and improve overall system resilience. Communication efforts kept stakeholders informed throughout the incident, contributing to a swift and transparent resolution.