**bees, need more bees **
also:
Please for the Love and understanding of all us. I have 400 hours in game till now. If it API service issues. I would personally migrate to different server option or service. Fire the team you have running servers at this current. Good read.
Infrastructure failure
When resource usage exceeds capacity, servers in an API backend may run slowly or become unresponsive. Individual nodes in a cluster can stop working due to local hardware failure, operating system crashes, application crashes, or loss of network connectivity to the rest of the cluster. When a node fails, clusters without failover capabilities can take the API endpoint offline.
Container orchestration is the layer that streamlines container deployment, management, scaling, and networking. Microservice APIs running on containers without proper orchestration may fail when the containers crash.
A widely adopted container orchestration technology is Kubernetes. APIs can experience outages when pods in a Kubernetes cluster crash and don't come up in another node. Kubernetes pods can crash for many reasons, including the following:
incorrect configuration
out-of-memory events
readiness probe failing
liveness probe check failing
application crashing
Network failure
Networks without redundant paths, connections, subnets, or devices can experience outages. The network architecture for APIs, therefore, should include failover zones, routing mechanisms, and load balancers.
High availability at a network level means the loss of a subnet in one part of the network does not disrupt the API. Client requests are seamlessly routed to a standby subnet with the same service running in it.
Without proper routing configuration, API gateways may not be able to send client requests to the appropriate API instance. An API gateway must employ either client-side or server-side discovery patterns to route requests to available service instances.