User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
weinfuse.com · Cloud & developer
Is WeInfuse 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 → weinfuse.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 1 hr ago. Last stored result reached it in 265 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 73 ms | 0 |
| Mon 19 | 0 | 0.0 | 240 ms | 0 |
| Mon 22 | 0 | 0.0 | 71 ms | 0 |
| Tue 00 | 0 | 0.0 | 147 ms | 0 |
| Tue 02 | 0 | 0.0 | 188 ms | 0 |
| Tue 04 | 0 | 0.0 | 161 ms | 0 |
| Tue 06 | 0 | 0.0 | 243 ms | 0 |
| Tue 08 | 0 | 0.0 | 168 ms | 0 |
| Tue 10 | 0 | 0.0 | 272 ms | 0 |
| Tue 12 | 0 | 0.0 | 230 ms | 0 |
| Tue 15 | 0 | 0.0 | 172 ms | 0 |
| Tue 17 | 0 | 0.0 | 172 ms | 0 |
| Tue 19 | 0 | 0.0 | 241 ms | 0 |
| Tue 21 | 0 | 0.0 | 212 ms | 0 |
| Wed 00 | 0 | 0.0 | 376 ms | 0 |
| Wed 02 | 0 | 0.0 | 158 ms | 0 |
| Wed 04 | 0 | 0.0 | 256 ms | 0 |
| Wed 06 | 0 | 0.0 | 333 ms | 0 |
| Wed 09 | 0 | 0.0 | 303 ms | 0 |
| Wed 11 | 0 | 0.0 | 390 ms | 0 |
| Wed 13 | 0 | 0.0 | 350 ms | 0 |
| Wed 15 | 0 | 0.0 | 201 ms | 0 |
| Wed 17 | 0 | 0.0 | 242 ms | 0 |
| Wed 20 | 0 | 0.0 | 247 ms | 0 |
| Wed 22 | 0 | 0.0 | 162 ms | 0 |
| Thu 00 | 0 | 0.0 | 354 ms | 0 |
| Thu 02 | 0 | 0.0 | 333 ms | 0 |
| Thu 04 | 0 | 0.0 | 227 ms | 0 |
| Thu 06 | 0 | 0.0 | 236 ms | 0 |
| Thu 08 | 0 | 0.0 | 225 ms | 0 |
| Thu 10 | 0 | 0.0 | 148 ms | 0 |
| Thu 12 | 0 | 0.0 | 237 ms | 0 |
| Thu 14 | 0 | 0.0 | 228 ms | 0 |
| Thu 17 | 0 | 0.0 | 362 ms | 0 |
| Thu 19 | 0 | 0.0 | 258 ms | 0 |
| Thu 21 | 0 | 0.0 | 387 ms | 0 |
| Thu 23 | 0 | 0.0 | 148 ms | 0 |
| Fri 01 | 0 | 0.0 | 252 ms | 0 |
| Fri 03 | 0 | 0.0 | 222 ms | 0 |
| Fri 05 | 0 | 0.0 | 241 ms | 0 |
| Fri 07 | 0 | 0.0 | 164 ms | 0 |
| Fri 08 | 0 | 0.0 | 140 ms | 0 |
| Fri 10 | 0 | 0.0 | 272 ms | 0 |
| Fri 11 | 0 | 0.0 | 226 ms | 0 |
| Fri 13 | 0 | 0.0 | 270 ms | 0 |
| Fri 14 | 0 | 0.0 | 150 ms | 0 |
| Fri 16 | 0 | 0.0 | 353 ms | 0 |
| Fri 17 | 0 | 0.0 | 265 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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 WeInfuse 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 WeInfuse yet. Outages of 10 minutes or more get their own page here.
Having trouble with WeInfuse?
One report per service every 10 minutes from this network. No account.
Follow WeInfuse
Get an email when WeInfuse goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send WeInfuse alerts to Slack, Discord or a webhook — free.
About WeInfuse
We track WeInfuse (weinfuse.com) as part of the Cloud & developer group. WeInfuse's infusion software streamlines operations for infusion centers and home infusion & specialty pharmacies.
WeInfuse publishes an official status page at status.weinfuse.com; when we can read it, its incident level is folded into the status shown here.
Common problems for 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: 239 ms average, 140–387 ms range across 14 successful checks.
Questions
Is WeInfuse down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was WeInfuse last down?
We have not recorded a public WeInfuse incident since monitoring began 8 days ago.
What is WeInfuse's uptime?
From our own checks: 100% over 8 days of checks.
How fast does WeInfuse respond?
239 ms on average over the last 24 hours (140–387 ms).
Does WeInfuse have an official status page?
Yes, at https://status.weinfuse.com.
WeInfuse 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 cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report WeInfuse here at once, the problem is on WeInfuse'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 WeInfuse. 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.