User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Health
omniamedcommunications.com · Health
Is Omniamed Communications 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 → omniamedcommunications.com—
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 2 hr ago. Last stored result reached it in 595 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 05 | 0 | 0.0 | 521 ms | 0 |
| Tue 07 | 0 | 0.0 | 627 ms | 0 |
| Tue 09 | 0 | 0.0 | 639 ms | 0 |
| Tue 11 | 0 | 0.0 | 209 ms | 0 |
| Tue 14 | 0 | 0.0 | 434 ms | 0 |
| Tue 16 | 0 | 0.0 | 666 ms | 0 |
| Tue 18 | 0 | 0.0 | 482 ms | 0 |
| Tue 20 | 0 | 0.0 | 517 ms | 0 |
| Tue 23 | 0 | 0.0 | 619 ms | 0 |
| Wed 01 | 0 | 0.0 | 762 ms | 0 |
| Wed 03 | 0 | 0.0 | 613 ms | 0 |
| Wed 05 | 0 | 0.0 | 621 ms | 0 |
| Wed 08 | 0 | 0.0 | 614 ms | 0 |
| Wed 10 | 0 | 0.0 | 669 ms | 0 |
| Wed 12 | 0 | 0.0 | 637 ms | 0 |
| Wed 14 | 0 | 0.0 | 670 ms | 0 |
| Wed 16 | 0 | 0.0 | 709 ms | 0 |
| Wed 18 | 0 | 0.0 | 153 ms | 0 |
| Wed 21 | 0 | 0.0 | 669 ms | 0 |
| Wed 23 | 0 | 0.0 | 721 ms | 0 |
| Thu 01 | 0 | 0.0 | 693 ms | 0 |
| Thu 03 | 0 | 0.0 | 463 ms | 0 |
| Thu 05 | 0 | 0.0 | 673 ms | 0 |
| Thu 07 | 0 | 0.0 | 645 ms | 0 |
| Thu 09 | 0 | 0.0 | 667 ms | 0 |
| Thu 11 | 0 | 0.0 | 636 ms | 0 |
| Thu 13 | 0 | 0.0 | 667 ms | 0 |
| Thu 15 | 0 | 0.0 | 687 ms | 0 |
| Thu 18 | 0 | 0.0 | 712 ms | 0 |
| Thu 20 | 0 | 0.0 | 679 ms | 0 |
| Thu 22 | 0 | 0.0 | 658 ms | 0 |
| Fri 00 | 0 | 0.0 | 618 ms | 0 |
| Fri 02 | 0 | 0.0 | 542 ms | 0 |
| Fri 04 | 0 | 0.0 | 645 ms | 0 |
| Fri 06 | 0 | 0.0 | 622 ms | 0 |
| Fri 08 | 0 | 0.0 | 587 ms | 0 |
| Fri 10 | 0 | 0.0 | 536 ms | 0 |
| Fri 12 | 0 | 0.0 | 649 ms | 0 |
| Fri 14 | 0 | 0.0 | 643 ms | 0 |
| Fri 16 | 0 | 0.0 | 694 ms | 0 |
| Fri 18 | 0 | 0.0 | 702 ms | 0 |
| Fri 19 | 0 | 0.0 | 631 ms | 0 |
| Fri 21 | 0 | 0.0 | 247 ms | 0 |
| Fri 23 | 0 | 0.0 | 629 ms | 0 |
| Sat 01 | 0 | 0.0 | 619 ms | 0 |
| Sat 03 | 0 | 0.0 | 640 ms | 0 |
| Sat 05 | 0 | 0.0 | 620 ms | 0 |
| Sat 07 | 0 | 0.0 | 595 ms | 0 |
Reliability
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.
Embed this status: free live Omniamed Communications 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 Omniamed Communications yet. Outages of 10 minutes or more get their own page here.
Having trouble with Omniamed Communications?
One report per service every 10 minutes from this network. No account.
Follow Omniamed Communications
Get an email when Omniamed Communications goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Omniamed Communications alerts to Slack, Discord or a webhook — free.
About Omniamed Communications
Omniamed Communications is listed in our Health category and checked at omniamedcommunications.com. We’re proud of our credentials as a leading medical communications agency. But we’re so much more than that.
Omniamed Communications publishes an official status page at status.omniamedcommunications.com; when we can read it, its incident level is folded into the status shown here.
Typical issues 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: 604 ms average, 247–702 ms range across 14 successful checks.
Questions
Is Omniamed Communications down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Omniamed Communications last down?
We have not recorded a public Omniamed Communications incident since monitoring began 8 days ago.
What is Omniamed Communications's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Omniamed Communications respond?
604 ms on average over the last 24 hours (247–702 ms).
Does Omniamed Communications have an official status page?
Yes, at https://status.omniamedcommunications.com.
Omniamed Communications 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 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 Omniamed Communications here at once, the problem is on Omniamed Communications'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 Omniamed Communications. 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.