Operations | Monitoring | ITSM | DevOps | Cloud

Explore how the $6.36B Binance breach exposed critical gaps in identity, DevOps, and signing security - and what engineering teams can learn from it. The October 29, 2026 theft from Binance is best read as a failure of identity and release-path trust, not a failure of cryptography. Binance's early findings point to a compromised DevOps engineer's laptop that gave an attacker a route into a service container and the ability to submit unauthorized withdrawals.

Think about Outlook, Salesforce or the shared drive your staff open each morning, and at least one of them probably runs in AWS, Azure or Google Cloud. That puts a good share of your traffic on a cloud network nobody on your team has ever seen. You still own a lot of that path (the VPN link, the route tables, the security groups), and it breaks in ways an office network doesn't.

You call your ISP because calls keep dropping and the Internet crawls every afternoon. Support asks you to restart the modem. Then they test the line from their side, see nothing wrong, and tell you everything looks fine on their end. By the time a technician shows up, the problem is gone, and the ticket gets closed. The issue usually isn't that your ISP doesn't care. First-line support is trained to rule out the customer's network first, and most complaints arrive with nothing they can check.

Most network diagrams we come across land in one of two piles: the one drawn for an audit years ago and never opened since, and the one so crowded that finding the firewall takes squinting. The network diagram examples below sit between those piles, 8 diagrams IT teams actually use, sorted into physical, logical, and cloud or WAN. For the full build process behind one map, see our guide to the network topology diagram.

Kepler has picked up a lot over the last few releases. So much, in fact, that Gyo, GitKraken’s Director of Engineering, had to trim his list before walking us through it. We sat down with Gyo and Jonathan, our Product Advocate, to go through the highlights. Gyo explained what shipped and why. Jonathan put the features to work live, building themes, cleaning up tasks, and forking a session from Claude to Codex. Here’s what we learned.

It's no secret that getting started with observability can be much harder than it should be. That's why, at ObservabilityCon 2025, we introduced Instrumentation Hub: a guided, scalable way to roll out observability coverage while still keeping you in control. Today, we’re excited to announce that Instrumentation Hub is now Generally Available in Grafana Cloud.

StatusGator’s audit logs now track more of your team’s activity, including changes to monitors, incidents, scheduled maintenance, status pages, and integrations. Previously, audit logs focused on sign-ins and account security. With this update, organization admins can also see who changed a monitor’s component filters, rescheduled maintenance, resolved an incident, or updated a status page’s password.

StatusGator webhooks now support user outage reports, so you can send reports from your status page to your own tools as soon as they’re confirmed. We’ve also added event settings to each webhook, letting you choose which notifications an endpoint receives. Use outage reports to create support tickets, alert your on-call team, or collect reports for analysis. Each payload includes the affected service, selected components, the reporter’s comment, and their approximate location.