you are viewing a single comment's thread
view the rest of the comments
[–] 130 points 1 week ago (22 children)

What my agency has been told.

Latest as of 2026-11-12 2:18:39 PM (EST)

Status: Investigating
We've determined that the elevated load isn't driven by an overall increase in traffic, but by a large number of servers being unexpectedly unavailable, which is shifting load onto the remaining infrastructure. We're investigating what's causing these servers to become unavailable while we work to safely return them to service.

Maybe they should try asking copilot why all those serves are unavailable.

  • source
  • hideshow 22 child comments
  • [–] [S] 61 points 1 week ago* (9 children)
  • [–] 56 points 1 week ago (6 children)

    Is Clippy alright? Is he safe?

  • source
  • parent
  • hideshow 6 child comments
  • [–] 21 points 1 week ago (3 children)

    I don't think anyone has heard from Clippy. I'm really worried right now.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 17 points 1 week ago

    "You're absolutely right, turning those servers off as a cost-cutting effort was a mistake, and has caused more problems than it has solved. I'm still learning, so I appreciate your understanding and patience 🙏"

  • source
  • parent
  • [–] 7 points 1 week ago

    Something something paired core routers went down during audit tasks in AMER and EMEA knocking 2 AZs offline at the same time. Automation did what automation do and eff it all up. Now it takes all hands on deck to untangle it.

    The internal messaging is nuts.

  • source
  • parent
  • [–] 3 points 1 week ago (2 children)

    load balancers are just turned into total load takers.

  • source
  • parent
  • hideshow 2 child comments