Nurbak Feature
Nurbak creates, tracks, and resolves incidents automatically so you never miss a failure.
Automatic API incident tracking means Nurbak creates an incident record the moment an endpoint fails for the first time. Each incident captures the start time, error type, and error message. When the endpoint recovers, the incident is automatically resolved with a human-readable duration like 45s, 23m, or 1.5h — giving your team a complete outage timeline without any manual work.
When a health check fails, Nurbak immediately creates an incident record with the exact timestamp, error type classification (timeout, DNS error, SSL error, connection refused, or HTTP error), and the raw error message.
While the endpoint remains down, the incident stays open with a status of active. Nurbak continues monitoring and recording each failed check. Per-region isolation ensures that a failure in one region does not create duplicate incidents.
The moment the endpoint responds successfully again, Nurbak automatically resolves the incident. The total duration is calculated and displayed in human-readable format — seconds, minutes, or hours — giving you a complete outage record.
No manual intervention needed. The instant an endpoint fails a health check, Nurbak opens an incident with full context including timestamp, error type, and error message.
When the endpoint starts responding successfully again, the incident is automatically marked as resolved. No need to close incidents manually or remember to update status pages.
Every resolved incident shows its total duration in a format humans can quickly understand — 45s for short blips, 23m for moderate outages, or 1.5h for extended downtime.
Incidents are categorized into 7 distinct error types including timeout, DNS resolution failure, SSL handshake error, connection refused, HTTP 4xx, HTTP 5xx, and unknown errors for fast root cause analysis.
If an endpoint is monitored from multiple regions, incidents are tracked per region. A DNS issue affecting only one geography will not create false incidents for regions where the endpoint is healthy.
Filter your incident history by status to see all currently active incidents at a glance or review resolved incidents for post-mortem analysis and reliability reporting.
No. Nurbak handles the entire incident lifecycle automatically. An incident is created the instant a health check fails, and it is resolved the moment the endpoint recovers. You can review all incidents in your dashboard with full details including duration, error type, and error messages. No manual status updates are ever required.
Nurbak classifies incidents into 7 error types based on the failure mode. Timeout means the endpoint did not respond within the allowed time. DNS error means the domain could not be resolved. SSL error indicates a certificate or handshake problem. Connection refused means the server rejected the connection. HTTP errors are split into 4xx and 5xx categories. Unknown covers any other failure.
Nurbak tracks incidents per monitoring region. If your endpoint fails health checks from the US East region but passes from EU West, only a US East incident is created. This per-region isolation prevents false positives and gives you accurate geographic failure data to help diagnose network-level or CDN-related issues.
Free during beta. No credit card required.
No spam. Unsubscribe anytime.
