Damn, is it down?

All services / Cloud & developer

section.io · Cloud & developer

Is Section 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 → section.io—
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 479 ms · 8 min ago.

Reports and checks

Reports compared with the typical volume, with check latency and failures overlaid101671 ms17:1523:1505:1511:0017:00
ReportsTypical baselineCheck latencyFailed checkTimes in UTC
Numbers behind the chart
Time (UTC)ReportsBaselineLatencyFailed checks
05:0000.0451 ms0
05:1500.01477 ms0
05:3000.0447 ms0
05:4500.0961 ms0
06:0000.0378 ms0
06:1500.0468 ms0
06:3000.01115 ms0
06:4500.0717 ms0
07:0000.0395 ms0
07:1500.01289 ms0
07:3000.0651 ms0
07:4500.0388 ms0
08:0000.0725 ms0
08:1500.0307 ms0
08:3000.01071 ms0
08:4500.0976 ms0
09:0000.0339 ms0
09:1500.01099 ms0
09:3000.0606 ms0
09:4500.0440 ms0
10:0000.0798 ms0
10:1500.0356 ms0
10:3000.0559 ms0
10:4500.0424 ms0
11:0000.0518 ms0
11:1500.0340 ms0
11:3000.0646 ms0
11:4500.0440 ms0
12:0000.0368 ms0
12:1500.0520 ms0
12:3000.0896 ms0
12:4500.0446 ms0
13:0000.0504 ms0
13:1500.0453 ms0
13:3000.01465 ms0
13:4500.01015 ms0
14:0000.0988 ms0
14:1500.0389 ms0
14:3000.0890 ms0
14:4500.01070 ms0
15:0000.0375 ms0
15:1500.01082 ms0
15:3000.0448 ms0
15:4500.0351 ms0
16:0000.01111 ms0
16:1500.0483 ms0
16:3000.01671 ms0
16:4500.0462 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.

Section status badge Embed a live Section status badge

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

Section status and 30-day uptime badge

Past outages

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

All Section outages · Every recent outage

Having trouble with Section?

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 Section down right now?

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

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

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

How does Damn is it down decide Section'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 Section checked?

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