New integration announcement 📣 ilert + @DBmarlin With the ilert + DBmarlin integration you can route DBmarlin alert rules to the right responders, trigger reliable escalations, and have alerts resolve automatically once the condition clears — so incident response keeps moving and ilert reflects the real state of your databases. Learn more here: eu1.hubs.ly/H0z4yCr0

ilert is now a Silver Member of the @Cloud Native Computing Foundation (CNCF) and @The Linux Foundation. Most on-call pages our customers handle start somewhere in the cloud native stack. ilert integrates with CNCF projects like Prometheus and Kubernetes, and that is where the alerts originate long before an engineer gets woken up. Membership gets us closer to the projects and maintainers behind that stack, and into the working groups where observability and incident response practices get shaped. #CNCF #CloudNative #IncidentManagement

How can one failed DNSSEC key rollover make an entire national domain unreachable? The .al incident in July 2026 shows how withdrawing an old DNSKEY before updating the matching root record broke the DNSSEC chain of trust for Albania’s top-level domain. As cached records expired, validating resolvers began returning SERVFAIL, affecting access to government services, banks, media organizations, businesses, and other .al domains. In our latest postmortem, we break down what happened, how Cloudflare temporarily restored resolution for 1.1.1.1 users with a Negative Trust Anchor, and what teams can learn about DNSSEC key overlap, full-chain validation, independent emergency communication, and separating availability recovery from security recovery. Read the full breakdown 👇 eu1.hubs.ly/H0yXW5k0

Incident response does not have to be chaotic. 🤷🏻‍♂️ We built Compass into ilert as an incident lifecycle assistant. It suggests your next move when you need it, and stays quiet when you do not.

The EU AI Act got delayed. Partly. The Digital Omnibus (in force since July 27) moved high-risk obligations, including Article 73 serious-incident reporting, to December 2, 2027. AI embedded in regulated products moves to August 2, 2028. What didn't move: → Article 50 transparency has applied since August 2, 2026 → The Commission can now fine GPAI providers up to 3% of global turnover or €15M → NIS2, DORA and GDPR clocks are unchanged The new dates are fixed, not conditional. There's no scenario where they come early and no realistic one where they slip again.

How can a three-millisecond voltage drop lead to a cloud outage lasting nearly 15 hours? Google Cloud’s July 2026 incident shows how a brief electrical disturbance exposed failures across backup power and cooling systems in europe-west4-a. Feed A’s DRUPS failed, one server row lost power, and a chiller controller failed to restart the cooling pumps. As temperatures reached 44°C, Google shut down infrastructure to protect hardware and customer data. In our latest postmortem, we break down what happened, how Google restored VMware Engine, Bare Metal Solution, and NetApp Volumes, and what teams can learn about power redundancy, cooling dependencies, thermal monitoring, and dependency-ordered recovery. Read the full breakdown 👇 eu1.hubs.ly/H0yxsnL0

A nice little upgrade for your eyes! ilert now supports dark mode. Choose light, dark, or follow your system in the profile menu.

New integration announcement 📣 ilert + Bleemeo! @Bleemeo is a French monitoring platform, built in Toulouse since 2015, covering servers, containers and applications on open standards like Prometheus, with data hosted entirely in the EU. It now connects natively to ilert: threshold breaches reach the responder on duty through your escalation policy, and alerts close automatically once the issue clears. Two European vendors, one alerting chain that never leaves the EU. Learn more here: eu1.hubs.ly/H0yt5Cg0

Most incident response time is spent finding, not fixing. Tomorrow: September 22 at 3:00 PM CEST, we're doing a live session on what ilert AI SRE actually does during an incident: the full setup walkthrough, a real investigation end to end, and open Q&A with the team behind it. Register: eu1.hubs.ly/H0y4xcw0

Something has been cooking for months and is finally out: we are very excited to announce that ilert AI SRE is now generally available. 🎉 Here's the thing about a 3am page: the fix is usually fast. It's the search that eats your night: open the dashboard, check what deployed, grep the logs, ask in Slack who touched the database. AI SRE does that search. Hand it an alert or incident and a few minutes later you have a root cause hypothesis with a confidence label, evidence behind every finding, and a proposed action. Live today on every paid plan and during trials. Read more about the vision and the philosophy from our co-founder and CEO Birol Yildiz: eu1.hubs.ly/H0ylRL_0

Your incidents don't respect tool boundaries. Your incident response shouldn't either. ✨ Introducing our newest guide: The AI SRE Buyer's Guide: How to Evaluate Incident Response for a Multi-Tool Stack. Inside: - A 5-dimension framework for evaluating any AI SRE platform - 10 questions to take into every vendor call - The governance and EU data checks that matter before you buy Read more: eu1.hubs.ly/H0x_QJK0

We're very excited to announce that we will be the Platinum Sponsor of OSMC 2026, the Open Source Monitoring Conference, celebrating 20 years of monitoring excellence. OSMC is the annual meeting of international monitoring experts, where future trends and objectives are set and where specialists share the full scope of monitoring and observability, from technical deep dives to real-world best practices. Excited to see you in Nuremberg, November 17–19. eu1.hubs.ly/H0y4VL30 #OSMC

Evaluating an AI SRE solution but not sure where to start? ✨ Introducing our newest guide: The AI SRE Buyer's Guide: How to Evaluate Incident Response for a Multi-Tool Stack. Inside the AI SRE Buyer's Guide, you will find: - A 5-dimension framework for evaluating any AI SRE platform - 10 questions to take into every vendor call - The governance and EU data checks that matter before you buy Read here: eu1.hubs.ly/H0x_Rr40

How can the loss of one regional database replica disrupt ChatGPT, Codex, Voice, and other shared features? OpenAI’s July 2026 incident shows how cloud infrastructure maintenance reduced capacity for an internal identity service. The remaining regional capacity could not handle the full production workload, weakening cache effectiveness and increasing pressure on dependent services. Automated failover did not redirect enough traffic, leading to elevated errors for a subset of users. In our latest postmortem, we break down what happened, how OpenAI restored service in 57 minutes, and what teams can learn about replica-loss testing, capacity headroom, cache degradation, and automated cross-region failover. Read the full breakdown 👇 eu1.hubs.ly/H0xSnyD0

How can an automatic dependency update cause more than 36,800 AI code reviews to fail? GitHub Copilot’s June 2026 incident shows how an unpinned dependency introduced a version incompatible with the code review workflow’s runtime environment. The average failure rate reached 81.6%, peaking at 93.9%, while failed jobs remained active until their timeouts expired and continued consuming processing capacity. In our latest postmortem, we break down what happened, how GitHub rolled back the dependency and restored customer-facing service, and what teams can learn about dependency pinning, compatibility testing, fail-fast behavior, and separating service recovery from queue recovery. Read the full breakdown 👇 eu1.hubs.ly/H0xzpZX0

We are bringing our ilert community together for the very first time for the first edition of ilert Customer Day! ⏰ When? September 10, 2026 📍 Where? ilert HQ in Cologne, Germany We have planned a day of customer stories, hands-on workshops and honest conversations on incident management. If you are an ilert customer, check your inbox, or register here 👉 eu1.hubs.ly/H0xwmdd0

Managing incidents does not have to be a multiple tool job. ilert's incident management workspace brings everything your team needs to coordinate a major incident in one place: 👤 Commander: assign one person to lead the response. ⚡ Parallel escalations: page your on-call engineer, a full team, and a backup policy all at once. 💬 Incident channel: a dedicated channel created the moment you declare an incident. ⏰ Timeline: every action, page, and status change recorded automatically. Useful during the incident, essential for the post-mortem. Learn more: eu1.hubs.ly/H0xnL6X0

How can a degraded network path between two external providers disrupt CI jobs for nearly 30 hours? CircleCI’s July 2026 incident shows how routing and capacity problems between its third-party Mac infrastructure provider and GitHub caused macOS jobs to stall during code and dependency fetches. Fetch steps that normally took one to two minutes stretched to 20–30 minutes, while the intermittent nature of the issue made detection and recovery more difficult. In our latest postmortem, we break down what happened, how CircleCI and its provider mitigated the issue, and what teams can learn about inter-vendor dependencies, end-to-end monitoring, recurring failure patterns, and avoiding premature incident closure. Read the full breakdown 👇 eu1.hubs.ly/H0xhTNV0

No more context-switching mid-incident. Rich incident cards now render fully in Microsoft Teams and Google Chat, not just Slack. Acknowledge, escalate, and resolve without leaving the tool you're already in. Learn more: eu1.hubs.ly/H0x1YC20

Integration highlight: today we highlight our ilert x Site24x7 integration. ManageEngine Site24x7 gives you full-stack visibility: websites, servers, cloud infrastructure, apps, and networks. ilert makes sure something happens the moment it spots a problem. Feed Site24x7 alert notifications into ilert to ensure on‑call teams respond swiftly to website, server, or network outages. Monitoring tells you something's wrong. ilert makes sure the right person knows, fast. Read more here: eu1.hubs.ly/H0wKgwy0