Vilkas Outage History

Vilkas is up right now

Pingoru has recorded 48 incidents for Vilkas: 2 in the last 12 months and 2 in the last 90 days.

Source: status.vilkas.fi

48incidents recorded
2last 12 months
2last 90 days
2 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Vilkas in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202614 of 744 (0%)
September 202600 of 720 (0%)
October 202611 of 521 (0%)

Incidents, newest first

Critical October 2, 2026 Apothecary Shops partial outage 1h 4m Vilkas Apothecary Shops

Started Oct 02, 2026, 09:37 PM UTC· resolved Oct 02, 2026, 10:42 PM UTC

  1. identified Oct 02, 2026, 09:37 PM UTC

    An issue in the datacenter has caused small number of the apothecary shops to not be available. Fix is already on the way.

  2. resolved Oct 02, 2026, 10:42 PM UTC

    The issue has been resolved

Read the full incident report →

Critical August 21, 2026 Shops not available 3h 32m Vilkas Suite Shops

Started Aug 21, 2026, 10:27 AM UTC· resolved Aug 21, 2026, 01:59 PM UTC

  1. identified Aug 21, 2026, 10:27 AM UTC

    A storage issue in our datacenter has been indentified and is being fixed. To prevent dataloss the shops are not available.

  2. identified Aug 21, 2026, 10:54 AM UTC

    We are continuing to work on a fix for this issue.

  3. identified Aug 21, 2026, 11:49 AM UTC

    Datacenter has resolved the storage issue, we still have some work to do to get services back up safely.

  4. identified Aug 21, 2026, 12:07 PM UTC

    This is taking a bit longer than we anticipated

  5. identified Aug 21, 2026, 12:49 PM UTC

    Datacenter has to still do things to get the storage back up for us

  6. identified Aug 21, 2026, 01:24 PM UTC

    We're getting there. Progress is being made, and we're working to bring the shops back online safely. Thanks for your patience!

  7. monitoring Aug 21, 2026, 01:33 PM UTC

    Services are back up and running. We're continuing to monitor the situation closely. Shops will be slower for a while as the services are catching up.

  8. monitoring Aug 21, 2026, 01:41 PM UTC

    Looks good, shops are up and operational. We will continue to monitor the situation.

  9. resolved Aug 21, 2026, 01:59 PM UTC

    Situation is now normal, we will provide a postmortem in the near future.

  10. postmortem Aug 27, 2026, 02:38 PM UTC

    ## Summary On 21 August 2026, a storage backend incident at our datacenter provider caused an outage affecting slightly more than half of the shops hosted on our platform. Our monitoring detected the first service problems at **12:59:57 EEST**, and investigation started immediately. We worked closely with our datacenter provider throughout the incident while they investigated the storage backend, verified the affected systems and performed the manual actions required before the servers could be safely started again. All affected Vilkas application servers were back online by approximately **16:33 EEST**. We continued enhanced monitoring afterwards to ensure the environment remained stable. ## Root cause According to our datacenter provider, the root cause was a previously undetected hardware defect affecting a specific storage hardware model. The storage platform is redundant, with server data stored on multiple physical storage systems. Under normal circumstances, an issue with one storage backend is handled automatically by continuing operation through another backend. In this incident, however, some virtual servers entered an error state and required manual verification before they could be safely started again. This meant that resolving the underlying storage issue alone was not sufficient. The state of the affected storage and servers also had to be verified before services could be brought back online in a controlled manner. ## Timeline * **12:59:57 EEST** – Our monitoring detected the first service problems. Investigation started immediately. * **13:05** – Our datacenter provider identified an issue in its storage environment. * **13:12** – The provider confirmed the affected infrastructure and escalated the incident internally. * **13:23** – The provider had started work on the affected storage systems and confirmed to us that our infrastructure was impacted by the storage incident. * **13:27** – We published this incident on our status page. * **13:38** – The provider identified virtual servers that had entered an error state as a result of the storage incident. * **13:59** – Manual verification and actions on affected servers were in progress. * **During the afternoon** – We remained in continuous contact with the datacenter provider while the storage state and affected servers were verified and we coordinated the safe startup of our infrastructure. * **16:20** – The affected storage server was available again. * **16:33** – All affected Vilkas application servers were running. * **16:49** – Normal service operation had been confirmed and enhanced monitoring continued. ## Data integrity We have found **no indication of data loss or corruption** related to the incident. Affected shops were intentionally kept unavailable while the storage environment and affected servers were being verified. Services were only brought back online once the required systems could be started safely and in a controlled manner. ## Preventive actions Our datacenter provider has identified and mitigated the hardware defect responsible for the incident. They have also stated that they are improving their storage failover software as well as their internal processes and tooling for handling similar storage incidents. We are also reviewing the incident internally, including our startup procedures, monitoring and incident communication. We apologize for the disruption and thank you for your patience while we worked with our datacenter provider to bring the affected services safely back online.

Read the full incident report →

Major September 25, 2025 Vilkas Now shops outage 1h 58m Vilkas Now Shops

Started Sep 25, 2025, 10:59 AM UTC· resolved Sep 25, 2025, 12:57 PM UTC

  1. 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.

  2. 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.

  3. monitoring Sep 25, 2025, 12:19 PM UTC

    We are continuing to monitor for any further issues.

  4. 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.

  5. 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.

  6. 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.

Read the full incident report →

Major September 10, 2025 Intermittant connectivity issues 36m Vilkas Suite Shops, Vilkas Enterprise Shops, Vilkas Apothecary Shops

Started Sep 10, 2025, 05:34 PM UTC· resolved Sep 10, 2025, 06:11 PM UTC

  1. 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.

  2. monitoring Sep 10, 2025, 06:01 PM UTC

    The loadbalancer node network issue has now been resolved. Monitoring for a bit.

  3. resolved Sep 10, 2025, 06:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 10, 2025 A problem has been detected. 10h 59m Vilkas Suite Shops

Started Apr 10, 2025, 05:30 AM UTC· resolved Apr 10, 2025, 04:29 PM UTC

  1. investigating Apr 10, 2025, 05:30 AM UTC

    We are investigating intermittent connectivity issue.

  2. monitoring Apr 10, 2025, 05:38 AM UTC

    Looks like it was just fluke in the network. We will continue monitoring.

  3. monitoring Apr 10, 2025, 11:28 AM UTC

    Servers are a bit overloaded because of huge amount of scraping traffic from china.

  4. resolved Apr 10, 2025, 04:29 PM UTC

    Looks like we have managed to block enough of the scraping traffic (for now)

Read the full incident report →

Major January 14, 2025 Problem with shops 35m Vilkas Suite Shops

Started Jan 14, 2025, 09:58 PM UTC· resolved Jan 14, 2025, 10:34 PM UTC

  1. investigating Jan 14, 2025, 09:58 PM UTC

    We are currently investigating this issue.

  2. identified Jan 14, 2025, 10:08 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Jan 14, 2025, 10:15 PM UTC

    There is an intermittant network connectivity issue in the datacenter affecting some of our hosts. This connectivity problem causes "heavy traffic" messages on pageloads. The datacenter is working on the issue.

  4. resolved Jan 14, 2025, 10:34 PM UTC

    The network issues should now be resolved by the datacenter.

Read the full incident report →

Major November 27, 2024 Partial degraded service 20m Vilkas Suite Shops

Started Nov 27, 2024, 11:50 AM UTC· resolved Nov 27, 2024, 12:10 PM UTC

  1. investigating Nov 27, 2024, 11:50 AM UTC

    We are currently investigating partially degraded service on Vilkas Suite shops.

  2. identified Nov 27, 2024, 12:04 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Nov 27, 2024, 12:07 PM UTC

    Service has been restored, performance might be affected for a while

  4. resolved Nov 27, 2024, 12:10 PM UTC

    This incident has been resolved.

Read the full incident report →