User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
mindbloom.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 9 min ago. Last stored result reached it in 153 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 70 ms | 0 |
| Mon 22 | 0 | 0.0 | 65 ms | 0 |
| Tue 00 | 0 | 0.0 | 62 ms | 0 |
| Tue 02 | 0 | 0.0 | 106 ms | 0 |
| Tue 04 | 0 | 0.0 | 143 ms | 0 |
| Tue 06 | 0 | 0.0 | 60 ms | 0 |
| Tue 08 | 0 | 0.0 | 74 ms | 0 |
| Tue 10 | 0 | 0.0 | 97 ms | 0 |
| Tue 12 | 0 | 0.0 | 373 ms | 0 |
| Tue 15 | 0 | 0.0 | 63 ms | 0 |
| Tue 17 | 0 | 0.0 | 150 ms | 0 |
| Tue 19 | 0 | 0.0 | 208 ms | 0 |
| Tue 22 | 0 | 0.0 | 101 ms | 0 |
| Wed 00 | 0 | 0.0 | 149 ms | 0 |
| Wed 02 | 0 | 0.0 | 152 ms | 0 |
| Wed 04 | 0 | 0.0 | 80 ms | 0 |
| Wed 06 | 0 | 0.0 | 73 ms | 0 |
| Wed 09 | 0 | 0.0 | 45 ms | 0 |
| Wed 11 | 0 | 0.0 | 60 ms | 0 |
| Wed 13 | 0 | 0.0 | 88 ms | 0 |
| Wed 15 | 0 | 0.0 | 92 ms | 0 |
| Wed 17 | 0 | 0.0 | 214 ms | 0 |
| Wed 20 | 0 | 0.0 | 113 ms | 0 |
| Wed 22 | 0 | 0.0 | 194 ms | 0 |
| Thu 00 | 0 | 0.0 | 119 ms | 0 |
| Thu 02 | 0 | 0.0 | 243 ms | 0 |
| Thu 04 | 0 | 0.0 | 133 ms | 0 |
| Thu 05 | 0 | 0.0 | 257 ms | 0 |
| Thu 06 | 0 | 0.0 | 154 ms | 0 |
| Thu 08 | 0 | 0.0 | 59 ms | 0 |
| Thu 10 | 0 | 0.0 | 95 ms | 0 |
| Thu 12 | 0 | 0.0 | 104 ms | 0 |
| Thu 14 | 0 | 0.0 | 96 ms | 0 |
| Thu 16 | 0 | 0.0 | 240 ms | 0 |
| Thu 18 | 0 | 0.0 | 113 ms | 0 |
| Thu 20 | 0 | 0.0 | 74 ms | 0 |
| Thu 22 | 0 | 0.0 | 152 ms | 0 |
| Fri 00 | 0 | 0.0 | 185 ms | 0 |
| Fri 03 | 0 | 0.0 | 152 ms | 0 |
| Fri 05 | 0 | 0.0 | 184 ms | 0 |
| Fri 07 | 0 | 0.0 | 157 ms | 0 |
| Fri 09 | 0 | 0.0 | 101 ms | 0 |
| Fri 10 | 0 | 0.0 | 57 ms | 0 |
| Fri 12 | 0 | 0.0 | 147 ms | 0 |
| Fri 14 | 0 | 0.0 | 59 ms | 0 |
| Fri 16 | 0 | 0.0 | 184 ms | 0 |
| Fri 17 | 0 | 0.0 | 73 ms | 0 |
| Fri 18 | 0 | 0.0 | 153 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Mindbloom 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 Mindbloom goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Mindbloom alerts to Slack, Discord or a webhook — free.
We track Mindbloom (mindbloom.com) as part of the Cloud & developer group. Neuroplasticity that works, results you can trust. The only at-home ketamine therapy with proven outcomes for depression, anxiety, and PTSD. Get started today.
Mindbloom publishes an official status page at status.mindbloom.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 124 ms average, 45–185 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Mindbloom incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
124 ms on average over the last 24 hours (45–185 ms).
Yes, at https://status.mindbloom.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 Mindbloom here at once, the problem is on Mindbloom'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 Mindbloom. 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.