Critical October 20, 2026 - Detected by Pingoru
- Oct 20, 2026, 01:07 AM UTC
- Resolved
- Oct 20, 2026, 02:39 AM UTC
- Duration
- 1h 32m
Affected: Website
Timeline · 3 updates
-
investigating Oct 20, 2026, 01:07 AM UTC
The team are currently investigating a hardware issue on an internal hardware node which is impacting the SiteHost website, our Knowledge Base and some supplemental services such as paste.sitehost.nz. If you need to access the SiteHost control panel you should still be able to access it via cp.sitehost.nz
-
monitoring Oct 20, 2026, 02:30 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 20, 2026, 02:39 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 26, 2026, 06:57 PM UTC
- Resolved
- Sep 27, 2026, 12:28 AM UTC
- Duration
- 5h 30m
Affected: DE - FRA01DE - FRA01
Timeline · 3 updates
-
identified Sep 26, 2026, 06:57 PM UTC
We have seen some intermittent connectivity issues to some of our services in the FRA01 data center and we are closely monitoring the situation with our upstream providers.
-
monitoring Sep 26, 2026, 07:21 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 27, 2026, 12:28 AM UTC
Our providers have stated that everything is at full operation in FRA01 and our monitoring shows a stable connection.
Read the full incident report →
- Detected by Pingoru
- Sep 25, 2026, 01:54 AM UTC
- Resolved
- Sep 25, 2026, 05:18 AM UTC
- Duration
- 3h 23m
Affected: Domains
Timeline · 3 updates
-
identified Sep 25, 2026, 01:54 AM UTC
Our upstream provider InternetNZ has identified an issue at their end impacting multiple registrars. They have a status page up here with more information: https://status.internetnz.nz/incidents/mw4lt67vz5t4 This affects domain registrations, renewals, transfers, and WHOIS lookups.
-
monitoring Sep 25, 2026, 02:42 AM UTC
InternetNZ have said a fix has been applied, they are monitoring system transactions and zone generations.
-
resolved Sep 25, 2026, 05:18 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 21, 2026, 09:20 PM UTC
- Resolved
- Sep 21, 2026, 11:29 PM UTC
- Duration
- 2h 9m
Affected: Domains
Timeline · 5 updates
-
investigating Sep 21, 2026, 09:20 PM UTC
We're investigating an issue affecting all .nz domains. Registrations, renewals and transfers are currently unavailable. We'll update this notice as soon as we know more.
-
investigating Sep 21, 2026, 09:20 PM UTC
We are continuing to investigate this issue.
-
identified Sep 21, 2026, 10:01 PM UTC
Our upstream supplier InternetNZ has identified an issue at their end impacting multiple registrars. We're in contact with them and are awaiting a resolution (https://status.internetnz.nz/incidents/0lpv5xvhd2wr)
-
monitoring Sep 21, 2026, 10:22 PM UTC
InternetNZ have implemented a fix and .nz functionality has been restored. We'll continue monitoring closely, but registrations, renewals and transfers should all be working correctly now.
-
resolved Sep 21, 2026, 11:29 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 15, 2026, 02:12 AM UTC
- Resolved
- Sep 15, 2026, 03:40 AM UTC
- Duration
- 1h 27m
Affected: NZ – AKL01
Timeline · 3 updates
-
identified Sep 15, 2026, 02:12 AM UTC
We've identified a hardware issue with the NZ-AKL1-V0P385 node, and we're performing an emergency shutdown. Servers on this hardware node will be unavailable during this time. For any emergency queries please email us at [email protected]
-
monitoring Sep 15, 2026, 02:42 AM UTC
We've identified a faulty component in the hardware node and it's been replaced. Servers on this node should be coming back online now, and we are continuing to monitor the situation. If you're still experiencing issues please email us at [email protected]
-
resolved Sep 15, 2026, 03:40 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 06, 2026, 11:08 PM UTC
- Resolved
- Sep 06, 2026, 11:33 PM UTC
- Duration
- 24m
Timeline · 2 updates
-
investigating Sep 06, 2026, 11:08 PM UTC
We are currently experiencing delays in receiving support tickets. Our team is aware and working to resolve this as quickly as possible. Please be assured that your existing services are unaffected, customer servers, websites and email are operating normally. For urgent issues, please call us: 0800 484 537
-
resolved Sep 06, 2026, 11:33 PM UTC
We have identified and fixed the issue and the tickets are now being delivered normally.
Read the full incident report →
- Detected by Pingoru
- Jul 06, 2026, 03:30 AM UTC
- Resolved
- Jul 06, 2026, 04:07 AM UTC
- Duration
- 37m
Affected: NZ – AKL01NZ – AKL01NZ – AKL02NZ – AKL02NZ – AKL03NZ – AKL03AU – SYD01AU – SYD01
Timeline · 3 updates
-
identified Jul 06, 2026, 03:30 AM UTC
We're currently experiencing upstream network issues between SiteHost and overseas data centres that may be impacting some customers. Our team is investigating and we will post more information as it comes available.
-
monitoring Jul 06, 2026, 03:40 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 06, 2026, 04:07 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 30, 2026, 05:56 PM UTC
- Resolved
- Jul 01, 2026, 01:44 AM UTC
- Duration
- 7h 48m
Timeline · 3 updates
-
investigating Jun 30, 2026, 05:56 PM UTC
We are aware of an issue with the US-CAL1-93PN5L hardware node affecting guests. Our engineers are currently investigating the issue and working to get this back up as soon as possible.
-
monitoring Jun 30, 2026, 06:50 PM UTC
All servers are back up and running on the affected node and we are continuing to monitor for further issues.
-
resolved Jul 01, 2026, 01:44 AM UTC
The node and guests have remained stable and we will continue to monitor for further issues. If you are still having issues with a guest on this node please get in touch at [email protected].
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2026, 01:51 AM UTC
- Resolved
- Jun 18, 2026, 03:20 AM UTC
- Duration
- 1h 28m
Affected: NZ – AKL01
Timeline · 3 updates
-
investigating Jun 18, 2026, 01:51 AM UTC
We are aware of an issue with the NZ-AKL1-VEPQQR hardware node affecting guests. Our engineers are currently investigating the issue and working to get this back up as soon as possible.
-
monitoring Jun 18, 2026, 02:45 AM UTC
All servers are back up and running on the affected node and we are continuing to monitor for further issues.
-
resolved Jun 18, 2026, 03:20 AM UTC
The node and guests have remained stable and we will continue to monitor for further issues. If you are still having issues with a guest on this node please get in touch at [email protected].
Read the full incident report →
- Detected by Pingoru
- May 29, 2026, 12:56 AM UTC
- Resolved
- Jun 10, 2026, 12:03 AM UTC
- Duration
- 11d 23h
Timeline · 5 updates
-
investigating May 29, 2026, 12:56 AM UTC
We’re currently investigating an issue affecting customers using Starlink internet connections who are unable to reach our services. Our monitoring shows that traffic from Starlink networks is not currently being correctly routed to our infrastructure, which is preventing normal connectivity. This appears to be a routing issue outside of our direct control. Our network team is actively investigating possible mitigation and working with upstream networks to restore normal access as quickly as possible. Customers using other internet providers are not affected at this time. We will provide further updates as more information becomes available.
-
monitoring Jun 03, 2026, 03:18 AM UTC
Starlink has confirmed a routing adjustment on their side to resolve an issue that was impacting connectivity to our services. Their traffic is now being directed via an alternate path, and initial monitoring shows restored access. We are continuing to monitor the situation closely to ensure stability. If you continue to experience issues from Starlink connections, please let us know.
-
identified Jun 05, 2026, 01:01 AM UTC
The routing issue with Starlink has recurred. Starlink customers based in the South Island are currently unable to access services hosted on our network. This is a routing issue outside of our control. We recommend that affected users raise this with Starlink. We're continuing to reach out to them directly, and our networking team are investigating what mitigations we can take from our end. In the meantime, we'd advise affected users to use a VPN or another internet connection as a workaround. Sites behind a CDN such as Cloudflare should be unaffected by this issue.
-
monitoring Jun 06, 2026, 09:37 PM UTC
Starlink has made further adjustments on their end and customers are reporting a stable connection throughout the night. We are monitoring the situation closely and are working with Starlink and our upstream providers to reduce the likelihood of this recurring. If you are still experiencing connectivity issues please let us know.
-
resolved Jun 10, 2026, 12:03 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 25, 2026, 06:08 AM UTC
- Resolved
- May 25, 2026, 09:28 PM UTC
- Duration
- 15h 20m
Affected: APIControl PanelNZ – AKL02NZ – AKL02NZ – AKL02NZ – AKL02NZ – AKL02NZ – AKL02
Timeline · 5 updates
-
investigating May 25, 2026, 06:08 AM UTC
We have experienced an unplanned network outage affecting our customers in the AKL02 region. Our engineers are currently investigating. We will share additional updates as we have more information.
-
monitoring May 25, 2026, 06:28 AM UTC
The services have now been restored and we are actively monitoring the situation. If you have any persistent issues, please contact [email protected]
-
investigating May 25, 2026, 07:16 AM UTC
We have experienced another network outage affecting our customers in the AKL02 region. Our engineers are currently investigating this outage. We will share additional updates as we have more information.
-
monitoring May 25, 2026, 10:11 AM UTC
The services have now been restored and we are actively monitoring the situation. If you have any persistent issues, please contact [email protected]
-
resolved May 25, 2026, 09:28 PM UTC
Monitoring over the past few hours has confirmed this specific AKL02 network issue is resolved.
Read the full incident report →
- Detected by Pingoru
- May 25, 2026, 12:02 AM UTC
- Resolved
- May 27, 2026, 10:06 PM UTC
- Duration
- 2d 22h
Affected: IMAPAPIName Server 1NZ – AKL01NZ – AKL01NZ – AKL01NZ – AKL01NZ – AKL01NZ – AKL01Control PanelName Server 2POP3NZ – AKL02NZ – AKL02NZ – AKL02NZ – AKL02NZ – AKL02NZ – AKL02Name Server 3WebmailNZ – AKL03NZ – AKL03NZ – AKL03NZ – AKL03NZ – AKL03NZ – AKL03AU – SYD01AU – SYD01AU – SYD01US – CAL01AU – SYD01AU – SYD01UK – LDN01US - CAL01SG – SGP01DE - FRA01AU – SYD01DE - FRA01WebsiteDomains
Timeline · 15 updates
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 11:47 PM UTC
- Resolved
- Mar 20, 2026, 02:15 AM UTC
- Duration
- 2h 28m
Affected: NZ – AKL01
Timeline · 4 updates
-
investigating Mar 19, 2026, 11:47 PM UTC
We are aware of an issue with the NZ-AKL1-6O53ER hardware node affecting guests. Our engineers are currently investigating the issue and working to get this back up as soon as possible.
-
identified Mar 20, 2026, 12:53 AM UTC
We’ve identified a hardware issue affecting the node and are currently in the process of replacing the faulty component. Our engineering team is actively working to restore services as quickly as possible.
-
monitoring Mar 20, 2026, 01:25 AM UTC
The faulty hardware component has been replaced, and the node has been brought back online. All servers on the affected node are now operational, and we are continuing to monitor the environment closely for any further issues. Please don't hesitate to reach out if you notice any issues.
-
resolved Mar 20, 2026, 02:15 AM UTC
The hardware node and associated services have remained stable. We will continue to monitor the situation closely. If you experience any further issues with a server on this node, please contact us at [email protected]
Read the full incident report →
- Detected by Pingoru
- Feb 02, 2026, 04:04 PM UTC
- Resolved
- Feb 02, 2026, 08:17 PM UTC
- Duration
- 4h 13m
Affected: Name Server 1Name Server 2Name Server 3
Timeline · 3 updates
-
identified Feb 02, 2026, 04:04 PM UTC
We are aware of ongoing issues with our DNS services due to denial of service attack. We are working to mitigate the issues. This service degradation may result in intermittent issues resolving services that are using SiteHost DNS servers on or outside of our network.
-
monitoring Feb 02, 2026, 06:46 PM UTC
We have implemented some mitigations and the DNS service appears to now be stable. If you are experiencing ongoing issues with SiteHost DNS resolution please get in touch.
-
resolved Feb 02, 2026, 08:17 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 25, 2025, 08:02 PM UTC
- Resolved
- Dec 25, 2025, 11:40 PM UTC
- Duration
- 3h 38m
Affected: US – CAL01US - CAL01
Timeline · 4 updates
-
investigating Dec 25, 2025, 08:02 PM UTC
We are aware of a networking issue at present that is affecting traffic to our California Data Center (CAL01), this could lead to degraded connectivity or increased latency for servers located in CAL01. We are working with our upstream providers to get this resolved.
-
monitoring Dec 25, 2025, 10:38 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Dec 25, 2025, 10:38 PM UTC
We are continuing to monitor for any further issues.
-
resolved Dec 25, 2025, 11:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 27, 2025, 09:36 PM UTC
- Resolved
- Nov 27, 2025, 10:05 PM UTC
- Duration
- 29m
Affected: Website
Timeline · 4 updates
-
investigating Nov 27, 2025, 09:36 PM UTC
Currently, we are experiencing an outage on some internal hardware nodes, which is affecting our website, knowledge base, API documentation, and other services. Engineers are actively working on resolving the issue. No customer servers, containers, or websites are impacted and our Control Panel and API are working as expected.
-
monitoring Nov 27, 2025, 09:52 PM UTC
We have restored the nodes and all of our impacted services are back online. We're monitoring the health of the nodes and conducting further investigations.
-
monitoring Nov 27, 2025, 10:01 PM UTC
We are continuing to monitor for any further issues.
-
resolved Nov 27, 2025, 10:05 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 12:52 PM UTC
- Resolved
- Nov 18, 2025, 07:31 PM UTC
- Duration
- 6h 39m
Timeline · 3 updates
-
identified Nov 18, 2025, 12:52 PM UTC
We are aware of an issue with Cloudflare. They are investigating issues with their services and/or network. More details on this can be found here: https://www.cloudflarestatus.com/
-
monitoring Nov 18, 2025, 02:46 PM UTC
We have observed the fix that has been rolled out by Cloudflare is propagating. We are actively monitoring the situation. If you are still experiencing any issues please reach out to us on [email protected]
-
resolved Nov 18, 2025, 07:31 PM UTC
Cloudflare have indicated that their services are considered stable. For further information, please see the Cloudflare status page for the event: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
Read the full incident report →
- Detected by Pingoru
- Oct 23, 2025, 11:51 AM UTC
- Resolved
- Oct 23, 2025, 12:47 PM UTC
- Duration
- 55m
Affected: Name Server 3DE - FRA01
Timeline · 3 updates
-
investigating Oct 23, 2025, 11:51 AM UTC
We are aware of an issue with our high performance hardware nodes in FRA01 affecting guests. Our engineers are currently investigating the issue and working to get this back up as soon as possible.
-
monitoring Oct 23, 2025, 12:13 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 23, 2025, 12:47 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 24, 2025, 08:30 PM UTC
- Resolved
- Sep 24, 2025, 10:55 PM UTC
- Duration
- 2h 25m
Timeline · 4 updates
-
identified Sep 24, 2025, 08:30 PM UTC
We have experienced some hardware node instability issues with one of the nodes (NZ-AKL2-6O20W9). As a result, we need to perform emergency maintenance to reduce the likelihood of future issues. This will involve rebooting the servers on this node.
-
monitoring Sep 24, 2025, 08:57 PM UTC
We have completed the emergency maintenance and are currently monitoring the situation. All services hosted on the node should be restored.
-
resolved Sep 24, 2025, 10:55 PM UTC
The node and guests have remained stable and we will continue to monitor for further issues. If you are still having issues with a guest on this node please get in touch at [email protected].
-
postmortem Sep 24, 2025, 10:59 PM UTC
**Summary** This morning **at 8:30 AM**, one of our monitoring systems alerted us to a problem with the storage service on a node. This caused disruption for the virtual machines \(VMs\) running on that hardware. **Timeline** * **8:30 AM** – Monitoring detected the issue. * **8:45 AM** – Our team determined a reboot was the fastest way to restore service. * **8:55 AM** – The node was rebooted and VMs began coming back online. * **11:00 AM** – Services confirmed stable; incident closed. **Cause** The disruption was traced to a **faulty hard drive** in the storage system. **Resolution** The faulty drive was removed and replaced. The storage service has remained stable since, and no further issues are expected. **Next Steps** We are improving monitoring and alerting to catch early signs of drive degradation sooner, helping us prevent similar issues in the future. **Current Status** All services are fully operational.
Read the full incident report →
- Detected by Pingoru
- Aug 14, 2025, 08:09 AM UTC
- Resolved
- Aug 14, 2025, 01:39 PM UTC
- Duration
- 5h 30m
Affected: NZ – AKL01NZ – AKL01
Timeline · 3 updates
-
identified Aug 14, 2025, 08:09 AM UTC
We’ve had a hardware failure on one of our core distribution switches in the AKL01 data centre. To restore full network redundancy and capacity, we’ll be carrying out emergency maintenance tonight at 11:00 PM NZST. We’re not expecting downtime, but you may notice brief periods of higher latency or reduced performance during the work. If you experience any issues accessing services, please contact us at [email protected].
-
monitoring Aug 14, 2025, 11:36 AM UTC
The core network issue in the AKL01 data centre has been resolved and full redundancy has been restored. We are actively monitoring the network to ensure stability and normal performance.
-
resolved Aug 14, 2025, 01:39 PM UTC
The core network issue in the AKL01 data centre has been fully resolved. Services have remained stable, and monitoring confirms normal performance. If you experience any issues accessing services, please contact us at [email protected].
Read the full incident report →
- Detected by Pingoru
- Jul 21, 2025, 10:23 PM UTC
- Resolved
- Jul 22, 2025, 05:55 AM UTC
- Duration
- 7h 31m
Affected: NZ – AKL01NZ – AKL01NZ – AKL01NZ – AKL02NZ – AKL02NZ – AKL02NZ – AKL03NZ – AKL03NZ – AKL03AU – SYD01AU – SYD01US – CAL01UK – LDN01US - CAL01SG – SGP01DE - FRA01AU – SYD01DE - FRA01
Timeline · 3 updates
-
identified Jul 21, 2025, 10:23 PM UTC
We have become aware of an issue affecting automated SSL renewal/issuance on Cloud Containers and Servers that are using LetsEncrypt. They are currently dealing with the incident and we will be monitoring the status and keeping you posted as the situation develops.
-
monitoring Jul 22, 2025, 03:13 AM UTC
LetsEncrypt has implemented a fix which means certificate renewals should start working again. Keep in mind that they are experiencing higher than average traffic volumes so there may still be some delays in certificate renewal/issuing.
-
resolved Jul 22, 2025, 05:55 AM UTC
All of our services appear to be operating correctly, LetsEncrypt is currently monitoring the status of their API.
Read the full incident report →
- Detected by Pingoru
- Jun 27, 2025, 03:09 AM UTC
- Resolved
- Jul 06, 2025, 09:33 PM UTC
- Duration
- 9d 18h
Affected: NZ – AKL01
Timeline · 4 updates
-
monitoring Jun 27, 2025, 03:09 AM UTC
We experienced intermittent network connectivity issues affecting guests hosted on node NZ-AKL1-6G2QEQ, starting around 1:00 PM. This was due to a targeted DDOS attack on the node, resulting in brief network flaps for some customers in the affected zone. The issue was mitigated, and as of 2:12 PM, network performance has returned to normal. We are continuing to monitor the situation closely to ensure ongoing stability. If you continue to experience any issues, please don’t hesitate to reach out to us at [email protected].
-
investigating Jun 27, 2025, 03:25 AM UTC
We are seeing some network connectivity issues again. Our team is actively investigating and working to identify the source of this recurrence, which may be related to the earlier DDOS activity. We’ll provide further updates as we progress with mitigation. We appreciate your patience and understanding while we work to restore full stability.
-
monitoring Jun 27, 2025, 04:30 AM UTC
Network performance has returned to normal. We are continuing to monitor the situation closely.
-
resolved Jul 06, 2025, 09:33 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 12, 2025, 10:38 PM UTC
- Resolved
- May 13, 2025, 01:40 AM UTC
- Duration
- 3h 1m
Timeline · 3 updates
-
identified May 12, 2025, 10:38 PM UTC
We are aware of an ongoing DNS outage affecting domains configured with nameservers pointing to Freeparking. This is causing websites, email services, and other dependent systems to become inaccessible or unreliable. If you'd like to transfer your domains and DNS over to us, you can reach out to us at [email protected] for assistance.
-
monitoring May 12, 2025, 11:01 PM UTC
DNS services for domains using Freeparking nameservers appear to be back online now. As this outage originated from Freeparking's infrastructure, it was outside our control. We are continuing to monitor the situation in case of any further disruptions.
-
resolved May 13, 2025, 01:40 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2025, 11:54 PM UTC
- Resolved
- Mar 07, 2025, 03:18 AM UTC
- Duration
- 3h 24m
Affected: NZ – AKL02
Timeline · 3 updates
-
investigating Mar 06, 2025, 11:54 PM UTC
We are aware of an issue affecting several of our hardware nodes in the AKL02 region, and are working to get this back up as soon as possible.
-
monitoring Mar 07, 2025, 01:24 AM UTC
We've identified an issue with the power supply in one of our cabinets in the AKL02 datacentre. We've restored the services, but will be keeping a close eye on it.
-
resolved Mar 07, 2025, 03:18 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 26, 2025, 12:39 AM UTC
- Resolved
- Feb 26, 2025, 08:33 AM UTC
- Duration
- 7h 54m
Timeline · 3 updates
-
identified Feb 26, 2025, 12:39 AM UTC
We are aware of an issue within the Spark network at present that is affecting traffic passing through Cloudflare towards our network for Spark customers. We are currently working with Cloudflare to help get this resolved but as the issue is within Spark's network we have limited remediation options at present. We recommend you contact Spark directly to help expedite a solution to the issues within their network. Alternatively, Cloudflare can temporarily be paused by following the steps: https://developers.cloudflare.com/fundamentals/setup/manage-domains/pause-cloudflare/
-
monitoring Feb 26, 2025, 04:24 AM UTC
We believe this issue should be resolved, if you were affected please re-test now and contact our support team if you're still experiencing issues. Additionally, if you temporarily disabled Cloudflare because of this, it should now be safe to re-enable and test.
-
resolved Feb 26, 2025, 08:33 AM UTC
This incident has been resolved.
Read the full incident report →
