User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
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.
Live diagnosis
Is it just me?
Tests section.io from your browser and compares it with our checks, the official status, and user reports.
Your browser → section.io—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
Press Run testNothing leaves your browser except a request to the site and to us.
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.
What's broken
Our checks
Reaching it
Last check reached it in 419 ms · 8 min ago.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:15 | 0 | 0.0 | 540 ms | 0 |
| 03:30 | 0 | 0.0 | 1217 ms | 0 |
| 03:45 | 0 | 0.0 | 652 ms | 0 |
| 04:00 | 0 | 0.0 | 547 ms | 0 |
| 04:15 | 0 | 0.0 | 1161 ms | 0 |
| 04:30 | 0 | 0.0 | 1530 ms | 0 |
| 04:45 | 0 | 0.0 | 438 ms | 0 |
| 05:00 | 0 | 0.0 | 451 ms | 0 |
| 05:15 | 0 | 0.0 | 1477 ms | 0 |
| 05:30 | 0 | 0.0 | 447 ms | 0 |
| 05:45 | 0 | 0.0 | 961 ms | 0 |
| 06:00 | 0 | 0.0 | 378 ms | 0 |
| 06:15 | 0 | 0.0 | 468 ms | 0 |
| 06:30 | 0 | 0.0 | 1115 ms | 0 |
| 06:45 | 0 | 0.0 | 717 ms | 0 |
| 07:00 | 0 | 0.0 | 395 ms | 0 |
| 07:15 | 0 | 0.0 | 1289 ms | 0 |
| 07:30 | 0 | 0.0 | 651 ms | 0 |
| 07:45 | 0 | 0.0 | 388 ms | 0 |
| 08:00 | 0 | 0.0 | 725 ms | 0 |
| 08:15 | 0 | 0.0 | 307 ms | 0 |
| 08:30 | 0 | 0.0 | 1071 ms | 0 |
| 08:45 | 0 | 0.0 | 976 ms | 0 |
| 09:00 | 0 | 0.0 | 339 ms | 0 |
| 09:15 | 0 | 0.0 | 1099 ms | 0 |
| 09:30 | 0 | 0.0 | 606 ms | 0 |
| 09:45 | 0 | 0.0 | 440 ms | 0 |
| 10:00 | 0 | 0.0 | 798 ms | 0 |
| 10:15 | 0 | 0.0 | 356 ms | 0 |
| 10:30 | 0 | 0.0 | 559 ms | 0 |
| 10:45 | 0 | 0.0 | 424 ms | 0 |
| 11:00 | 0 | 0.0 | 518 ms | 0 |
| 11:15 | 0 | 0.0 | 340 ms | 0 |
| 11:30 | 0 | 0.0 | 646 ms | 0 |
| 11:45 | 0 | 0.0 | 440 ms | 0 |
| 12:00 | 0 | 0.0 | 368 ms | 0 |
| 12:15 | 0 | 0.0 | 419 ms | 0 |
Reliability
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.
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
Past outages
No outages on record for Section yet. Outages of 10 minutes or more get their own page here.
Having trouble with Section?
One report per service every 10 minutes from this network. No account.
Follow Section
Get an email when Section goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Section alerts to Slack, Discord or a webhook — free.
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.