How It Works

NepalStatus uses evidence-based monitoring. Public status labels are computed from reports, automated checks, official signals, and incident workflow rules.

1) Inputs We Collect

• User reports from service pages and report forms.
• Automated HTTP system checks for services that have check URLs configured.
• Official provider signals and admin-created incident entries.

2) Evidence Window and Freshness

• Primary user evidence window: last 15 minutes.
• Fresh successful checks inside 10 minutes are treated as positive evidence.
• Repeated failed checks are stronger than one failed probe.

3) Public Status Rules

• No evidence and no configured check: Checking.
• No reports and healthy check: No current problems.
• Small report volume: Reports detected.
• Single failed/slow check: Possible problem.
• Combined strong signals or active incidents: Service disruption.
• Maintenance flags and official maintenance: Under maintenance.

4) Incident Lifecycle

• Incidents open when thresholds show meaningful disruption risk.
• Incident timelines are updated with investigation/resolution notes.
• Incidents resolve after evidence returns toward baseline.

5) Domain Check and Monitoring Requests

• One-time website checks are immediate and can be used for unknown domains.
• If a domain is not yet monitored, users can suggest monitoring or report an issue.
• Auto-approval queue can convert pending domains into tracked services with automated checks enabled.

6) Editorial Standards

• Editorial posts include experience, expertise, authority, and trust notes to support publishing quality.
• Contact submissions route to the support inbox for operations follow-up.
• NepalStatus is independent and not affiliated with monitored providers.

FAQ