Binary Lane status history
Current state: operational — “All Systems Operational” per http://status.binarylane.com.au (Atlassian Statuspage), checked 2026-09-24 12:28 UTC.
How long do Binary Lane incidents last?
From 5 incidents with a vendor-posted start and resolve time. Longest on record: Internet connectivity interruption — 53.9 days (2026-05-15 03:19 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (5)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-16 21:46 UTC | sydcompute(52-57) sydcomr06s(01-08,17-24,33-40) host outage | resolved | major | 6 d 3 h |
| 2026-05-15 03:19 UTC | Internet connectivity interruption | resolved | major | 53 d 21 h |
| 2026-05-10 04:26 UTC | sydcompute98 host outage | resolved | major | 1 h 40 min |
| 2026-04-24 10:57 UTC | sydcompute38 host outage | resolved | major | 15 h 26 min |
| 2026-03-09 04:51 UTC | Unscheduled VPS host outage in Sydney | resolved | major | 2 h 11 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Binary Lane with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"binary-lane"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
