Is SENKO down?

Last checked 8m ago
Current status
SENKO is up

No incidents right now.

  • Official status page: senkostatus.com
  • Checked every 5 minutes
  • 31 components tracked

SENKO is operational right now. Last checked 8m ago; the most recent incident resolved 11h ago.

Real-time SENKO status, recent outages, and incident history: pulled directly from SENKO's official status page at senkostatus.com every 5 minutes. Pingoru tracks 31 SENKO services and has captured 8 incidents in the last 90 days (99.71% uptime). Get email, Slack, Discord, or webhook alerts the moment SENKO reports a new incident, free for 3 monitors, no credit card.

Users who monitor SENKO also follow these Telecom services: Optus SMS iQmetrix TPG Telecom Dubber Vimla Simbase gaiia software Helium Mobile Tuatahi First Fibre Glink View all 8,000+ providers
SENKO uptime 99.71% uptime · past 90 days
Mon Wed Fri
JulAugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 36m
    Started Oct 21, 2026, 01:59 PM UTC · Resolved Oct 21, 2026, 02:35 PM UTC
    Timeline · 2 updates
    • identified · Oct 21, 2026, 01:59 PM UTC

      We are currently performing an emergency replacement of a failed NVMe drive in this node's RAID array. All customer data is safe and intact. Affected VMs will be back online as soon as the disk replacement is complete and the node has been booted back into the OS. We'll post an update once service is restored.

    • resolved · Oct 21, 2026, 02:35 PM UTC

      The affected node is back online and virtual machines are now powering back on. Services should return to normal over the next 15-20 minutes as each VM completes boot.

    Latest: The affected node is back online and virtual machines are now powering back on. Services should return to normal over the next 15-20 minutes as each VM completes boot.

  2. Resolved 2d 9h
    Started Oct 17, 2026, 06:30 AM UTC · Resolved Oct 19, 2026, 03:30 PM UTC
    Timeline · 2 updates
    • 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.

    • resolved · Oct 19, 2026, 03:30 PM UTC

      Marking as resolved (see post-mortem)

    Latest: Marking as resolved (see post-mortem)

  3. Resolved 4h 56m
    Started Aug 31, 2026, 07:25 PM UTC · Resolved Sep 01, 2026, 12:22 AM UTC
    Timeline · 4 updates
    • investigating · Aug 31, 2026, 05:55 PM UTC

      We are investigating the issue on the ams-9950x-odessana node in the Netherlands.

    • identified · Aug 31, 2026, 06:56 PM UTC

      We found the cause of the issue and are working with the data center engineers to diagnose and resolve it as soon as possible.

    • identified · Aug 31, 2026, 09:47 PM UTC

      We are continuing our work on resolving the issue.

    • resolved · Sep 01, 2026, 12:22 AM UTC

      After a thorough investigation, we identified the root cause of the incident: a software issue between the AMD platform and IOMMU caused the PCI devices backing the NVMe drives on cluster node ams-9950x-odessana to malfunction on a software level, forcing the system to switch into a read-only mode and render the VMs unoperable. The issue was initially misdiagnosed as a drive failure, which led to an extended delay while we requested remote hands at the data center to replace the suspected faulty drive. Further diagnosis revealed the actual cause. We adjusted the BIOS settings accordingly, then gracefully recovered and resynced the RAID array on the node. All of the VMs are back up since 00:04 AM UTC, and all customer data is safe. However, we strongly recommend running a file system check on any virtual machines hosted on ams-9950x-odessana to rule out any latent issues. We sincerely apologize for the disruption and the extended downtime. We will be providing two extra days of service time to all customer services that were affected by this outage.

    Latest: After a thorough investigation, we identified the root cause of the incident: a software issue between the AMD platform and IOMMU caused the PCI devices backing the NVMe drives on …

  4. Resolved –
    Started Aug 27, 2026, 12:48 PM UTC · Resolved Aug 27, 2026, 12:48 PM UTC
    Timeline · 2 updates
    • identified · Aug 27, 2026, 11:35 AM UTC

      We are investigating the issues with the cluster nodes fra-9275f-odessana, fra-9555p-rooki, fra-9375f-budget-2, fra-9334-budget-3, ams-9575f-vulpes, ams-9575f-odessana

    • resolved · Aug 27, 2026, 12:48 PM UTC

      During planned maintenance affecting five cluster nodes in our fra-9950X cluster, the data center power phase was brought down as scheduled. Due to the interaction between the motherboard firmware and the redundant power supply configuration used on these servers, the motherboards locked CPU frequency to 600 MHz. This caused severe performance degradation and VM outages for customers hosted on the affected nodes. Affected cluster nodes: fra-9275f-odessana fra-9555p-rooki fra-9375f-budget-2 fra-9334-budget-3 Separately and unrelated to the incident above, our Netherlands location experienced an issue with the VM platform that caused a partial networking malfunction, resulting in outages on: ams-9575f-vulpes ams-9575f-odessana This has already been resolved and no further action is required. ℹ️ This is an unplanned incident. No action is required from customers at this time. We will automatically provide two extra days of service to all impacted customers as compensation for this incident. We sincerely apologize for the inconvenience. This incident was not something we could have anticipated. The issue has already been resolved, and our team has restored full performance across all affected nodes. Thank you for your patience and understanding.

    Latest: During planned maintenance affecting five cluster nodes in our fra-9950X cluster, the data center power phase was brought down as scheduled. Due to the interaction between the moth…

Incident record

Since October 2026 · Hyperping · 31 components checked every 5 minutes
19incidents recorded
19last 12 months
4last 90 days
32 hourstypical duration, 12 months

The longest incident in the last year, Network Degradation in 🇳🇱 Netherlands on January 25, 2026, ran for 16 days. 9 maintenance windows announced in the same period.

Most affected components, last 12 months

  • 🇩🇪 SNK Germany, Frankfurt am Main2
  • 🇩🇪 SNK ns1.senkodns.net2
  • 🇫🇮 SNK Edge Router 12
  • 🇫🇮 SNK Finland, Helsinki2
  • 🇫🇮 SNK ns2.senkodns.net2

Latest incidents

  • Emergency disk replacement on fra-9575f-culpaeus October 21, 2026 · 36 minutes · major outage

    We are currently performing an emergency replacement of a failed NVMe drive in this node's RAID array. All customer data is safe and intact. Affected VMs will…

  • [Post-Mortem] VMmanager Security Incident October 17, 2026 · 2 days · degraded service

    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…

  • ams-9950x-odessana outage August 31, 2026 · 5 hours · major outage

    We are investigating the issue on the ams-9950x-odessana node in the Netherlands.

Outage history

Past 90 days · 4 incidents View full outage history →