Binary Lane Outage History
Binary Lane is up right nowBinary Lane had 5 outages in the last 2 years totaling 1385h 35m of downtime — averaging 0.2 incidents per month.
There were 5 Binary Lane outages since August 1, 2025 totaling 1385h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.
sydcompute98 host outage
Timeline · 4 updates
- investigating May 10, 2026, 04:26 AM UTC
We are currently investigating this issue.
- identified May 10, 2026, 04:34 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring May 10, 2026, 04:43 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 10, 2026, 06:07 AM UTC
This incident has been resolved.
sydcompute38 host outage
Timeline · 4 updates
- investigating Apr 24, 2026, 10:57 AM UTC
We are currently investigating this issue.
- identified Apr 24, 2026, 11:01 AM UTC
This host node has encountered an irrecoverable hardware fault. We will begin restoring affected servers from latest backup (if purchased) or fresh OS installation shortly.
- monitoring Apr 24, 2026, 11:16 AM UTC
Restore/reinstall of affected servers is underway.
- resolved Apr 25, 2026, 02:24 AM UTC
This incident has been resolved.
Unscheduled VPS host outage in Sydney
Timeline · 5 updates
- investigating Mar 09, 2026, 04:51 AM UTC
We are currently investigating this issue.
- investigating Mar 09, 2026, 04:51 AM UTC
We are continuing to investigate this issue.
- identified Mar 09, 2026, 05:30 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Mar 09, 2026, 06:28 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 09, 2026, 07:03 AM UTC
This incident has been resolved.
melcompute18 host outage
Timeline · 4 updates
- investigating Aug 01, 2025, 12:51 AM UTC
We are currently investigating this issue.
- identified Aug 01, 2025, 02:14 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Aug 01, 2025, 05:25 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Aug 04, 2025, 01:16 AM UTC
This incident has been resolved.