# ilert

Alerting, on-call scheduling, incident communication and status pages from a German vendor.

- Website: https://www.ilert.com/
- Listing: https://openack.co/p/ilert
- Not evaluated. Listed by OpenACK: its 8 claimed capabilities are OpenACK's reading of the product's public site, not the maker's word, and nobody has checked them yet.

OpenACK's description (not checked):

> ilert receives alerts from monitoring tools, routes them through on-call schedules and escalation policies, and notifies responders by push, SMS, voice and chat. It also covers incidents, postmortems and status pages. The free plan includes up to five users, one schedule, one escalation policy, 100 SMS or voice notifications a month and one status page.

## Capabilities

- **not evaluated**: Send an alert to the service from a webhook or email
- **not evaluated**: Set who gets alerted with an on-call schedule
- **not evaluated**: Escalate an alert if nobody acknowledges it
- **not evaluated**: Acknowledge and resolve an alert
- **not evaluated**: Get an alert by SMS or phone call
- **not evaluated**: Get an alert in Slack
- **not evaluated**: Alert when a cron job stops checking in
- **not evaluated**: Publish a public status page

## What the statuses mean

- **confirmed** (ACK): a person from OpenACK signed in with a test account and saw it work.
- **not confirmed** (NAK or ?): it was tried and didn't work, or we couldn't reach or check it. Not proof it's missing, but not verified.
- **not evaluated** (—): nobody has checked it. It's the founder's word only.

Treat only "confirmed" as verified. A result is a record of one evaluation on the date shown, not a guarantee.