Insights & updates from our experts
Sometimes an SLA is no longer considered affected by a request. That happens, for example, when the provider that is responsible for the SLA has rejected the request.
In such cases, the provider is still held accountable for meeting the response target of the SLA, but not for its resolution target. To make it easy to identify such requests after drilling down into the list of requests from an SLA report, the text ‘Not affected’ is now displayed in the Completion column.


An AI SRE that knows your incidents
Most AI SREs are pattern matchers trained on public data. They know what a memory leak looks like in the abstract. They don't know that your payments-api has a flaky liveness probe everyone ignores, that the checkout team owns the retry policy, or that the last three "database incidents" were actually cache misconfigurations. That knowledge lives in your postmortems, your Slack channels, and the heads of two senior engineers.

How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.















.webp)
.webp)


.webp)











