Question

Your team launched a new internal API six weeks ago with an availability SLO of 99.0% while it stabilized. Since then, the service has consistently delivered 99.7% availability, error budget burn has been minimal, and downstream teams have begun building critical workflows on top of it. Leadership asks how you should adjust reliability targets as the service matures. What is the most appropriate SRE-aligned action?

Accepted Answer

Review consumer dependencies and observed performance, then incrementally tighten the SLO (e.g., to 99.5%) to a level that reflects actual user needs and is sustainably achievable.

Answer

Raise the SLO to 99.99% immediately to match the highest reliability the service has ever briefly achieved, ensuring maximum headroom for downstream consumers.

Answer

Keep the SLO at 99.0% permanently, since the service is already exceeding it and there is no reason to change a target that is being met.

Answer

Remove the SLO entirely now that the service is stable, and rely on the observed 99.7% availability as an informal benchmark.