> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/changelog/2026/september-2026.md).

# September 2026

### New features and improvements

* 🎉 **AI SRE is now generally available** — investigations have left beta. Every paid plan now includes a monthly allotment of **AI credits**, shared between AI SRE investigations and the AI voice agent, and you can add **recurring credit upgrades** if your team needs more
* 🎉 **Service topology and the Service Health dashboard are now generally available** — after the closed beta we started in July, every team can now explore its own live service graph, built automatically from the traces your **telemetry sources** receive, to understand blast radius and likely root cause during an incident
* 🎉 We introduced **Global Actions** (closed beta) — standalone outbound actions that react to **alert and incident** lifecycle events, built from a catalog of action templates. The first templates cover **Jira, Zendesk, Zammad, GitHub, Mattermost** and **Discord**
* **AI SRE** investigations are easier to steer: chat messages you send while an investigation is running are queued as additional context, **Interrupt** lets your message take over right away, and **Stop** simply stops. The **agent creation wizard** got a refreshed layout, and the **AWS MCP** connection now also supports key-pair authentication
* **Dark mode** now offers a **Light / Dark / Follow system** preference
* The alert list filters moved into a **filter flyout**, giving the list more room — your **saved filters** stay one click away
* The **outbound email alert action** now supports **templating in the To, CC and BCC fields**
* The `ilert incidents` alert action is now called **Update status page**, making clear that it publishes a status update
* **Telemetry sources** and the services they discovered now link to each other, so you can jump from a telemetry source to its services and back
* The call flow **route call node** now uses the new multi-entity picker, letting you filter targets by users, schedules and teams
* Edit views now **warn responders before they remove the team that grants them permission** to manage a resource
* Notifications for newly created incidents no longer read "New update"
* All users have moved to the **vertical navigation**; the old horizontal navigation has been retired
* Mobile: the apps now **reopen where you left off**, clearly show when you are **offline**, and display an incident's **conference bridge** so you can join the call from your phone. The iOS app now requires **iOS 15** or later

### Integration updates

* We have introduced new inbound integrations: **Tideways** and **Bleemeo**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ilert.com/changelog/2026/september-2026.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
