Service Status

This Service Status page is intended to publish confirmed maintenance, incidents, performance issues and important operational notices about Nettescil services. When there is no verified monitoring source, the page should not pretend that every service is operational. A current status should be published only when a confirmed event, maintenance record or operational review exists.

How status is evaluated

A page loading successfully does not prove that every service is healthy. Web hosting, DNS, email, customer panel, licensing, payment and support systems are separate components. A DNS issue may affect a website while the server is running, and an application problem may affect one customer without being a general outage. Availability, error rate, affected service, start time and current impact should be considered together.

Hosting and servers

For web hosting, DNS resolution, web response, SSL, PHP, database and file access may be checked separately. Reseller hosting also includes account limits and customer accounts. In VPS, VDS and dedicated servers, operating system, disk, network, firewall, control panel and customer-installed services are separate responsibility layers. A customer configuration change should not automatically be described as a data center outage.

Domains and external providers

Domain operations can depend on registrar responses, DNS, nameservers, WHOIS, transfer lock and customer panel processes. Licensing may depend on a provider, license IP, activation service and automation response. If an external provider has not replied, an order or renewal should not be presented as completed.

Status categories

A verified status source may use Working, Performance Issue, Partial Outage, Major Outage and Maintenance. These labels describe the confirmed scope of an event. A Working label does not mean every customer application has been tested; it should represent the result of defined basic checks.

Maintenance and incident handling

A maintenance notice should include affected services, planned time, expected impact and customer action. During an incident, collect the start time, affected URL, error, recent changes and tests from another network. After recovery, verify the affected workflow rather than only the homepage. Cached DNS or browser sessions may continue to show an old error for a short period.

Future status integration

If a real monitoring or status API becomes available, it should be integrated with source identity, timeout handling, maintenance records, event history and notification rules. A colorful status card alone is not a monitoring system. Until the data source is verified, confirmed notices are more reliable than artificial live indicators.

See Infrastructure, Network Infrastructure, Security Infrastructure and Backup Policy. For a service-specific issue, contact support with the domain, service and error time.