Independent service intelligence
About NepalStatus
NepalStatus is an evidence-led monitoring platform for Nepal's most important digital services. We combine automated checks, public reports, and incident signals to show whether a problem looks local, partial, or widespread.
What We Monitor
Coverage spans the services people rely on every day:
- Digital wallets: eSewa, Khalti, IME Pay, and similar payment platforms.
- Banking: commercial banks, development banks, and internet banking portals.
- Telecom and ISPs: NTC, Ncell, WorldLink, Vianet, DishHome, and related providers.
- Government and education: MeroShare, passport, licensing, and public service portals.
- Commonly used global platforms: services that are widely accessed from Nepal.
How We Work
We combine several evidence sources before showing a status result:
- Automated HTTP checks that verify reachability, response time, redirects, and SSL health.
- User-submitted reports that help identify regional or ISP-specific impact.
- Incident records and editorial review for broader service disruption signals.
- Historical baselines so a single short-lived failure does not become a false outage label.
How We Interpret HTTP and Network Results
A result on NepalStatus is not just a binary up-or-down label. We inspect the type of failure and whether it appears to be a site-level issue, a gateway issue, or a temporary edge condition.
Healthy response
Successful responses or normal redirects usually indicate the service is reachable.
Access or request issue
Examples include 404 Not Found, 403 Forbidden, and 429 Too Many Requests.
Server-side failure
Examples include 500, 502, 503, 504, and 505 responses when the origin or gateway is failing.
Name resolution issue
The hostname could not be resolved or pointed to an invalid target.
Slow or unreachable
The service did not respond within the expected window.
Handshake or certificate issue
The site may have expired certificates, mismatched names, or handshake problems.
Why This Matters
We aim to separate real service disruption from browser errors, routing issues, local connectivity problems, and temporary edge failures. That makes the platform more useful for users, operators, and support teams who need a clearer signal than a simple error page.
A Better Path for Reliability Content
We keep publication areas focused on practical guidance, incident analysis, and status methodology. When a page is not yet populated, we prefer a clear placeholder over a misleading label.
Editorial Standard
NepalStatus is independent and is not affiliated with monitored providers unless explicitly stated. We prefer precise language, evidence-backed status labels, and public explanations that are useful for both users and operations teams.