User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Utilities
Is Dispel 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 → dispel.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 120 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 23 | 0 | 0.0 | 271 ms | 0 |
| Tue 01 | 0 | 0.0 | 94 ms | 0 |
| Tue 03 | 0 | 0.0 | 243 ms | 0 |
| Tue 05 | 0 | 0.0 | 234 ms | 0 |
| Tue 07 | 0 | 0.0 | 233 ms | 0 |
| Tue 09 | 0 | 0.0 | 214 ms | 0 |
| Tue 11 | 0 | 0.0 | 137 ms | 0 |
| Tue 13 | 0 | 0.0 | 242 ms | 0 |
| Tue 16 | 0 | 0.0 | 214 ms | 0 |
| Tue 18 | 0 | 0.0 | 242 ms | 0 |
| Tue 20 | 0 | 0.0 | 221 ms | 0 |
| Tue 22 | 0 | 0.0 | 127 ms | 0 |
| Wed 01 | 0 | 0.0 | 253 ms | 0 |
| Wed 03 | 0 | 0.0 | 158 ms | 0 |
| Wed 05 | 0 | 0.0 | 152 ms | 0 |
| Wed 07 | 0 | 0.0 | 286 ms | 0 |
| Wed 10 | 0 | 0.0 | 239 ms | 0 |
| Wed 12 | 0 | 0.0 | 139 ms | 0 |
| Wed 14 | 0 | 0.0 | 104 ms | 0 |
| Wed 16 | 0 | 0.0 | 110 ms | 0 |
| Wed 18 | 0 | 0.0 | 164 ms | 0 |
| Wed 20 | 0 | 0.0 | 204 ms | 0 |
| Wed 23 | 0 | 0.0 | 235 ms | 0 |
| Thu 01 | 0 | 0.0 | 233 ms | 0 |
| Thu 03 | 0 | 0.0 | 235 ms | 0 |
| Thu 05 | 0 | 0.0 | 259 ms | 0 |
| Thu 07 | 0 | 0.0 | 241 ms | 0 |
| Thu 09 | 0 | 0.0 | 227 ms | 0 |
| Thu 11 | 0 | 0.0 | 217 ms | 0 |
| Thu 13 | 0 | 0.0 | 259 ms | 0 |
| Thu 15 | 0 | 0.0 | 253 ms | 0 |
| Thu 16 | 0 | 0.0 | 260 ms | 0 |
| Thu 18 | 0 | 0.0 | 244 ms | 0 |
| Thu 20 | 0 | 0.0 | 246 ms | 0 |
| Thu 22 | 0 | 0.0 | 186 ms | 0 |
| Fri 00 | 0 | 0.0 | 190 ms | 0 |
| Fri 02 | 0 | 0.0 | 111 ms | 0 |
| Fri 04 | 0 | 0.0 | 265 ms | 0 |
| Fri 06 | 0 | 0.0 | 218 ms | 0 |
| Fri 08 | 0 | 0.0 | 138 ms | 0 |
| Fri 10 | 0 | 0.0 | 256 ms | 0 |
| Fri 12 | 0 | 0.0 | 146 ms | 0 |
| Fri 14 | 0 | 0.0 | 144 ms | 0 |
| Fri 16 | 0 | 0.0 | 239 ms | 0 |
| Fri 18 | 0 | 0.0 | 264 ms | 0 |
| Fri 19 | 0 | 0.0 | 153 ms | 0 |
| Fri 21 | 0 | 0.0 | 247 ms | 0 |
| Fri 23 | 0 | 0.0 | 120 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 6 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Dispel 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 Dispel yet. Outages of 10 minutes or more get their own page here.
Having trouble with Dispel?
One report per service every 10 minutes from this network. No account.
Follow Dispel
Get an email when Dispel goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Dispel alerts to Slack, Discord or a webhook — free.
About Dispel
We track Dispel (dispel.com) as part of the Utilities group. Connect vendors, OEMs, and operators to critical OT systems in seconds — without the downtime or risk legacy tools create. Built for manufacturing, utilities, and energy at scale.
Dispel publishes an official status page at status.dispel.com; when we can read it, its incident level is folded into the status shown here.
Common problems for utilities services: outage maps and bill-pay pages slowing or failing during storms and peak demand, and account sign-in problems.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 194 ms average, 111–282 ms range across 14 successful checks.
Questions
Is Dispel down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Dispel last down?
We have not recorded a public Dispel incident since monitoring began 6 days ago.
What is Dispel's uptime?
From our own checks: 100% over 6 days of checks.
How fast does Dispel respond?
194 ms on average over the last 24 hours (111–282 ms).
Does Dispel have an official status page?
Yes, at https://status.dispel.com.
Dispel 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 utilities services, watch for outage maps and bill-pay pages slowing or failing during storms and peak demand, and account sign-in problems. If many people report Dispel here at once, the problem is on Dispel'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 Dispel. 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.