English
Statping-ng Hosting
Monitor services and share a public status page with incident history and alerts.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Official links
Statping-ng’s official links and original website
Statping-ng Website
More
Tech
- Docker image
- adamboutcher/statping-ng:latest
- Default port
- 8080
How Statping-ng works
Statping-ng lets administrators add services for HTTP, TCP, UDP, ICMP, and gRPC monitoring, then displays current state, response information, history, groups, messages, and announcements on a status page. HTTP checks can use different methods and validate response content. Notifiers connect service changes to external communication systems when the necessary credentials are configured.
The catalogue persists /app but does not generate a unique initial login. Upstream documents the default administrator credentials as admin / admin, so operators must change them immediately after first access. A public status page can be viewed separately from the administrative dashboard, and each monitored target, notifier, OAuth provider, and API consumer needs explicit configuration.
Key Statping-ng features
Statping-ng supports several network protocols, response matching, service groups, announcements, notifiers, an API, a Prometheus metrics endpoint, styling options, and optional OAuth providers. Those capabilities depend on correct configuration and external services. The mobile application is separate from the hosted package, and upstream notes that it is not maintained by the Statping-ng project.
Application email is disabled across the hosting service cloud apps, so the built-in SMTP notifier cannot be promised. Other notifier credentials, OAuth clients, public communication policy, and monitoring targets are also not included. As with any monitor hosted in one location, a passing result reflects that path and condition rather than every user, region, or end-to-end workflow.
Statping-ng vs UptimeRobot
Statping-ng is a self-hosted monitoring server and status page that the operator configures and maintains. UptimeRobot offers provider-hosted monitoring, alert integrations, incident tools, and public status pages through its managed plans. The provider operates the checking service, while Statping-ng leaves placement, credentials, upgrades, notifier setup, and status-page governance to the customer.
UptimeRobot may suit teams that want external hosted checks, a commercial service interface, and provider-managed integrations without running monitoring infrastructure. Statping-ng fits operators who prefer a browser-managed self-hosted status system and accept responsibility for securing default credentials, selecting check locations, configuring alerts, and keeping communication available during outages.
Who uses Statping-ng
Small hosting operators monitor websites and ports, software teams publish service groups for customers, and communities share announcements and incident history from one page. Administrators can connect selected failures to existing chat, webhook, or notification services when separately configured.
Statping-ng is not a distributed observability platform, browser transaction system, log analyser, performance profiler, root-cause engine, or assurance that every user can reach a service. The monitor should be separated from the systems it observes when the status page must survive their failure.
Self-hosting Statping-ng: requirements and cost
Statping-ng resource use depends on service count, polling interval, protocol, response validation, history, notifier activity, metrics collection, and status-page traffic. PostgreSQL and MariaDB are Not required by this catalogue template; the persistent /app volume stores its local state. The software carries no separate application fee, while many frequent checks can increase network and processing load.
On AvaHost, Statping-ng uses Plan 1 at €2. The hosted Statping-ng package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. The package persists Statping-ng data but starts with upstream default admin credentials that must be changed. It does not create monitoring targets, independent locations, notifier or OAuth credentials, incident staffing, or application email. Customers must secure administration, configure non-email integrations, and consider hosting the status path outside monitored failure domains.
F.A.Q
Statping-ng starts at €2 on Plan 1. That plan suits a modest number of checks at sensible intervals. Service count, polling frequency, protocols, response matching, history, notifier activity, metrics scraping, and public status traffic determine when more capacity is appropriate. External probe networks and incident-response staff are not included.
A custom domain can point to Statping-ng, with automated HTTPS applied after DNS is configured. Update bookmarks, API clients, OAuth callbacks, metrics consumers, mobile-app connections, and published status links to the final hostname. Test the public page and administrative interface separately before announcing the address to customers or stakeholders.
Upstream documents the initial administrator login as username `admin` and password `admin`, and the catalogue does not replace it with a generated secret. Change both credentials immediately, review additional users and API secrets, and restrict the administrative interface. Public status visibility should not imply public access to configuration, services, notifiers, or incident controls.
Application email is disabled, so SMTP notifications are not available from this hosted package. Statping-ng supports other notifiers and OAuth providers, but customers must create the external accounts, supply credentials, and test delivery. Automatic application updates and scheduled backups protect the hosted installation, not a third-party integration or an incident communication process.