Server reachable?
Run the ping test against your domain. Replies with steady times point away from a network outage.
WebJi® network status covers how every hosting node is monitored: uptime, web, mail, DNS, SSL expiry and backups, polled every 60 seconds. Hosting plans carry a 99.9% monthly uptime commitment, about 43 minutes of downtime a month, with SLA service credits beyond that. Report a fault by ticket or support@webji.services, 24/7.
For WebJi® customers whose site or mail has stopped working and who need to know what is watched, what to check and how to report it.
Last editorial update: 14 November 2026.
WebJi® network monitoring polls every hosting node every 60 seconds, from inside and outside the network, and watches the services your site and mail depend on. A check from outside catches what a customer would see; a check from inside separates a network fault from a failed service on the server itself.
| Check | What is watched | What you notice if it fails |
|---|---|---|
| Server uptime and load | Every hosting node, every 60 seconds | Site slow or not loading at all |
| Web service | HTTP and HTTPS daemons | Browser timeout or 5xx error |
| Mail services | SMTP, IMAP and POP3 | Mail stuck in outbox or not arriving |
| DNS, FTP, databases | Name service, file transfer, MySQL-type databases | Domain not resolving, upload refused, "error establishing a database connection" |
| SSL certificate expiry | Automated renewal with alerts before any certificate lapses | Browser security warning |
| Backup jobs | Daily jobs verified; failures escalated the same day | Nothing visible — this protects your restore point |
| Data-centre network | Upstream links and packet loss to Indian and international peering points | Site reachable from some networks but not others |
An alert reaches the on-call engineer when a check fails twice in a row, and diagnosis starts at once. Requiring two failures filters out a single dropped probe, so engineers respond to real faults rather than noise.
Scheduled maintenance is announced in advance and is not counted as downtime; emergency maintenance is handled by severity.
Five minutes with free tools usually tells you whether a fault sits with your internet connection, your site's code or DNS, or the hosting server. Running them before you report also gives the engineer evidence to work from.
Run the ping test against your domain. Replies with steady times point away from a network outage.
A DNS lookup shows whether the A record still points at your WebJi® server IP after a recent nameserver change.
The SSL checker confirms expiry date and chain when visitors report a security warning.
If only your office cannot reach the site, note your public address from What Is My IP; repeated failed logins can block an IP.
A 500 usually means site code; a 502 or 503 can be the server. The HTTP status codes guide explains each one.
For a site that is down and none of these explain it, the website down checklist lists the next steps.
Open a support ticket with your domain and the time you first noticed the fault; that timestamp lets the engineer match server logs straight away. Email works as a parallel channel when you need a written trail, and phone suits urgent calls during office hours.
| Channel | Best for | Availability |
|---|---|---|
| Ticket via client area or contact page | Downtime, slow sites, mail faults | 24×7 — the fastest route |
| Email support@webji.services | Written record, monitoring questions, uptime report requests | 24/7 in Hindi and English; average first reply under 60 minutes |
| Phone +91 141 4941811 | Urgent outage during the working day | Jaipur office, business hours |
99.9% measured monthly allows roughly 43 minutes of unplanned downtime in a 30-day month, or about 8.76 hours across a year. The arithmetic is 0.1% of 43,200 minutes. Downtime beyond that on an eligible service earns credits; the claim route and exclusions — announced maintenance, client-side code, third-party DNS and upstream ISP failures — are set out on the SLA page.
Per-server uptime reports are available to any customer on request from the support desk. They are issued per account rather than as a site-wide average, because a figure without your own server behind it tells you little. You are welcome to run an independent monitor as well; the uptime monitoring guide explains how, and in a dispute both datasets are compared.
Every hosting node is polled every 60 seconds, from inside and outside the WebJi® network. An alert goes to the on-call engineer after two consecutive failed checks, so a fault is normally being worked on within a couple of minutes of starting.
Yes. Affected customers receive status updates by ticket and email while the incident is open. Any outage longer than 15 minutes is followed by a root-cause write-up once service is restored.
No. Maintenance announced in advance is excluded from the monthly measurement, as are faults outside the WebJi® network path such as your site's own code, third-party DNS and upstream ISP failures. Emergency work is handled by severity.
Yes. Email support@webji.services from the account's registered address and ask for the per-server uptime report for the months you need. Reports are issued per account, not as a general average.
Probably not. When one network fails and another works, the usual causes are a firewall block on your office IP after failed logins or a stale DNS cache. Send your public IP in a ticket and support can check the block list.
Last editorial update: 14 November 2026.
Join 12,000+ businesses across India and overseas. INR pricing, 18% GST shown before payment and 24/7 email support in Hindi and English — average first reply under 60 minutes.