This afternoon, from about 3:00pm to 3:30pm NZST (1:00–1:30pm AEST), some Nectar services in the Auckland availability zone were disrupted. The problem is resolved and all services are working normally.
What you may have noticed
- Launching, deleting, resizing or otherwise managing Auckland instances through the dashboard or command line may have failed or returned errors.
- Instances that were launched or rebooted during this time may not have started up correctly, for example missing their SSH key or initial setup.
What was not affected
- Instances that were already running kept running. Their network access, volumes and data were not affected.
What happened
We made a security certificate update to one of our internal systems. It turned out not to be compatible with the way the central Nectar services connect to Auckland. Once we identified the cause we reversed the change, and services recovered straight away.
What you need to do
In most cases, nothing. If you launched an Auckland instance between 3:00pm and 3:30pm and it is in an Error state or not behaving as expected, try rebooting it, or delete and relaunch it. If an action failed during that time, simply try it again.
If you are still having trouble, contact us through the Nectar helpdesk and we'll help.
We apologise for the inconvenience.
Completed
Significant
Last modification at:
Mon, 21 Sep 2026 3:40a.m. (UTC)
Change reverted. All solved now.
Update posted
1 month, 1 week ago.
problem solved , just for recording.
Update posted
1 month, 1 week ago.