---
title: "Prateek Srivastava (@prateeksrivastav598) | Hashnode"
description: "SRE & DevOps Engineer | Kubernetes, Multi-Cloud, Linux | Writing about real production systems. Read the latest articles by Prateek Srivastava on Hashnode."
url: "https://hashnode.com/@prateeksrivastav598"
---

@prateeksrivastav598

# Prateek Srivastava

@prateeksrivastav598 · Bangalore, India · Joined August 2026

SRE & DevOps Engineer | Kubernetes, Multi-Cloud, Linux | Writing about real production systems

### [GCP Is Running Out of N2 Machines in us-central1 — And It's Silently Breaking Production Clusters](https://prateeksrivastav598.hashnode.dev/gcp-is-running-out-of-n2-machines-in-us-central1-and-it-s-silently-breaking-production-clusters?utm_source=hashnode&utm_medium=feed)

🔴 Ongoing · Reports active since April 2026 · No official GCP acknowledgement

6 min read · [prateeksrivastav598.hashnode.dev](https://prateeksrivastav598.hashnode.dev/gcp-is-running-out-of-n2-machines-in-us-central1-and-it-s-silently-breaking-production-clusters?utm_source=hashnode&utm_medium=feed)

[Aug 27](https://hashnode.com/posts/gcp-is-running-out-of-n2-machines-in-us-central1-and-it-s-silently-breaking-production-clusters/6a90748bf5604d063a7534d6)

### [Claude Went Down Today. And It Says More About AI Than You Might Think !!!!](https://prateeksrivastav598.hashnode.dev/claude-went-down-today-and-it-says-more-about-ai-than-you-might-think?utm_source=hashnode&utm_medium=feed)

If you tried to use Claude today and suddenly got errors, failed responses, or a model that just refused to cooperate, you weren’t imagining things.

7 min read · [prateeksrivastav598.hashnode.dev](https://prateeksrivastav598.hashnode.dev/claude-went-down-today-and-it-says-more-about-ai-than-you-might-think?utm_source=hashnode&utm_medium=feed)

[Aug 24](https://hashnode.com/posts/claude-went-down-today-and-it-says-more-about-ai-than-you-might-think/6a8c072d542056c3227ff06a)

### [A Windows Service is Down. Now What?](https://prateeksrivastav598.hashnode.dev/a-windows-service-is-down-now-what?utm_source=hashnode&utm_medium=feed)

A repeatable 5-step investigation methodology for any Windows service alert — Windows Event Logs, service transitions, shutdown events, and app logs — with SQL Server as a worked example at every step.

8 min read · [prateeksrivastav598.hashnode.dev](https://prateeksrivastav598.hashnode.dev/a-windows-service-is-down-now-what?utm_source=hashnode&utm_medium=feed)

[1](https://hashnode.com/posts/a-windows-service-is-down-now-what/6a8b4af4febcd7643db171fc) [Aug 23](https://hashnode.com/posts/a-windows-service-is-down-now-what/6a8b4af4febcd7643db171fc)

### [I Managed Kubernetes Across AWS, Azure, and GCP Simultaneously — Here's What Nobody Tells You"](https://prateeksrivastav598.hashnode.dev/i-managed-kubernetes-across-aws-azure-and-gcp-simultaneously-here-s-what-nobody-tells-you?utm_source=hashnode&utm_medium=feed)

"The day the same Helm chart behaved differently on three clouds in the same hour was the day I stopped trusting cloud-agnostic as a real thing."

8 min read · [prateeksrivastav598.hashnode.dev](https://prateeksrivastav598.hashnode.dev/i-managed-kubernetes-across-aws-azure-and-gcp-simultaneously-here-s-what-nobody-tells-you?utm_source=hashnode&utm_medium=feed)

[Aug 21](https://hashnode.com/posts/i-managed-kubernetes-across-aws-azure-and-gcp-simultaneously-here-s-what-nobody-tells-you/6a88a013dbe5c5f82ae57638)

### [Our EKS Node Crashed and Four Auto-Recovery Mechanisms All Failed. Here's Why.](https://prateeksrivastav598.hashnode.dev/our-eks-node-crashed-and-four-auto-recovery-mechanisms-all-failed-here-s-why?utm_source=hashnode&utm_medium=feed)

Four different layers of protection. Four completely different failure modes. One node stuck NotReady for 4 hours.

9 min read · [prateeksrivastav598.hashnode.dev](https://prateeksrivastav598.hashnode.dev/our-eks-node-crashed-and-four-auto-recovery-mechanisms-all-failed-here-s-why?utm_source=hashnode&utm_medium=feed)

[Aug 20](https://hashnode.com/posts/our-eks-node-crashed-and-four-auto-recovery-mechanisms-all-failed-here-s-why/6a86e714d07b8a9cbe7ac7b9)
