User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
trimrx.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 1 hr ago. Last stored result reached it in 89 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 88 ms | 0 |
| Mon 19 | 0 | 0.0 | 80 ms | 0 |
| Mon 21 | 0 | 0.0 | 130 ms | 0 |
| Tue 00 | 0 | 0.0 | 232 ms | 0 |
| Tue 02 | 0 | 0.0 | 91 ms | 0 |
| Tue 04 | 0 | 0.0 | 77 ms | 0 |
| Tue 06 | 0 | 0.0 | 96 ms | 0 |
| Tue 08 | 0 | 0.0 | 1132 ms | 0 |
| Tue 10 | 0 | 0.0 | 94 ms | 0 |
| Tue 12 | 0 | 0.0 | 118 ms | 0 |
| Tue 14 | 0 | 0.0 | 67 ms | 0 |
| Tue 17 | 0 | 0.0 | 124 ms | 0 |
| Tue 19 | 0 | 0.0 | 139 ms | 0 |
| Tue 21 | 0 | 0.0 | 146 ms | 0 |
| Wed 00 | 0 | 0.0 | 121 ms | 0 |
| Wed 02 | 0 | 0.0 | 103 ms | 0 |
| Wed 04 | 0 | 0.0 | 77 ms | 0 |
| Wed 06 | 0 | 0.0 | 103 ms | 0 |
| Wed 08 | 0 | 0.0 | 124 ms | 0 |
| Wed 11 | 0 | 0.0 | 228 ms | 0 |
| Wed 13 | 0 | 0.0 | 92 ms | 0 |
| Wed 15 | 0 | 0.0 | 60 ms | 0 |
| Wed 17 | 0 | 0.0 | 121 ms | 0 |
| Wed 19 | 0 | 0.0 | 90 ms | 0 |
| Wed 22 | 0 | 0.0 | 129 ms | 0 |
| Thu 00 | 0 | 0.0 | 1138 ms | 0 |
| Thu 02 | 0 | 0.0 | 72 ms | 0 |
| Thu 04 | 0 | 0.0 | 1115 ms | 0 |
| Thu 06 | 0 | 0.0 | 163 ms | 0 |
| Thu 08 | 0 | 0.0 | 115 ms | 0 |
| Thu 10 | 0 | 0.0 | 114 ms | 0 |
| Thu 12 | 0 | 0.0 | 87 ms | 0 |
| Thu 14 | 0 | 0.0 | 129 ms | 0 |
| Thu 16 | 0 | 0.0 | 86 ms | 0 |
| Thu 18 | 0 | 0.0 | 90 ms | 0 |
| Thu 19 | 0 | 0.0 | 121 ms | 0 |
| Thu 21 | 0 | 0.0 | 42 ms | 0 |
| Thu 22 | 0 | 0.0 | 69 ms | 0 |
| Fri 01 | 0 | 0.0 | 163 ms | 0 |
| Fri 03 | 0 | 0.0 | 99 ms | 0 |
| Fri 05 | 0 | 0.0 | 85 ms | 0 |
| Fri 07 | 0 | 0.0 | 102 ms | 0 |
| Fri 09 | 0 | 0.0 | 109 ms | 0 |
| Fri 11 | 0 | 0.0 | 99 ms | 0 |
| Fri 13 | 0 | 0.0 | 77 ms | 0 |
| Fri 15 | 0 | 0.0 | 96 ms | 0 |
| Fri 17 | 0 | 0.0 | 177 ms | 0 |
| Fri 18 | 0 | 0.0 | 89 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 TrimRx 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 TrimRx goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send TrimRx alerts to Slack, Discord or a webhook — free.
TrimRx is listed in our Cloud & developer category and checked at trimrx.com. Lose weight with a doctor-supervised program and GLP-1 medication delivered to your door. Free shipping, expert care from $179/mo.
TrimRx publishes an official status page at status.trimrx.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: 101 ms average, 42–177 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public TrimRx incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
101 ms on average over the last 24 hours (42–177 ms).
Yes, at https://status.trimrx.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 TrimRx here at once, the problem is on TrimRx'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 TrimRx. 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.