SENKO Outage History

SENKO is up right now

SENKO had 14 outages in the last 2 years totaling 597h 42m of downtime, averaging 0.6 incidents per month.

There were 14 SENKO outages since January 18, 2026 totaling 597h 42m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: senkostatus.com

Minor October 17, 2026

[Post-Mortem] VMmanager Security Incident

Detected by Pingoru
Oct 17, 2026, 06:30 AM UTC
Resolved
Oct 19, 2026, 03:30 PM UTC
Duration
2d 9h
Timeline · 2 updates
  1. identified Oct 17, 2026, 06:30 AM UTC

    The VM panel is currently under maintenance, therefore it is not available. Please contact the support team if you require any changes within the VM, such as a OS reinstall or password change. Please note that the maintenance time does not reflect the actual time it will take for the panel to come back online.

  2. resolved Oct 19, 2026, 03:30 PM UTC

    Marking as resolved (see post-mortem)

Read the full incident report →

Minor June 15, 2026

Packet Loss in Finland

Detected by Pingoru
Jun 15, 2026, 06:00 PM UTC
Resolved
Jun 15, 2026, 06:20 PM UTC
Duration
19m
Timeline · 2 updates
  1. identified Jun 15, 2026, 05:25 PM UTC

    Our Finland location is currently experiencing traffic losses originating from our upstream provider's uplink at Arelion since 05:25 PM UTC. The issue has been traced to Arelion's side, with packet losses visible directly on their routers. This confirms the problem lies within their network and not our own configuration. This issue also impacts many other providers who rely on Arelion. Our upstream provider has escalated the matter, and we are currently awaiting resolution on Arelion's end. As the fix is dependent on Arelion's team, we do not have a definitive timeframe at this stage. We are staying in close contact with our upstream provider and will provide updates as soon as the situation progresses. We apologize for the disruption and appreciate your understanding. Further updates will follow as soon as we have more information.

  2. resolved Jun 15, 2026, 06:20 PM UTC

    We are happy to confirm that the Finland traffic loss issue has been fully resolved as of 06:20 PM UTC. Arelion has confirmed that the problem was on their side, caused by congestion issues within their network in Finland. Our Finland network is now operating normally, and packet losses are no longer present. We will continue to monitor the situation to ensure stability remains consistent. Fun fact: this was most likely linked to the UEFA World Cup, with a live game between Belgium and Egypt taking place right now. We thank everyone for their patience and understanding throughout this incident.

Read the full incident report →

Minor February 21, 2026

[All locations] Ongoing Network Disruption Due to DDoS Attack

Detected by Pingoru
Feb 21, 2026, 08:45 AM UTC
Resolved
Feb 21, 2026, 05:41 PM UTC
Duration
8h 55m
Affected: 🌐 Landing Page💻 Client Area💻 Dedicated Panel🎮 Game Panel🔐 Secrets💬 Live Chat💾 OS Repository📚 Wiki🇩🇪 SNK Germany, Frankfurt am Main🇫🇮 SNK Finland, Helsinki🇳🇱 SNK Netherlands, Amsterdam🌐 DNS Panel🇩🇪 SNK ns1.senkodns.net🇫🇮 SNK ns2.senkodns.net🇩🇪 SNK Route Reflector 1🇩🇪 SNK Route Reflector 2🇫🇮 SNK Edge Router 1🇳🇱 SNK Route Reflector 1🇳🇱 SNK Route Reflector 2
Timeline · 5 updates

Read the full incident report →

Minor February 17, 2026

Network Degradation in Netherlands

Detected by Pingoru
Feb 17, 2026, 06:58 PM UTC
Resolved
Feb 17, 2026, 10:56 PM UTC
Duration
3h 57m
Affected: 🇳🇱 SNK Netherlands, Amsterdam
Timeline · 2 updates
  1. identified Feb 17, 2026, 05:20 PM UTC

    We are currently observing intermittent network connectivity issues in our Netherlands location caused by a fault at the upstream provider ZetNet. According to the provider, their wavelength carrier is experiencing problems, with multiple transport waves currently down. This is impacting overall connectivity within the facility and may result in packet loss, increased latency, or temporary reachability issues for affected services. The upstream provider is actively working to restore the failed transport waves. We are monitoring the situation closely and will provide further updates as more information becomes available or once stability is fully restored. We apologize for the disruption and appreciate your patience.

  2. resolved Feb 17, 2026, 10:56 PM UTC

    Network connectivity in our Netherlands location has been fully restored as of 10:56 PM UTC. The upstream provider ZetNet has confirmed that the issue affecting their wavelength carrier and multiple transport waves has been resolved. No further interruptions or instability are expected. The provider also noted that they are continuing internal work to improve resilience and prevent similar incidents in the future. There was no complete downtime during this incident. However, internal packet loss caused by the upstream fault resulted in intermittent connectivity degradation and brief packet loss for some services while the issue was ongoing. We will continue to monitor the location to ensure ongoing stability.

Read the full incident report →

Major February 5, 2026

Multiple nodes outage

Detected by Pingoru
Feb 05, 2026, 11:39 AM UTC
Resolved
Feb 05, 2026, 11:39 AM UTC
Duration
–
Timeline · 2 updates
  1. investigating Feb 05, 2026, 09:30 AM UTC

    A part of our DE-RZ9 cluster is currently unavailable due to issues that occurred following the planned maintenance. Our team is actively working to restore full service as quickly as possible. Affected nodes: - fra-9950x-pallida - fra-9950x-zerda All customers impacted by this unplanned downtime will receive compensation in the form of three additional days added to their service period. We sincerely apologize for the inconvenience and appreciate your patience while we resolve the issue.

  2. resolved Feb 05, 2026, 11:39 AM UTC

    The issue affecting a part of our DE-RZ9 cluster has now been fully resolved, and all services are operating normally again. Compensation in the form of three additional days of service will be credited automatically to all impacted customers. No action is required on your side.

Read the full incident report →