Earlier this morning an unexpected database issue interrupted Nectar's control-plane services during the planned maintenance window. You may have seen:
• 500 / 503 errors when signing in to the Dashboard, Jupyter Notebook Service, BinderHub or Virtual Desktop Service
• Failed API or CLI calls for actions such as launching instances, attaching volumes or creating DNS records
What wasn't affected
• Running virtual machines and network traffic
• Stored data in volumes, Swift/S3 buckets or object storage
• Existing long-lived API tokens (workloads already in progress continued normally)
Current status
All authentication and control-plane endpoints are back online and operating normally. At this point, we have no evidence of data loss or impact to running workloads.
Our engineers are reviewing logs to confirm the precise trigger and will post a further update once the root cause analysis is complete.
If you continue to encounter errors, please retry after a few minutes. Persistent issues can be logged via support@ehelp.edu.au with the approximate time and API/command you were using.
Thank you for your patience while we completed the recovery.
Completed
Minimal
Last modification at:
Wed, 16 Jul 2025 1:03a.m. (UTC)
Services are operating normally
Update posted
1 year, 3 months ago.
Outage resolved, investigation of root cause underway
Update posted
1 year, 3 months ago.