Vilkas Outage History
Vilkas is up right nowVilkas had 3 outages in the last 2 years totaling 6h 7m of downtime — averaging 0.1 incidents per month.
There were 3 Vilkas outages since September 10, 2025 totaling 6h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.
Vilkas Now shops outage
Timeline · 6 updates
- investigating Sep 25, 2025, 10:59 AM UTC
Our datacenter provider is currently experiencing network issues affecting Vilkas Now shops. Their team is actively working on a fix, and we will share updates as soon as more information is available.
- monitoring Sep 25, 2025, 11:52 AM UTC
The network issues at our datacenter have been resolved. Vilkas Now shops are operating normally, and we are monitoring the situation to ensure stability.
- monitoring Sep 25, 2025, 12:19 PM UTC
We are continuing to monitor for any further issues.
- monitoring Sep 25, 2025, 12:21 PM UTC
We experienced a hardware failure (power supply) at our datacenter, which escalated into a wider service disruption. Most Vilkas systems have been back online since approximately 13:24 CET, but we are still seeing issues with email/SMTP servers. Our provider is continuing work on full recovery.
- monitoring Sep 25, 2025, 12:28 PM UTC
Email services have now been restored. All Vilkas systems are operating normally, and we will continue to monitor to ensure stability.
- resolved Sep 25, 2025, 12:57 PM UTC
All services are now fully operational. Thank you for your patience while we worked to restore normal operations.
Intermittant connectivity issues
Timeline · 3 updates
- identified Sep 10, 2025, 05:34 PM UTC
We have identified an issue that affects some of our shops. One of our loadbalancer nodes is experiencing network connectivity problems and that causes some of the connections to fail. We are working on resolving the network issues with our datacenter.
- monitoring Sep 10, 2025, 06:01 PM UTC
The loadbalancer node network issue has now been resolved. Monitoring for a bit.
- resolved Sep 10, 2025, 06:11 PM UTC
This incident has been resolved.