Nurbak Feature
Configure intelligent alert rules with custom thresholds for downtime, latency, error rates, and SSL expiry.
API alert rules let you define custom conditions that trigger notifications when your endpoints misbehave. Nurbak supports four alert types — API Down, High Latency, Error Rate, and SSL Certificate Expiry — each with configurable thresholds. An anti-spam cooldown prevents notification floods, and per-endpoint routing is available on Pro and Team plans.
Select from four alert types tailored to different failure modes. API Down detects the first failure, High Latency triggers on slow responses, Error Rate monitors 4xx/5xx percentages, and SSL Expiry warns before certificates expire.
Configure the exact conditions that matter to your team. Set latency thresholds in milliseconds, error rate percentages over a sliding window, or the number of days before SSL certificate expiration to trigger a warning.
Send alerts to email, Slack, or webhooks. On Pro and Team plans, configure per-endpoint routing so the right team gets notified for the right service. Anti-spam cooldown ensures you never get duplicate alerts within one hour.
Get notified on the very first failed health check. No waiting for consecutive failures — Nurbak alerts you immediately when an endpoint stops responding.
Set a maximum acceptable response time in milliseconds. When any health check exceeds your threshold, Nurbak triggers an alert so you can investigate before users notice.
Track the percentage of 4xx and 5xx responses over a sliding window of 20 checks. Get alerted when error rates cross your defined threshold, catching intermittent issues early.
Configure how many days before certificate expiration you want to be warned. Never get caught off guard by an expired SSL certificate taking your API offline.
After an alert fires, Nurbak enforces a 1-hour cooldown period for that specific rule and endpoint combination. This prevents notification floods during extended outages or flapping services.
On Pro and Team plans, route alerts from different endpoints to different channels. Send payment API alerts to the billing team and auth API alerts to the security team.
Nurbak alerts on the very first failed health check. Since checks run every 30 seconds from multiple regions, you will typically be notified within 30 to 60 seconds of an outage starting. The alert is sent immediately — there is no requirement for consecutive failures before notification, so you get the fastest possible detection.
The 1-hour anti-spam cooldown prevents notification floods during flapping. After the first alert fires, you will not receive another alert for the same rule and endpoint combination for one hour. The incident tracking system continues recording each failure, so you have full visibility into the flapping pattern even without repeated notifications.
Yes. Each alert rule is configured independently and can target specific endpoints. On the Free plan, alerts go to a single notification channel. On Pro and Team plans, you can route alerts from different endpoints to different Slack channels, email addresses, or webhook URLs, ensuring the right team is notified for each service.
Free during beta. No credit card required.
No spam. Unsubscribe anytime.
