New Multi-region uptime checks and custom-domain status pages

Dizzion Outage History

Daily provider-status observations and published incident history for Dizzion.

Unknown

Current status for Dizzion cannot be verified right now. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Dizzion for future changes.

100% of 81 verified observed days had no reported provider issue

90-Day Trend

Aug 18Nov 15

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
October 2026 100% 30 0
September 2026 100% 29 0

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Aug 17 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.

Legacy Incident Archive

1 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

August 2026
Intermittent Access to use.difr.com
critical Source not attested
Last archived state: resolved
View archived record details
monitoring
Dizzion has resolved an issue with the difr.com domain. Users may still experience issues accessing use.difr.com as the DNS changes propagate. Dizzion is monitoring for stability. If you are still experiencing issues, please try a DNS flush and reach out to Dizzion support if that does not resolve the issue for the user(s).
investigating
Dizzion is investigating an issue where when trying to reach use.difr.com, an error is intermittently presented. Dizzion is investigating and will provide an update in the next 60 minutes. As a workaround, users can use console.nutanix.com.