Operations | Monitoring | ITSM | DevOps | Cloud

Slow Degradation Incident Response: The 7 Hour Ramp

At about 2 a.m. Eastern on Sunday, September 6, 2026, reports that Google services were failing started trickling into Downdetector. They did not spike. They climbed. By roughly 9 a.m. the volume was running about ten times higher than normal, with users saying that Google Search, Gmail, YouTube and YouTube TV were failing to load. That is a seven hour ramp, and it is the single hardest incident shape for an on-call team to catch.

How to Write Runbooks Your On-Call Team Actually Uses

Most engineering teams have on-call runbooks. Very few have on-call runbooks that anyone opens during an actual incident. The document exists, it was written with good intentions during a quiet sprint, it is linked from a wiki page called "Operations", and when the pager fires at 3 in the morning the responder ignores it completely and starts guessing in a terminal instead.

Driving Impact and AI Adoption as an FDE

Enterprise AI is only useful when it actually runs in production, inside the tools teams already depend on. Getting there is harder than it sounds. Forward Deployed Engineers at Atlassian work directly inside some of the world's largest organizations, building AI-powered agents, connectors, and workflows on Atlassian's platform. They work alongside customers to understand the real constraints, design solutions that hold up at scale, and see them through to deployment.

Why Founders Pivot, and Why You Should Too | Atlassian for Startups | Atlassian

In the Startup Stories with Atlassian series, we interview founders about their entrepreneurial journey, learn about the problems they are trying to solve, and explore how their teams are using Atlassian tools to grow and deliver value to their customers. In this episode of Startup Stories with Atlassian, Adam sits down with Stan Suchkov, Founder and CEO of Evolve, to explore why pivoting isn't the failure most founders fear – and why the best founders do it deliberately, quickly, and without losing their team in the process.

We Benchmarked AI Models on Git Tasks. Results Surprised Us

Most AI model benchmarks measure general coding ability or reasoning. GitBench, built by GitKraken developer advocate Chris Griffing, measures something narrower and more practical: how well a given AI model handles specific Git tasks, starting with commit squashing, identifying which commits in a messy history should be combined into one clean commit.

Assign Bugs and Tickets to the Current On-Call, Automatically

There is a particular kind of ticket that costs more than it should. It is filed correctly, it has a good description, it is in the right project, and it has nobody's name on it. It sits in the queue for two days because everyone who looks at the board assumes someone else has it. Then a customer follows up, someone notices, and the fix takes twenty minutes. The gap was never engineering time. It was ownership.

Identity Provider Outage: The On-Call Blast Radius

An identity provider outage is the one failure mode where your dashboards stay green and your entire company stops working anyway. On August 31, 2026, Microsoft acknowledged a widespread Exchange Online incident at 5:30 PM UTC, tracked as EX1464935, and described it in the admin center as "a common failure pattern across affected Exchange Online requests that is associated with authentication and protocol connectivity." Tens of thousands of users were affected according to Downdetector.

Run an Incident Response Game Day for Your On-Call Team

An incident response game day is the cheapest reliability investment most engineering teams still refuse to make. The 2026 Catchpoint SRE Report, based on 418 responses from reliability professionals worldwide, names it as one of five defining trends: resilience has to be practiced. Teams that deliberately test failure report more confidence and better preparedness. And yet the same report finds production chaos engineering is still far from standard practice.

GitKraken Desktop 12.4 Release: Multiple WIPs, Approve/Deny Agents, and more!

What if you could counterspell an agent action? GitKraken Desktop 12.4 pulls the whole AI agent workflow into one place, so you stay in the flow. Back in 12.0 we shipped Agent Sessions, where you kick off AI coding agents right inside the context of your repo. GitKraken 12.4 builds on that. What's new in 12.4: This release is not about handing more of your work to agents. It's about seeing everything they do, and deciding what actually changes.

Kepler: Coordinate Every AI Coding Agent From One Place

Kepler is GitKraken's new agentic development environment (ADE), and it's now in public preview for Windows, Mac, and Linux. If GitKraken Desktop is built to go deep on one repository, Kepler is built to go wide: one task, multiple repositories, multiple AI agents, tracked in a single place instead of a dozen open terminals.