User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
releem.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps 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. Every report with a known place can appear on the map. Updates every minute.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 438 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 04 | 0 | 0.0 | 455 ms | 0 |
| Tue 06 | 0 | 0.0 | 130 ms | 0 |
| Tue 08 | 0 | 0.0 | 295 ms | 0 |
| Tue 10 | 0 | 0.0 | 535 ms | 0 |
| Tue 12 | 0 | 0.0 | 399 ms | 0 |
| Tue 14 | 0 | 0.0 | 120 ms | 0 |
| Tue 17 | 0 | 0.0 | 417 ms | 0 |
| Tue 19 | 0 | 0.0 | 85 ms | 0 |
| Tue 21 | 0 | 0.0 | 385 ms | 0 |
| Tue 23 | 0 | 0.0 | 482 ms | 0 |
| Wed 01 | 0 | 0.0 | 303 ms | 0 |
| Wed 04 | 0 | 0.0 | 294 ms | 0 |
| Wed 06 | 0 | 0.0 | 120 ms | 0 |
| Wed 08 | 0 | 0.0 | 393 ms | 0 |
| Wed 11 | 0 | 0.0 | 187 ms | 0 |
| Wed 13 | 0 | 0.0 | 283 ms | 0 |
| Wed 15 | 0 | 0.0 | 431 ms | 0 |
| Wed 17 | 0 | 0.0 | 438 ms | 0 |
| Wed 19 | 0 | 0.0 | 452 ms | 0 |
| Wed 21 | 0 | 0.0 | 268 ms | 0 |
| Wed 23 | 0 | 0.0 | 326 ms | 0 |
| Thu 02 | 0 | 0.0 | 377 ms | 0 |
| Thu 04 | 0 | 0.0 | 304 ms | 0 |
| Thu 06 | 0 | 0.0 | 385 ms | 0 |
| Thu 08 | 0 | 0.0 | 331 ms | 0 |
| Thu 10 | 0 | 0.0 | 149 ms | 0 |
| Thu 12 | 0 | 0.0 | 339 ms | 0 |
| Thu 14 | 0 | 0.0 | 308 ms | 0 |
| Thu 16 | 0 | 0.0 | 231 ms | 0 |
| Thu 18 | 0 | 0.0 | 183 ms | 0 |
| Thu 20 | 0 | 0.0 | 266 ms | 0 |
| Thu 22 | 0 | 0.0 | 123 ms | 0 |
| Fri 00 | 0 | 0.0 | 471 ms | 0 |
| Fri 02 | 0 | 0.0 | 342 ms | 0 |
| Fri 04 | 0 | 0.0 | 438 ms | 0 |
| Fri 05 | 0 | 0.0 | 193 ms | 0 |
| Fri 08 | 0 | 0.0 | 333 ms | 0 |
| Fri 10 | 0 | 0.0 | 200 ms | 0 |
| Fri 11 | 0 | 0.0 | 306 ms | 0 |
| Fri 12 | 0 | 0.0 | 429 ms | 0 |
| Fri 14 | 0 | 0.0 | 135 ms | 0 |
| Fri 17 | 0 | 0.0 | 397 ms | 0 |
| Fri 18 | 0 | 0.0 | 397 ms | 0 |
| Fri 19 | 0 | 0.0 | 262 ms | 0 |
| Fri 21 | 0 | 0.0 | 221 ms | 0 |
| Fri 22 | 0 | 0.0 | 342 ms | 0 |
| Sat 00 | 0 | 0.0 | 150 ms | 0 |
| Sat 02 | 0 | 0.0 | 438 ms | 0 |
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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Releem 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 Releem goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Releem alerts to Slack, Discord or a webhook — free.
Releem is listed in our Cloud & developer category and checked at releem.com. Improve MySQL performance with workload-based query, index and configuration recommendations, plus controlled automation. Also supports MariaDB and PostgreSQL.
Releem publishes an official status page at status.releem.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 297 ms average, 90–438 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Releem incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
297 ms on average over the last 24 hours (90–438 ms).
Yes, at https://status.releem.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Releem here at once, the problem is on Releem'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 Releem. 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.