A monitor can fail because of DNS, TLS, one network path, response content or a real short outage; compare evidence before dismissing it.
Applies to: 360 Monitoring
360 Monitoring Lite is included with Tudor Internet hosting products, with paid tiers available where more monitoring is required. Monitoring detects symptoms; it does not automatically repair the underlying service.
Before you start
- Confirm the active product or addon and the domain or user it protects.
- Record the current settings before changing them.
Work through these checks
- Record the monitor name, location, failure reason and first/last failure times.
- Check the Tudor Internet Service Status page and test the URL from another network.
- Verify DNS and certificate validity for both IPv4 and IPv6 where published.
- Review web access and error logs at the alert time to see whether the monitoring request reached the server.
- Check whether the monitor expected a status code or page text that changed during a normal deployment.
- Adjust timeout or content checks only when the old setting was objectively inappropriate.
- Keep recurring brief failures under investigation because they may reveal resource limits or an external dependency.
Confirm the result
- The service dashboard shows the intended setting or activation state after reload.
- A live test from a separate session or device confirms that the customer-facing service works as expected.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| The service does not show as active in its dashboard. | Provisioning is pending, the wrong plan is selected or the service requires an additional activation step. | Check the Customer Portal service status and order email, then open a ticket with the service ID instead of creating a duplicate order. |
| The dashboard setting is correct but the public result is not. | DNS caching, an integration token, a device cache or a second service layer still uses the old value. | Test from a separate session, check the integration and record exact timestamps before changing the setting again. |
When to contact Tudor Internet
Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:
- The addon service and protected domain or user
- The plan or licence level
- The time the issue started and exact message
- Screenshots with credentials, tokens and personal data removed
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.
Related articles
- Investigate a monitoring alert
- Check the public Service Status page
- Read website access and error logs
- Check DNS with dig, nslookup and public resolvers
- 360 Monitoring Lite included with Tudor Internet hosting
Last reviewed: 2026-07-18.
