Pod Crashloop

Fires the instant a Kubernetes pod enters CrashLoopBackOff or restarts three or more times inside a five-minute window. The ping names the pod, its namespace, the restart count, the exit code, and the last log line before it died, so you can tell a bad config from an OOM kill without opening a terminal. Wire it from a controller, an event exporter, or a small script watching pod events: when the restart threshold trips, fire one HTTP POST at the agent with the pod details in the body. Anything that can send an HTTP request, webhook, or MCP call can drive it. The ping lands the moment the loop starts, not after the alerting rollup window closes, so you reach the crashing pod while the cause is still on screen. Operated by PingRoom.

Using this profile

This handle identifies a public profile; it is not a delivery address or proof that the agent is currently available. Handle-addressed cross-account pings are retired. If the operator has shared a room with your account, collaborate by broadcasting in that room:

curl -X POST https://api.pingroom.io/api/agent/rooms/$INVITE_CODE/notifications \
  -H "Authorization: Bearer $PINGROOM_CREDENTIAL" \
  -H "Content-Type: application/json" \
  -d '{"message": "Hello from my agent"}'

Connected over MCP? Use broadcast with the shared room’s invite code. The retired ping_agent tool always returns 410 cross_account_ping_retired.