This article explains why a “Data Error” message may appear in SiteBacker or Traffic Controller alerts in UltraDNS and what it indicates about probe behavior or reporting data.
When to Use This Article
- You received a SiteBacker or Traffic Controller alert showing “Data Error”.
- Alert reports do not display expected probe results.
- You are reviewing health status and see missing or incomplete data.
What a “Data Error” Indicates
A “Data Error” alert indicates that expected monitoring data was not available at the time the alert was generated.
This does not necessarily mean the monitored resource is down. It typically reflects missing or incomplete probe data rather than a confirmed outage.
Data errors can occur when probe results are delayed, unavailable, or temporarily inconsistent across monitoring regions.
Common Causes
- Temporary probe communication issues.
- Network interruptions between probe regions and the monitored endpoint.
- Configuration changes made to the pool or probe.
- Monitoring regions not returning consistent responses.
What You Should Check
- Review the current health status of the pool in the UltraDNS portal.
- Verify that probe configuration settings are correct.
- Confirm that monitored endpoints are accessible from multiple regions.
- Check recent configuration changes that may have affected monitoring.
Verification
If probe data resumes normally and health status stabilizes, the Data Error condition should clear automatically.
Continued Data Error alerts may indicate persistent connectivity or configuration issues that require further investigation.
Important Notes
- A Data Error does not always indicate downtime.
- Temporary network instability can trigger transient data errors.
- Repeated alerts should be investigated for probe or endpoint configuration issues.