Damn, is it down?

All services / Cloud & developer

bigleaf.net · Cloud & developer

Is BigLeaf down?

Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.

What's broken? (optional)
Is it just me?
No problems detected

Live diagnosis

Is it just me?

Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.

Your browser → bigleaf.net—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—

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.

Live outage map

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.

User reports

0

Near baseline. 0 in the last hour. Typical hour is about 0.

Our checks

Reaching it

Last check reached it in 266 ms · 6 min ago.

Reports and checks

Reports compared with the typical volume, with check latency and failures overlaid10650 ms15:3021:3003:3009:1515:15
ReportsTypical baselineCheck latencyFailed checkTimes in UTC
Numbers behind the chart
Time (UTC)ReportsBaselineLatencyFailed checks
03:3000.0455 ms0
03:4500.0479 ms0
04:0000.0367 ms0
04:1500.0405 ms0
04:3000.0212 ms0
04:4500.0335 ms0
05:0000.0393 ms0
05:1500.0405 ms0
05:3000.0403 ms0
05:4500.0297 ms0
06:0000.0261 ms0
06:1500.0465 ms0
06:3000.0254 ms0
06:4500.0249 ms0
07:0000.0230 ms0
07:1500.0280 ms0
07:3000.0512 ms0
07:4500.0342 ms0
08:0000.077 ms0
08:1500.0194 ms0
08:3000.0531 ms0
08:4500.0253 ms0
09:0000.0406 ms0
09:1500.0210 ms0
09:3000.0274 ms0
09:4500.0484 ms0
10:0000.0238 ms0
10:1500.0125 ms0
10:3000.0155 ms0
10:4500.0186 ms0
11:0000.0412 ms0
11:1500.0433 ms0
11:3000.0360 ms0
11:4500.0589 ms0
12:0000.0134 ms0
12:1500.0461 ms0
12:3000.0305 ms0
12:4500.0554 ms0
13:0000.0650 ms0
13:1500.0271 ms0
13:3000.0273 ms0
13:4500.0295 ms0
14:0000.0620 ms0
14:1500.0292 ms0
14:3000.0236 ms0
14:4500.0189 ms0
15:0000.0496 ms0
15:1500.0266 ms0

Reliability

Score 100/100 · grade A

100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage

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.

BigLeaf status badge Embed a live BigLeaf status badge

Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server

BigLeaf status and 30-day uptime badge

Past outages

No outages on record for BigLeaf yet. Outages of 10 minutes or more get their own page here.

All BigLeaf outages · Every recent outage

Having trouble with BigLeaf?

One report per service every 10 minutes from this network. No account.

What's broken? (optional)

Notes are stored for rate-limit context and are not shown publicly.

Questions

Is BigLeaf down right now?

Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.

BigLeaf not working for me but the status is fine. What now?

If BigLeaf 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 BigLeaf's side.

How does Damn is it down decide BigLeaf's status?

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.

How often is BigLeaf checked?

About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.