User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
Is Released down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → released.so—
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. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 47 min ago. Last stored result reached it in 119 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 06:45 | 0 | 0.0 | 100 ms | 0 |
| 08:45 | 0 | 0.0 | 105 ms | 0 |
| 10:45 | 0 | 0.0 | 73 ms | 0 |
| 13:00 | 0 | 0.0 | 44 ms | 0 |
| 15:00 | 0 | 0.0 | 201 ms | 0 |
| 17:00 | 0 | 0.0 | 221 ms | 0 |
| 19:15 | 0 | 0.0 | 300 ms | 0 |
| 21:15 | 0 | 0.0 | 51 ms | 0 |
| 21:30 | 0 | 0.0 | 446 ms | 0 |
| 23:30 | 0 | 0.0 | 73 ms | 0 |
| 01:30 | 0 | 0.0 | 82 ms | 0 |
| 03:45 | 0 | 0.0 | 62 ms | 0 |
| 05:45 | 0 | 0.0 | 237 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Released badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Released yet. Outages of 10 minutes or more get their own page here.
Having trouble with Released?
One report per service every 10 minutes from this network. No account.
Follow Released
Get an email when Released goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Released alerts to Slack, Discord or a webhook — free.
About Released
Released is listed in our Productivity category and checked at released.so. Released builds Jira apps for faster product work: BetterBoard for flexible planning and Released Hub for customer feedback, roadmaps, and release notes.
Released publishes an official status page at status.released.so; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 159 ms average, 44–446 ms range across 14 successful checks.
Questions
Is Released down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Released last down?
We have not recorded a public Released incident since monitoring began 7 days ago.
What is Released's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Released respond?
159 ms on average over the last 24 hours (44–446 ms).
Does Released have an official status page?
Yes, at https://status.released.so.
Released not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Released here at once, the problem is on Released's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Released. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.