<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reliability on Prakash Khadka</title><link>https://prakash-khadka.com.np/tags/reliability/</link><description>Recent content in Reliability on Prakash Khadka</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 10 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://prakash-khadka.com.np/tags/reliability/index.xml" rel="self" type="application/rss+xml"/><item><title>Why I Prefer SLOs Over Uptime Targets</title><link>https://prakash-khadka.com.np/notes/slos-over-uptime/</link><pubDate>Tue, 10 Nov 2026 00:00:00 +0000</pubDate><guid>https://prakash-khadka.com.np/notes/slos-over-uptime/</guid><description>&lt;h1 class="heading" id="understanding-slos-and-error-budgets">
 Understanding SLOs and Error Budgets
 &lt;a class="anchor" href="#understanding-slos-and-error-budgets">#&lt;/a>
&lt;/h1>
&lt;p>&amp;ldquo;We need 99.99% uptime&amp;rdquo; sounds like a clear goal, but what does it actually mean for users?&lt;/p>
&lt;p>A service can be up while users are experiencing failed requests or slow responses. Uptime alone doesn&amp;rsquo;t tell us whether the service is working as expected.&lt;/p>
&lt;h2 class="heading" id="what-is-an-slo">
 What is an SLO?
 &lt;a class="anchor" href="#what-is-an-slo">#&lt;/a>
&lt;/h2>
&lt;p>An SLO (Service Level Objective) defines how reliable a service should be. It consists of three parts:&lt;/p></description></item></channel></rss>