User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Health
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 45 min ago. Last stored result reached it in 20 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 05 | 0 | 0.0 | 51 ms | 0 |
| Tue 07 | 0 | 0.0 | 48 ms | 0 |
| Tue 09 | 0 | 0.0 | 72 ms | 0 |
| Tue 11 | 0 | 0.0 | 59 ms | 0 |
| Tue 14 | 0 | 0.0 | 110 ms | 0 |
| Tue 16 | 0 | 0.0 | 141 ms | 0 |
| Tue 18 | 0 | 0.0 | 81 ms | 0 |
| Tue 20 | 0 | 0.0 | 126 ms | 0 |
| Tue 23 | 0 | 0.0 | 127 ms | 0 |
| Wed 01 | 0 | 0.0 | 150 ms | 0 |
| Wed 03 | 0 | 0.0 | 160 ms | 0 |
| Wed 05 | 0 | 0.0 | 66 ms | 0 |
| Wed 08 | 0 | 0.0 | 70 ms | 0 |
| Wed 10 | 0 | 0.0 | 132 ms | 0 |
| Wed 12 | 0 | 0.0 | 100 ms | 0 |
| Wed 14 | 0 | 0.0 | 64 ms | 0 |
| Wed 16 | 0 | 0.0 | 146 ms | 0 |
| Wed 18 | 0 | 0.0 | 70 ms | 0 |
| Wed 21 | 0 | 0.0 | 60 ms | 0 |
| Wed 23 | 0 | 0.0 | 126 ms | 0 |
| Thu 01 | 0 | 0.0 | 134 ms | 0 |
| Thu 03 | 0 | 0.0 | 90 ms | 0 |
| Thu 05 | 0 | 0.0 | 160 ms | 0 |
| Thu 07 | 0 | 0.0 | 107 ms | 0 |
| Thu 09 | 0 | 0.0 | 43 ms | 0 |
| Thu 11 | 0 | 0.0 | 111 ms | 0 |
| Thu 13 | 0 | 0.0 | 103 ms | 0 |
| Thu 15 | 0 | 0.0 | 64 ms | 0 |
| Thu 18 | 0 | 0.0 | 230 ms | 0 |
| Thu 20 | 0 | 0.0 | 223 ms | 0 |
| Thu 22 | 0 | 0.0 | 78 ms | 0 |
| Fri 00 | 0 | 0.0 | 57 ms | 0 |
| Fri 02 | 0 | 0.0 | 112 ms | 0 |
| Fri 04 | 0 | 0.0 | 117 ms | 0 |
| Fri 06 | 0 | 0.0 | 123 ms | 0 |
| Fri 08 | 0 | 0.0 | 62 ms | 0 |
| Fri 10 | 0 | 0.0 | 71 ms | 0 |
| Fri 11 | 0 | 0.0 | 130 ms | 0 |
| Fri 13 | 0 | 0.0 | 62 ms | 0 |
| Fri 15 | 0 | 0.0 | 140 ms | 0 |
| Fri 17 | 0 | 0.0 | 148 ms | 0 |
| Fri 18 | 0 | 0.0 | 152 ms | 0 |
| Fri 20 | 0 | 0.0 | 74 ms | 0 |
| Fri 22 | 0 | 0.0 | 136 ms | 0 |
| Sat 00 | 0 | 0.0 | 61 ms | 0 |
| Sat 02 | 0 | 0.0 | 50 ms | 0 |
| Sat 04 | 0 | 0.0 | 72 ms | 0 |
| Sat 05 | 0 | 0.0 | 20 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 Pharmetika 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 Pharmetika goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Pharmetika alerts to Slack, Discord or a webhook — free.
We track Pharmetika (pharmetika.com) as part of the Health group. Cloud-based compounding pharmacy software for intake, formulation, compliance, fulfillment, and patient delivery.
Pharmetika publishes an official status page at status.pharmetika.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with health services: patient portal and member sign-in failures, prescription refills or appointment booking not going through, and app errors.
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: 93 ms average, 20–152 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Pharmetika incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
93 ms on average over the last 24 hours (20–152 ms).
Yes, at https://status.pharmetika.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For health services, watch for patient portal and member sign-in failures, prescription refills or appointment booking not going through, and app errors. If many people report Pharmetika here at once, the problem is on Pharmetika'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 Pharmetika. 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.