User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
binarylane.com.au · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 594 ms · 8 min ago.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 06:00 | 0 | 0.0 | 1153 ms | 0 |
| 06:15 | 0 | 0.0 | 995 ms | 0 |
| 06:30 | 0 | 0.0 | 890 ms | 0 |
| 06:45 | 0 | 0.0 | 624 ms | 0 |
| 07:00 | 0 | 0.0 | 594 ms | 0 |
| 07:15 | 0 | 0.0 | 769 ms | 0 |
| 07:30 | 0 | 0.0 | 1496 ms | 0 |
| 07:45 | 0 | 0.0 | 704 ms | 0 |
| 08:00 | 0 | 0.0 | 1072 ms | 0 |
| 08:15 | 0 | 0.0 | 666 ms | 0 |
| 08:30 | 0 | 0.0 | 669 ms | 0 |
| 08:45 | 0 | 0.0 | 667 ms | 0 |
| 09:00 | 0 | 0.0 | 1014 ms | 0 |
| 09:15 | 0 | 0.0 | 1014 ms | 0 |
| 09:30 | 0 | 0.0 | 1090 ms | 0 |
| 09:45 | 0 | 0.0 | 491 ms | 0 |
| 10:00 | 0 | 0.0 | 821 ms | 0 |
| 10:15 | 0 | 0.0 | 639 ms | 0 |
| 10:30 | 0 | 0.0 | 688 ms | 0 |
| 10:45 | 0 | 0.0 | 739 ms | 0 |
| 11:00 | 0 | 0.0 | 1003 ms | 0 |
| 11:15 | 0 | 0.0 | 879 ms | 0 |
| 11:30 | 0 | 0.0 | 1022 ms | 0 |
| 11:45 | 0 | 0.0 | 1422 ms | 0 |
| 12:00 | 0 | 0.0 | 741 ms | 0 |
| 12:15 | 0 | 0.0 | 770 ms | 0 |
| 12:30 | 0 | 0.0 | 1133 ms | 0 |
| 12:45 | 0 | 0.0 | 755 ms | 0 |
| 13:00 | 0 | 0.0 | 2128 ms | 0 |
| 13:15 | 0 | 0.0 | 839 ms | 0 |
| 13:30 | 0 | 0.0 | 579 ms | 0 |
| 13:45 | 0 | 0.0 | 745 ms | 0 |
| 14:00 | 0 | 0.0 | 703 ms | 0 |
| 14:15 | 0 | 0.0 | 812 ms | 0 |
| 14:30 | 0 | 0.0 | 524 ms | 0 |
| 14:45 | 0 | 0.0 | 933 ms | 0 |
| 15:00 | 0 | 0.0 | 1013 ms | 0 |
| 15:15 | 0 | 0.0 | 1010 ms | 0 |
| 15:30 | 0 | 0.0 | 623 ms | 0 |
| 15:45 | 0 | 0.0 | 893 ms | 0 |
| 16:00 | 0 | 0.0 | 591 ms | 0 |
| 16:15 | 0 | 0.0 | 693 ms | 0 |
| 16:30 | 0 | 0.0 | 731 ms | 0 |
| 16:45 | 0 | 0.0 | 913 ms | 0 |
| 17:00 | 0 | 0.0 | 723 ms | 0 |
| 17:15 | 0 | 0.0 | 831 ms | 0 |
| 17:30 | 0 | 0.0 | 1007 ms | 0 |
| 17:45 | 0 | 0.0 | 594 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Binary Lane yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Binary Lane goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Binary Lane alerts to Slack, Discord or a webhook — free.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
If Binary Lane is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Binary Lane's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.