User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Health
omnipod.com · Health
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what 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, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 190 ms · 1 min ago.
No status feed
Omnipod does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 12:30 | 0 | 0.0 | 76 ms | 0 |
| 12:45 | 0 | 0.0 | 115 ms | 0 |
| 13:00 | 0 | 0.0 | 757 ms | 0 |
| 13:15 | 0 | 0.0 | 299 ms | 0 |
| 13:30 | 0 | 0.0 | 173 ms | 0 |
| 13:45 | 0 | 0.0 | 138 ms | 0 |
| 14:00 | 0 | 0.0 | 155 ms | 0 |
| 14:15 | 0 | 0.0 | 160 ms | 0 |
| 14:30 | 0 | 0.0 | 446 ms | 0 |
| 14:45 | 0 | 0.0 | 446 ms | 0 |
| 15:00 | 0 | 0.0 | 202 ms | 0 |
| 15:15 | 0 | 0.0 | 70 ms | 0 |
| 15:30 | 0 | 0.0 | 679 ms | 0 |
| 15:45 | 0 | 0.0 | 209 ms | 0 |
| 16:00 | 0 | 0.0 | 124 ms | 0 |
| 16:15 | 0 | 0.0 | 163 ms | 0 |
| 16:30 | 0 | 0.0 | 111 ms | 0 |
| 16:45 | 0 | 0.0 | 174 ms | 0 |
| 17:00 | 0 | 0.0 | 364 ms | 0 |
| 17:15 | 0 | 0.0 | 143 ms | 0 |
| 17:30 | 0 | 0.0 | 154 ms | 0 |
| 17:45 | 0 | 0.0 | 74 ms | 0 |
| 18:00 | 0 | 0.0 | 824 ms | 0 |
| 18:15 | 0 | 0.0 | 803 ms | 0 |
| 18:30 | 0 | 0.0 | 151 ms | 0 |
| 18:45 | 0 | 0.0 | 846 ms | 0 |
| 19:00 | 0 | 0.0 | 135 ms | 0 |
| 19:15 | 0 | 0.0 | 67 ms | 0 |
| 19:30 | 0 | 0.0 | 90 ms | 0 |
| 19:45 | 0 | 0.0 | 254 ms | 0 |
| 20:00 | 0 | 0.0 | 155 ms | 0 |
| 20:15 | 0 | 0.0 | 355 ms | 0 |
| 20:30 | 0 | 0.0 | 166 ms | 0 |
| 20:45 | 0 | 0.0 | 184 ms | 0 |
| 21:00 | 0 | 0.0 | 200 ms | 0 |
| 21:15 | 0 | 0.0 | 140 ms | 0 |
| 21:30 | 0 | 0.0 | 190 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Omnipod 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 Omnipod goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Omnipod alerts to Slack, Discord or a webhook — free.
We track Omnipod (omnipod.com) as part of the Health group. Live checks and user reports.
Omnipod has no official status feed we can read, so this page relies on our own checks and user reports.
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 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 281 ms average, 55–1543 ms range across 69 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public Omnipod incident since monitoring began 1 day ago.
From our own checks: 100% over 1 day of checks.
281 ms on average over the last 24 hours (55–1543 ms).
Not one we can read. This page uses independent checks of omnipod.com and user reports.
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 Omnipod here at once, the problem is on Omnipod's side.