{"id":1671,"date":"2026-02-15T05:27:30","date_gmt":"2026-02-15T05:27:30","guid":{"rendered":"https:\/\/sreschool.com\/blog\/follow-the-sun\/"},"modified":"2026-02-15T05:27:30","modified_gmt":"2026-02-15T05:27:30","slug":"follow-the-sun","status":"publish","type":"post","link":"https:\/\/sreschool.com\/blog\/follow-the-sun\/","title":{"rendered":"What is Follow the sun? Meaning, Architecture, Examples, Use Cases, and How to Measure It (2026 Guide)"},"content":{"rendered":"\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Quick Definition (30\u201360 words)<\/h2>\n\n\n\n<p>Follow the sun is a staffing and operational model that routes work to teams in time zones where business hours are active, ensuring near-continuous service coverage. Analogy: like relay runners passing a baton around a circular track so the race never stops. Formal: a distributed availability and handoff pattern for operational continuity.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">What is Follow the sun?<\/h2>\n\n\n\n<p>Follow the sun is an operational and staffing model combined with technical patterns that route tasks, incidents, and operational responsibilities to teams located across different time zones to provide near-continuous coverage without requiring 24\/7 single-location staffing.<\/p>\n\n\n\n<p>What it is NOT:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Not simply global on-call duplication.<\/li>\n<li>Not a single-technology solution; it is an organization + process + tooling pattern.<\/li>\n<li>Not automatic; requires clear handoffs, SLAs, and automation to work reliably.<\/li>\n<\/ul>\n\n\n\n<p>Key properties and constraints:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Temporal handoffs: ownership moves along predictable local-business-hour boundaries.<\/li>\n<li>Regional autonomy: local teams control immediate fixes within boundaries.<\/li>\n<li>Escalation paths: defined global escalation for unresolved or complex incidents.<\/li>\n<li>Data residency and compliance constraints may limit full automation.<\/li>\n<li>Latency and context transfer overhead across handoffs are real costs.<\/li>\n<\/ul>\n\n\n\n<p>Where it fits in modern cloud\/SRE workflows:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Incident response orchestration integrated with CI\/CD, observability, and runbooks.<\/li>\n<li>Enforced SLIs\/SLOs with distributed incident routing and automated handoffs.<\/li>\n<li>Cloud-native patterns for multi-region deployment, global load balancing, and service mesh routing.<\/li>\n<li>AI\/automation assists context transfer, triage summarization, and routine remediation.<\/li>\n<\/ul>\n\n\n\n<p>A text-only diagram description readers can visualize:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Global timeline circle with segments labeled APAC, EMEA, Americas; arrows moving clockwise representing handoffs; inner layer shows monitoring and automated routing; outer layer shows teams and escalation links.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Follow the sun in one sentence<\/h3>\n\n\n\n<p>Follow the sun is the coordinated practice of routing operational responsibilities to teams during their local business hours to maintain continuous effective coverage while minimizing burnout and cost.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Follow the sun vs related terms (TABLE REQUIRED)<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>ID<\/th>\n<th>Term<\/th>\n<th>How it differs from Follow the sun<\/th>\n<th>Common confusion<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>T1<\/td>\n<td>24&#215;7 on-call<\/td>\n<td>Single team covers all hours rather than handing off<\/td>\n<td>Often assumed same as 24&#215;7 coverage<\/td>\n<\/tr>\n<tr>\n<td>T2<\/td>\n<td>Follow the moon<\/td>\n<td>Focuses on night-only support rather than local business hours<\/td>\n<td>People mistake it for opposite model<\/td>\n<\/tr>\n<tr>\n<td>T3<\/td>\n<td>Shift rotation<\/td>\n<td>Rotates people inside one timezone not across regions<\/td>\n<td>Thought to solve timezone coverage<\/td>\n<\/tr>\n<tr>\n<td>T4<\/td>\n<td>Global NOC<\/td>\n<td>Centralized operations center vs distributed ownership<\/td>\n<td>Assumed identical to distributed teams<\/td>\n<\/tr>\n<tr>\n<td>T5<\/td>\n<td>Follow the sun with Handoff Automation<\/td>\n<td>Includes automated context transfer vs manual handoffs<\/td>\n<td>Automation level often unclear<\/td>\n<\/tr>\n<tr>\n<td>T6<\/td>\n<td>Multiregion deployment<\/td>\n<td>Infrastructure placement not staffing model<\/td>\n<td>Confused because both reduce latency<\/td>\n<\/tr>\n<tr>\n<td>T7<\/td>\n<td>Active-active support<\/td>\n<td>Multiple regions working concurrently not sequential handoffs<\/td>\n<td>Mistaken for handoff-only model<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h4 class=\"wp-block-heading\">Row Details (only if any cell says \u201cSee details below\u201d)<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>None<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Why does Follow the sun matter?<\/h2>\n\n\n\n<p>Business impact:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Revenue: Faster incident remediation reduces downtime and lost transactions.<\/li>\n<li>Trust: Customers see consistent SLAs and regional responsiveness.<\/li>\n<li>Risk: Avoid concentration risk from single-region failures or single-team burnout.<\/li>\n<\/ul>\n\n\n\n<p>Engineering impact:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Incident reduction: Local expertise shortens MTTR for region-specific issues.<\/li>\n<li>Velocity: Teams can deploy and respond during their business hours, reducing review lag.<\/li>\n<li>Knowledge continuity risks if handoffs are poor.<\/li>\n<\/ul>\n\n\n\n<p>SRE framing:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>SLIs\/SLOs: Follow the sun aims to meet SLOs by improving coverage during peak regional hours.<\/li>\n<li>Error budgets: Distributed ownership allows targeted error budget consumption per region.<\/li>\n<li>Toil: Automate routine handoffs and remediation to reduce human toil.<\/li>\n<li>On-call: Moves from single-person 24&#215;7 to predictable business-hour responsibilities and escalation.<\/li>\n<\/ul>\n\n\n\n<p>3\u20135 realistic \u201cwhat breaks in production\u201d examples:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>DNS misconfiguration in a primary region causes failed API calls for customers in that region.<\/li>\n<li>Scheduled database migration leads to unexpected lock contention during overlapping deployments.<\/li>\n<li>Third-party payment gateway times out for a specific region during local peak hours.<\/li>\n<li>CI\/CD pipeline misconfiguration pushes a bad image to multiple regions; localized rollbacks needed.<\/li>\n<li>IAM policy change accidentally revokes service account permissions within one region.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Where is Follow the sun used? (TABLE REQUIRED)<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>ID<\/th>\n<th>Layer\/Area<\/th>\n<th>How Follow the sun appears<\/th>\n<th>Typical telemetry<\/th>\n<th>Common tools<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>L1<\/td>\n<td>Edge and network<\/td>\n<td>Regional routing and DDoS response handled locally<\/td>\n<td>Traffic patterns latency and errors<\/td>\n<td>Global LB WAF CDN<\/td>\n<\/tr>\n<tr>\n<td>L2<\/td>\n<td>Service and app<\/td>\n<td>Localized incident ownership for microservices<\/td>\n<td>Request rate latency error rates<\/td>\n<td>APM logs traces<\/td>\n<\/tr>\n<tr>\n<td>L3<\/td>\n<td>Data and storage<\/td>\n<td>Region-aware failover and read replicas<\/td>\n<td>Replication lag consistency<\/td>\n<td>DB metrics backups<\/td>\n<\/tr>\n<tr>\n<td>L4<\/td>\n<td>Kubernetes<\/td>\n<td>Regional clusters with local SRE owners<\/td>\n<td>Pod restarts node health<\/td>\n<td>K8s metrics kubelet logs<\/td>\n<\/tr>\n<tr>\n<td>L5<\/td>\n<td>Serverless\/PaaS<\/td>\n<td>Region-specific alerts and scaling policies<\/td>\n<td>Invocation duration error count<\/td>\n<td>Cloud function metrics<\/td>\n<\/tr>\n<tr>\n<td>L6<\/td>\n<td>CI\/CD<\/td>\n<td>Region-targeted pipelines and gated releases<\/td>\n<td>Pipeline success times and failures<\/td>\n<td>CI logs artifacts<\/td>\n<\/tr>\n<tr>\n<td>L7<\/td>\n<td>Observability<\/td>\n<td>Local dashboards and synthetic checks<\/td>\n<td>SLI dashboards alert rates<\/td>\n<td>Observability platforms<\/td>\n<\/tr>\n<tr>\n<td>L8<\/td>\n<td>Security\/Compliance<\/td>\n<td>Local incident triage for security events<\/td>\n<td>Auth failures audit logs<\/td>\n<td>SIEM IAM tools<\/td>\n<\/tr>\n<tr>\n<td>L9<\/td>\n<td>Customer support<\/td>\n<td>Handoff for escalations during local hours<\/td>\n<td>Ticketing SLA times<\/td>\n<td>Ticketing systems<\/td>\n<\/tr>\n<tr>\n<td>L10<\/td>\n<td>Business ops<\/td>\n<td>Billing anomalies and fraud checks by region<\/td>\n<td>Cost anomalies billing alerts<\/td>\n<td>Cloud billing tools<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h4 class=\"wp-block-heading\">Row Details (only if needed)<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>None<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">When should you use Follow the sun?<\/h2>\n\n\n\n<p>When it\u2019s necessary:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>You have global customers in multiple active business regions needing rapid response.<\/li>\n<li>Region-specific regulations require local control or data residency.<\/li>\n<li>Latency-sensitive services require regional operational ownership.<\/li>\n<\/ul>\n\n\n\n<p>When it\u2019s optional:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Low-traffic global services with tolerant SLAs.<\/li>\n<li>Teams comfortable with distributed async handoffs and asynchronous communication.<\/li>\n<\/ul>\n\n\n\n<p>When NOT to use \/ overuse it:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Small organizations lacking the staffing maturity to manage multiple regional teams.<\/li>\n<li>When the overhead of handoffs outweighs the benefits, e.g., very low incident frequency.<\/li>\n<li>Where security\/compliance forbids cross-region access and automation.<\/li>\n<\/ul>\n\n\n\n<p>Decision checklist:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>If user base in 3+ active regions AND MTTR impacts revenue -&gt; adopt Follow the sun.<\/li>\n<li>If incidents are rare AND SLOs lenient -&gt; consider async on-call with regional escalation.<\/li>\n<li>If compliance requires local custody AND capacity exists -&gt; prefer local ownership.<\/li>\n<\/ul>\n\n\n\n<p>Maturity ladder:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Beginner: Single-region teams, documented handoffs, global escalation on-call.<\/li>\n<li>Intermediate: Multiple regional teams, automated summaries and partial routing, regional dashboards.<\/li>\n<li>Advanced: Automated incident routing, AI triage and handoff, active-active autonomy, regional CI\/CD gating.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">How does Follow the sun work?<\/h2>\n\n\n\n<p>Components and workflow:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Monitoring and alerting that detects incidents and classifies by region\/impact.<\/li>\n<li>Routing\/orchestration layer mapping incidents to on-call regional teams during local hours.<\/li>\n<li>Handoff artifacts: incident summary, logs, traces, runbook links, and priority.<\/li>\n<li>Escalation paths to regional leads and global escalation team if unresolved.<\/li>\n<li>Automation for known remediations, rollback, or traffic shifting.<\/li>\n<\/ul>\n\n\n\n<p>Data flow and lifecycle:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Synthetic or real-user monitoring detects issue.<\/li>\n<li>Alerting system enriches with context and assigns to local timezone owner.<\/li>\n<li>Team receives incident, attempts remediation using runbooks and automation.<\/li>\n<li>If unresolved by X minutes, escalate to next level or region.<\/li>\n<li>Post-incident: automated report generated, ownership transfers to follow-up team for RCA.<\/li>\n<\/ol>\n\n\n\n<p>Edge cases and failure modes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Midnight handoffs where fewer staff are available on the receiving side.<\/li>\n<li>Clock drift or DST misalignment causing routing errors.<\/li>\n<li>Network partitions that make regional teams unable to access necessary telemetry.<\/li>\n<li>Compliance blocks preventing cross-region remediation.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Typical architecture patterns for Follow the sun<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Regional Ownership Pattern: Each region runs full stack and owns incidents during local hours. Use when regulatory autonomy is needed.<\/li>\n<li>Handoff-Orchestrator Pattern: Central orchestration service routes incidents to region owners and holds the global view. Use when you need consistency.<\/li>\n<li>Active-Active with Local Failover: All regions active but local teams own incidents in local time windows. Use when low latency and redundancy required.<\/li>\n<li>Automation-first Pattern: Heavy automation for repetitive tasks reduces human handoffs. Use when repetitive operational tasks dominate.<\/li>\n<li>Tiered Support Pattern: Local teams handle Tier 1, centralized experts handle Tier 2\/3 across timezones. Use when expertise is scarce.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Failure modes &amp; mitigation (TABLE REQUIRED)<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>ID<\/th>\n<th>Failure mode<\/th>\n<th>Symptom<\/th>\n<th>Likely cause<\/th>\n<th>Mitigation<\/th>\n<th>Observability signal<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>F1<\/td>\n<td>Missed handoff<\/td>\n<td>Incident unacknowledged after shift<\/td>\n<td>Routing misconfiguration<\/td>\n<td>Add retry and escalation<\/td>\n<td>Alert ack time<\/td>\n<\/tr>\n<tr>\n<td>F2<\/td>\n<td>Context loss<\/td>\n<td>New team lacks incident history<\/td>\n<td>Poor handoff artifact<\/td>\n<td>Enforce structured summaries<\/td>\n<td>Number of clarifying messages<\/td>\n<\/tr>\n<tr>\n<td>F3<\/td>\n<td>Double work<\/td>\n<td>Two regions act on same incident<\/td>\n<td>No coordination locking<\/td>\n<td>Add incident locks<\/td>\n<td>Duplicate remediation events<\/td>\n<\/tr>\n<tr>\n<td>F4<\/td>\n<td>Compliance block<\/td>\n<td>Cannot execute cross-region fix<\/td>\n<td>Data residency policy<\/td>\n<td>Pre-approved cross-region processes<\/td>\n<td>Access denied logs<\/td>\n<\/tr>\n<tr>\n<td>F5<\/td>\n<td>Clock mismatch<\/td>\n<td>Alerts go to wrong region<\/td>\n<td>DST or timezone bug<\/td>\n<td>Use UTC canonical times<\/td>\n<td>Alert routing history<\/td>\n<\/tr>\n<tr>\n<td>F6<\/td>\n<td>Automation failure<\/td>\n<td>Automated remediation fails<\/td>\n<td>Outdated playbook<\/td>\n<td>Canary automation and rollbacks<\/td>\n<td>Automation error counts<\/td>\n<\/tr>\n<tr>\n<td>F7<\/td>\n<td>Escalation gap<\/td>\n<td>No one to escalate to<\/td>\n<td>Missing on-call assignment<\/td>\n<td>Backup escalation paths<\/td>\n<td>Escalation latency<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h4 class=\"wp-block-heading\">Row Details (only if needed)<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>None<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Key Concepts, Keywords &amp; Terminology for Follow the sun<\/h2>\n\n\n\n<p>Term \u2014 1\u20132 line definition \u2014 why it matters \u2014 common pitfall<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Follow the sun \u2014 Operational model handing work to local teams \u2014 Core concept \u2014 Confused with 24&#215;7 single-team.<\/li>\n<li>Handoff \u2014 Transfer of ownership between teams \u2014 Critical for continuity \u2014 Informal handoffs cause context loss.<\/li>\n<li>Escalation policy \u2014 Rules for when to move to next-level support \u2014 Prevents stalls \u2014 Overly complex policies delay action.<\/li>\n<li>Runbook \u2014 Step-by-step remediation guide \u2014 Reduces MTTR \u2014 Stale runbooks mislead responders.<\/li>\n<li>Incident orchestration \u2014 Automated routing and lifecycle management \u2014 Scales coordination \u2014 Poor routing breaks coverage.<\/li>\n<li>SLI \u2014 Service Level Indicator \u2014 Measures reliability aspects \u2014 Wrong SLI yields wrong priorities.<\/li>\n<li>SLO \u2014 Service Level Objective \u2014 Target for SLIs \u2014 Drives error budget policy \u2014 Misaligned SLOs cause churn.<\/li>\n<li>Error budget \u2014 Allowance for unreliability \u2014 Enables risk-taking \u2014 Mismanaged budgets lead to outages.<\/li>\n<li>MTTR \u2014 Mean Time To Repair \u2014 Key operational metric \u2014 Ignoring detection time skews data.<\/li>\n<li>MTTA \u2014 Mean Time To Acknowledge \u2014 Shows alert responsiveness \u2014 False positives inflate MTTA.<\/li>\n<li>Synthetic monitoring \u2014 Simulated transactions to test availability \u2014 Early detection tool \u2014 Tests may not cover real paths.<\/li>\n<li>Real-user monitoring \u2014 Observes actual user requests \u2014 Reflects true impact \u2014 Sampling can miss issues.<\/li>\n<li>Global load balancer \u2014 Routes users to regions \u2014 Facilitates traffic shifts \u2014 Misconfig leads to misrouting.<\/li>\n<li>Active-active \u2014 Multiple regions serve traffic simultaneously \u2014 Lowers latency \u2014 State synchronization is hard.<\/li>\n<li>Active-passive \u2014 One region standby \u2014 Simplifies state \u2014 Failover delay possible.<\/li>\n<li>Traffic shifting \u2014 Gradual reroute of traffic to healthy regions \u2014 Reduces blast radius \u2014 Poor metrics can hide issues.<\/li>\n<li>Replica consistency \u2014 Data sync between regions \u2014 Ensures correctness \u2014 Stale reads if lagging.<\/li>\n<li>Read replica \u2014 Read-only copy of DB \u2014 Offloads reads \u2014 Writes inconsistency risk.<\/li>\n<li>Failover \u2014 Move traffic to alternate region \u2014 Recovery method \u2014 Risk of split-brain.<\/li>\n<li>Canary deployment \u2014 Gradual rollout to subset of users \u2014 Limits impact \u2014 Small sample may hide issues.<\/li>\n<li>Blue-green deploy \u2014 Swap full environments for safety \u2014 Quick rollback \u2014 Resource expensive.<\/li>\n<li>Observability \u2014 Measurement of system behavior \u2014 Supports rapid ops \u2014 Incomplete telemetry blinds teams.<\/li>\n<li>Tracing \u2014 Request path visibility \u2014 Speeds root cause analysis \u2014 High cardinality costs.<\/li>\n<li>Logging \u2014 Event records for systems \u2014 Forensics and debug \u2014 Log noise hides signals.<\/li>\n<li>Alert fatigue \u2014 Excessive alerts reducing attention \u2014 Teams ignore alerts \u2014 Tune thresholds and dedupe.<\/li>\n<li>Runbook automation \u2014 Scripts for remediation \u2014 Reduces toil \u2014 Unsafe automation causes outages.<\/li>\n<li>ChatOps \u2014 Operations in collaborative chat \u2014 Faster coordination \u2014 Info scattering risk.<\/li>\n<li>Timezone routing \u2014 Directing alerts by TZ \u2014 Ensures local teams active \u2014 DST handling necessary.<\/li>\n<li>Handoff summary \u2014 Structured incident notes \u2014 Preserves context \u2014 Free-text leads to ambiguity.<\/li>\n<li>Ownership transfer \u2014 Formal change of responsibility \u2014 Prevents overlap \u2014 Unclear ownership causes delays.<\/li>\n<li>SLA \u2014 Service Level Agreement \u2014 Business contract level \u2014 Operationally rigid SLAs hurt agility.<\/li>\n<li>NOC \u2014 Network operations center \u2014 Centralized ops team \u2014 Can be bottleneck for local expertise.<\/li>\n<li>Multi-cloud \u2014 Use of multiple cloud providers \u2014 Increases resilience \u2014 Increases complexity.<\/li>\n<li>RBAC \u2014 Role-based access control \u2014 Security for cross-region ops \u2014 Overly strict blocks fixes.<\/li>\n<li>SIEM \u2014 Security telemetry aggregation \u2014 Local security analytics \u2014 High noise if misconfigured.<\/li>\n<li>Chaos engineering \u2014 Controlled failures to test resilience \u2014 Validates handoffs \u2014 Poorly scoped chaos breaks SLAs.<\/li>\n<li>Postmortem \u2014 Blameless incident analysis \u2014 Drives improvement \u2014 Blame culture reduces reporting.<\/li>\n<li>RCA \u2014 Root cause analysis \u2014 Identifies root fixes \u2014 Superficial RCAs repeat failures.<\/li>\n<li>Observability SLO \u2014 Targets for telemetry health \u2014 Ensures visibility \u2014 Missing metrics reduce confidence.<\/li>\n<li>Burn rate \u2014 Speed of error budget consumption \u2014 Triggers action thresholds \u2014 Miscalculated burn rate misleads ops.<\/li>\n<li>Local autonomy \u2014 Regional teams&#8217; authority to act \u2014 Speeds fixes \u2014 Too much autonomy fragments platform.<\/li>\n<li>Central governance \u2014 Global policies and standards \u2014 Ensures consistency \u2014 Heavy governance slows response.<\/li>\n<li>Cross-region playbook \u2014 Policy for cross-region fixes \u2014 Ensures compliance \u2014 Complex updates can lag.<\/li>\n<li>Incident lock \u2014 Prevents concurrent conflicting actions \u2014 Avoids double work \u2014 Locks can block progress if stuck.<\/li>\n<li>Context enrichment \u2014 Adding logs\/traces to alerts \u2014 Reduces time to debug \u2014 Large enrichment payloads slow systems.<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">How to Measure Follow the sun (Metrics, SLIs, SLOs) (TABLE REQUIRED)<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>ID<\/th>\n<th>Metric\/SLI<\/th>\n<th>What it tells you<\/th>\n<th>How to measure<\/th>\n<th>Starting target<\/th>\n<th>Gotchas<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>M1<\/td>\n<td>Regional MTTR<\/td>\n<td>Speed of fix per region<\/td>\n<td>Time from alert to resolved per region<\/td>\n<td>30-90 minutes<\/td>\n<td>Biased by detection delay<\/td>\n<\/tr>\n<tr>\n<td>M2<\/td>\n<td>MTTA by region<\/td>\n<td>Alert acknowledgement speed<\/td>\n<td>Time from alert to first ack<\/td>\n<td>5-15 minutes<\/td>\n<td>High noise inflates metric<\/td>\n<\/tr>\n<tr>\n<td>M3<\/td>\n<td>Handoff latency<\/td>\n<td>Time to transfer ownership<\/td>\n<td>Time from resolved to next owner ack<\/td>\n<td>&lt;15 minutes<\/td>\n<td>Manual handoffs vary widely<\/td>\n<\/tr>\n<tr>\n<td>M4<\/td>\n<td>Incident reopens<\/td>\n<td>Quality of resolution<\/td>\n<td>Count of reopened incidents per region<\/td>\n<td>&lt;5% incidents<\/td>\n<td>Post-incident fixes may reclassify<\/td>\n<\/tr>\n<tr>\n<td>M5<\/td>\n<td>SLI availability<\/td>\n<td>User-facing success rate<\/td>\n<td>Successful requests divided by total<\/td>\n<td>99.9% See caveats<\/td>\n<td>Varies by service criticality<\/td>\n<\/tr>\n<tr>\n<td>M6<\/td>\n<td>Automation success rate<\/td>\n<td>Remediation automation efficacy<\/td>\n<td>Successful automated runs ratio<\/td>\n<td>&gt;90% for trivial tasks<\/td>\n<td>Flaky automation hides failures<\/td>\n<\/tr>\n<tr>\n<td>M7<\/td>\n<td>Alert noise ratio<\/td>\n<td>Useful alerts vs total<\/td>\n<td>Number of actionable alerts divided by total<\/td>\n<td>&gt;25% actionable<\/td>\n<td>Poor dedupe skews ratio<\/td>\n<\/tr>\n<tr>\n<td>M8<\/td>\n<td>Escalation latency<\/td>\n<td>Time to escalate to global team<\/td>\n<td>Time from threshold to escalation<\/td>\n<td>&lt;30 minutes<\/td>\n<td>Missing on-call data delays it<\/td>\n<\/tr>\n<tr>\n<td>M9<\/td>\n<td>Cross-region fix time<\/td>\n<td>Time to complete cross-region action<\/td>\n<td>Start to end of cross-region remediation<\/td>\n<td>Varies \/ depends<\/td>\n<td>Compliance windows affect it<\/td>\n<\/tr>\n<tr>\n<td>M10<\/td>\n<td>Runbook usage<\/td>\n<td>Fraction of incidents using runbooks<\/td>\n<td>Count of incidents referencing runbook<\/td>\n<td>&gt;60%<\/td>\n<td>Runbooks may be outdated<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h4 class=\"wp-block-heading\">Row Details (only if needed)<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>M5: SLI availability starting target depends on service. Use conservative targets for critical systems and adjust by error budget.<\/li>\n<li>M9: Cross-region fix time varies by compliance and approvals; plan for long tails.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Best tools to measure Follow the sun<\/h3>\n\n\n\n<p>(Choose a concise set of industry tools representative in 2026)<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Tool \u2014 Grafana<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What it measures for Follow the sun: Dashboards for SLIs, regional MTTR and alert rates.<\/li>\n<li>Best-fit environment: Multi-cloud and Kubernetes.<\/li>\n<li>Setup outline:<\/li>\n<li>Connect observability backends.<\/li>\n<li>Create regional dashboards and panels.<\/li>\n<li>Configure alerting rules and notification policies.<\/li>\n<li>Strengths:<\/li>\n<li>Flexible visualization and alerting.<\/li>\n<li>Wide plugin ecosystem.<\/li>\n<li>Limitations:<\/li>\n<li>Alert dedupe requires careful configuration.<\/li>\n<li>No native incident orchestration.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Tool \u2014 PagerDuty<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What it measures for Follow the sun: Incident lifecycle, MTTA, escalations, and on-call scheduling.<\/li>\n<li>Best-fit environment: Enterprises needing robust on-call orchestration.<\/li>\n<li>Setup outline:<\/li>\n<li>Define escalation policies per region.<\/li>\n<li>Integrate monitoring alerts.<\/li>\n<li>Set up schedules and overrides.<\/li>\n<li>Strengths:<\/li>\n<li>Strong routing and escalation features.<\/li>\n<li>Audit trail for handoffs.<\/li>\n<li>Limitations:<\/li>\n<li>Cost scales with seats.<\/li>\n<li>Complex configs can be hard to manage.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Tool \u2014 Honeycomb<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What it measures for Follow the sun: Distributed tracing and high-cardinality observability for regional debugging.<\/li>\n<li>Best-fit environment: Microservices and event-driven systems.<\/li>\n<li>Setup outline:<\/li>\n<li>Instrument services with tracing.<\/li>\n<li>Create queries for regional impact.<\/li>\n<li>Build trace-based dashboards.<\/li>\n<li>Strengths:<\/li>\n<li>Powerful ad-hoc analysis.<\/li>\n<li>Fast trace-level debugging.<\/li>\n<li>Limitations:<\/li>\n<li>Learning curve for advanced analyses.<\/li>\n<li>Cost depends on event volume.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Tool \u2014 BigQuery (or Cloud Data Warehouse)<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What it measures for Follow the sun: Aggregated telemetry and post-incident analytics.<\/li>\n<li>Best-fit environment: Organizations aggregating logs and metrics for analytics.<\/li>\n<li>Setup outline:<\/li>\n<li>Stream telemetry to warehouse.<\/li>\n<li>Create regional partitioned tables.<\/li>\n<li>Build SLO and SLA reports.<\/li>\n<li>Strengths:<\/li>\n<li>Scalability and complex queries.<\/li>\n<li>Good for postmortem analysis.<\/li>\n<li>Limitations:<\/li>\n<li>Query cost if unoptimized.<\/li>\n<li>Not real-time for immediate alerting.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Tool \u2014 OpsGenie<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What it measures for Follow the sun: Scheduling and alert routing similar to PagerDuty.<\/li>\n<li>Best-fit environment: Teams using Atlassian toolchain.<\/li>\n<li>Setup outline:<\/li>\n<li>Configure policies and escalation chains.<\/li>\n<li>Integrate with monitoring tools.<\/li>\n<li>Set timezone-aware schedules.<\/li>\n<li>Strengths:<\/li>\n<li>Strong integrations and scheduling.<\/li>\n<li>Cost-effective for certain teams.<\/li>\n<li>Limitations:<\/li>\n<li>Less mature analytics than dedicated incident platforms.<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">Tool \u2014 ServiceNow<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What it measures for Follow the sun: Ticket and incident management with enterprise governance.<\/li>\n<li>Best-fit environment: Large enterprises requiring ITSM processes.<\/li>\n<li>Setup outline:<\/li>\n<li>Map incident workflows to regional teams.<\/li>\n<li>Automate ticket creation from alerts.<\/li>\n<li>Configure SLAs and reporting.<\/li>\n<li>Strengths:<\/li>\n<li>Process and compliance support.<\/li>\n<li>Workflow automation.<\/li>\n<li>Limitations:<\/li>\n<li>Heavyweight and slow to change.<\/li>\n<li>Integration overhead.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Recommended dashboards &amp; alerts for Follow the sun<\/h3>\n\n\n\n<p>Executive dashboard:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Global SLO health by region: quick business-level view.<\/li>\n<li>Error budget burn rate per region: show risk windows.<\/li>\n<li>Major incidents active with customer impact: executive snapshot.<\/li>\n<\/ul>\n\n\n\n<p>On-call dashboard:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Alerts by severity and region: triage view.<\/li>\n<li>Open incidents with owner and time since alert: workload triage.<\/li>\n<li>Handoff queue and pending handoffs: shows items needing transfer.<\/li>\n<\/ul>\n\n\n\n<p>Debug dashboard:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Per-service traces and error logs for affected region: root cause tools.<\/li>\n<li>Recent deploys and configuration changes timeline: link to CI\/CD.<\/li>\n<li>Resource metrics (CPU mem I\/O) and network metrics: operational context.<\/li>\n<\/ul>\n\n\n\n<p>Alerting guidance:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Page vs ticket: page for severity S1\/S2 impacting customers; ticket for S3 non-customer-facing issues.<\/li>\n<li>Burn-rate guidance: page when burn rate exceeds threshold and predicted SLO breach within business window.<\/li>\n<li>Noise reduction tactics: dedupe alerts at source, group related alerts into incidents, suppression windows for noisy maintenance, adaptive thresholds based on traffic.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Implementation Guide (Step-by-step)<\/h2>\n\n\n\n<p>1) Prerequisites\n&#8211; Global team structure with defined regional owners.\n&#8211; Observability and alerting in place across regions.\n&#8211; Runbooks and automation for common incidents.\n&#8211; Timezone-aware scheduling and on-call tools.<\/p>\n\n\n\n<p>2) Instrumentation plan\n&#8211; Define SLIs for regional availability and latency.\n&#8211; Instrument traces, logs, and metrics with region metadata.\n&#8211; Ensure synthetic checks per region and critical path.<\/p>\n\n\n\n<p>3) Data collection\n&#8211; Centralized telemetry store with region tags.\n&#8211; Local dashboards for shift teams and global view for managers.\n&#8211; Export events for post-incident analytics.<\/p>\n\n\n\n<p>4) SLO design\n&#8211; Set regional SLOs reflecting local traffic and business impact.\n&#8211; Define shared global SLOs for cross-region features.\n&#8211; Error budgets per region and a policy for cross-region borrowing.<\/p>\n\n\n\n<p>5) Dashboards\n&#8211; Build executive, on-call, and debug dashboards.\n&#8211; Provide per-service and per-region drilldowns.\n&#8211; Include deployment and changelog panels.<\/p>\n\n\n\n<p>6) Alerts &amp; routing\n&#8211; Create region-aware alerting rules.\n&#8211; Configure on-call schedules by local business hours.\n&#8211; Implement escalation policies and automatic retries.<\/p>\n\n\n\n<p>7) Runbooks &amp; automation\n&#8211; Author structured runbooks with automated steps where safe.\n&#8211; Implement Playbooks that include telemetry links.\n&#8211; Automate common fixes with safe rollback options.<\/p>\n\n\n\n<p>8) Validation (load\/chaos\/game days)\n&#8211; Run chaos tests targeting handoffs and cross-region failovers.\n&#8211; Game days simulating multi-region incidents and evening handoffs.\n&#8211; Validate automation in staging before production.<\/p>\n\n\n\n<p>9) Continuous improvement\n&#8211; Postmortems after each significant incident with action items.\n&#8211; Track runbook usage and update stale entries.\n&#8211; Adjust SLOs and routing based on measured outcomes.<\/p>\n\n\n\n<p>Include checklists:<\/p>\n\n\n\n<p>Pre-production checklist<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Region tagging across telemetry implemented.<\/li>\n<li>On-call schedules and escalation set up.<\/li>\n<li>Runbooks for top 10 incident types authored.<\/li>\n<li>Synthetic checks for critical paths in place.<\/li>\n<li>Cross-region access and compliance validation completed.<\/li>\n<\/ul>\n\n\n\n<p>Production readiness checklist<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Dashboard panels validated and shared with teams.<\/li>\n<li>Alert suppression for planned maintenance configured.<\/li>\n<li>Automation tested in staging and canaryed in production.<\/li>\n<li>Backup escalation exists for holiday coverage.<\/li>\n<\/ul>\n\n\n\n<p>Incident checklist specific to Follow the sun<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Acknowledge incident and assign local owner.<\/li>\n<li>Capture structured context for handoff.<\/li>\n<li>Attempt remediation per runbook and log steps.<\/li>\n<li>Escalate on time if thresholds exceeded.<\/li>\n<li>Produce automated post-incident summary and schedule RCA.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Use Cases of Follow the sun<\/h2>\n\n\n\n<p>Provide 8\u201312 use cases:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>\n<p>Global SaaS customer support\n&#8211; Context: SaaS with customers in APAC, EMEA, Americas.\n&#8211; Problem: Support response time lags outside a primary timezone.\n&#8211; Why Follow the sun helps: Local teams handle region-specific issues faster.\n&#8211; What to measure: Ticket TTR, regional CSAT, MTTR.\n&#8211; Typical tools: Ticketing system, PagerDuty, observability.<\/p>\n<\/li>\n<li>\n<p>E-commerce peak season operations\n&#8211; Context: Retail spikes in multiple countries during promotions.\n&#8211; Problem: Incidents during local peaks cause lost revenue.\n&#8211; Why Follow the sun helps: Immediate regional response during local peaks.\n&#8211; What to measure: Checkout error rate per region, revenue loss per minute.\n&#8211; Typical tools: APM, global LB, automation for failover.<\/p>\n<\/li>\n<li>\n<p>Financial services compliance incidents\n&#8211; Context: Regulatory events needing local handling.\n&#8211; Problem: Cross-region access restricted; centralized teams slow.\n&#8211; Why Follow the sun helps: Local teams with compliance knowledge act immediately.\n&#8211; What to measure: Time to remediate compliance incidents, audit trail completeness.\n&#8211; Typical tools: SIEM, ServiceNow, RBAC.<\/p>\n<\/li>\n<li>\n<p>Multi-region Kubernetes clusters\n&#8211; Context: Microservices deployed to clusters across regions.\n&#8211; Problem: Regional cluster failures affecting local customers.\n&#8211; Why Follow the sun helps: K8s SREs in-region manage clusters during their day.\n&#8211; What to measure: Pod restart rate, node failures, MTTR per cluster.\n&#8211; Typical tools: Prometheus, Grafana, kube-state-metrics.<\/p>\n<\/li>\n<li>\n<p>CDN and edge incidents\n&#8211; Context: Edge cache poisoning or regional CDN outages.\n&#8211; Problem: Traffic spike or configuration errors local to edges.\n&#8211; Why Follow the sun helps: Local teams aware of regional traffic patterns intervene.\n&#8211; What to measure: Cache hit ratio, edge latency, error rates.\n&#8211; Typical tools: CDN analytics, global LB, observability.<\/p>\n<\/li>\n<li>\n<p>Serverless function regressions\n&#8211; Context: Functions deployed globally as managed PaaS.\n&#8211; Problem: Runtime or third-party API regressions impacting region.\n&#8211; Why Follow the sun helps: Adjust region-specific config or rollback quickly.\n&#8211; What to measure: Invocation failure rate, cold start times.\n&#8211; Typical tools: Cloud function metrics, deployment pipelines.<\/p>\n<\/li>\n<li>\n<p>Data replication lag incidents\n&#8211; Context: Multi-region databases with read replicas.\n&#8211; Problem: Stale reads or consistency issues.\n&#8211; Why Follow the sun helps: Local DB teams troubleshoot replication during local hours.\n&#8211; What to measure: Replication lag, failed transactions.\n&#8211; Typical tools: DB monitoring, observability.<\/p>\n<\/li>\n<li>\n<p>Security event triage\n&#8211; Context: Suspicious activity detected regionally.\n&#8211; Problem: Immediate local law and privacy needs require quick local action.\n&#8211; Why Follow the sun helps: Security analysts can triage and contain faster locally.\n&#8211; What to measure: Time to containment, number of false positives.\n&#8211; Typical tools: SIEM, endpoint detection, SOC playbooks.<\/p>\n<\/li>\n<li>\n<p>Incident-driven feature rollbacks\n&#8211; Context: New features causing regional regressions.\n&#8211; Problem: Need fast rollbacks in specific regions.\n&#8211; Why Follow the sun helps: Regional teams can rollback while other regions stay unaffected.\n&#8211; What to measure: Rollback time, rollback success rate.\n&#8211; Typical tools: CI\/CD, feature flags.<\/p>\n<\/li>\n<li>\n<p>Customer escalations for SLAs\n&#8211; Context: Enterprise customers require quick remediation.\n&#8211; Problem: Local SLAs require response within business hours.\n&#8211; Why Follow the sun helps: Locally routed responses meet contractual obligations.\n&#8211; What to measure: SLA compliance, response time.\n&#8211; Typical tools: Ticketing, monitoring, reporting.<\/p>\n<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Scenario Examples (Realistic, End-to-End)<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Scenario #1 \u2014 Kubernetes cluster regional outage<\/h3>\n\n\n\n<p><strong>Context:<\/strong> A regional Kubernetes cluster reports node controller failures during local business hours.<br\/>\n<strong>Goal:<\/strong> Restore cluster function and return services to normal within regional SLO.<br\/>\n<strong>Why Follow the sun matters here:<\/strong> On-site regional SREs can access provider support and execute region-specific remediation during local workday.<br\/>\n<strong>Architecture \/ workflow:<\/strong> Regional cluster with regional monitoring, central observability, and CI\/CD pipelines supporting the cluster.<br\/>\n<strong>Step-by-step implementation:<\/strong> <\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Alert triggers regional on-call via PagerDuty. <\/li>\n<li>On-call acknowledges and opens incident in tracking tool. <\/li>\n<li>Runbook executed: check node autoscaling, drain faulty nodes, restart controller pods. <\/li>\n<li>If controllers fail, escalate to global K8s team. <\/li>\n<li>After fix, update dashboards and generate post-incident summary.<br\/>\n<strong>What to measure:<\/strong> Regional MTTR, pod restart rates, controller crash loops.<br\/>\n<strong>Tools to use and why:<\/strong> Prometheus\/Grafana for metrics, PagerDuty for routing, kubectl and cloud provider console for remediation.<br\/>\n<strong>Common pitfalls:<\/strong> Using stale runbooks; lack of provider permissions.<br\/>\n<strong>Validation:<\/strong> Chaos test simulating controller failures and validating handoff.<br\/>\n<strong>Outcome:<\/strong> Local team recovers cluster within SLO and documents a missed provider quota check.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Scenario #2 \u2014 Serverless function third-party API outage (Serverless\/PaaS)<\/h3>\n\n\n\n<p><strong>Context:<\/strong> A third-party payments API degrades in EMEA during a promotional campaign.<br\/>\n<strong>Goal:<\/strong> Maintain checkout success while minimizing revenue impact.<br\/>\n<strong>Why Follow the sun matters here:<\/strong> EMEA team can immediately enable fallback payment path and coordinate with finance during local hours.<br\/>\n<strong>Architecture \/ workflow:<\/strong> Global serverless functions with region-specific configs and feature flags for fallback flows.<br\/>\n<strong>Step-by-step implementation:<\/strong> <\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Synthetic checks detect increased payment failures in EMEA. <\/li>\n<li>Alert routes to EMEA on-call. <\/li>\n<li>EMEA team flips feature flag to fallback payment provider and monitors success. <\/li>\n<li>Global team investigates third-party SLA and coordinates remediation. <\/li>\n<li>Post-incident: adjust retry logic and add synthetic checks.<br\/>\n<strong>What to measure:<\/strong> Payment success rate per region, rollback time.<br\/>\n<strong>Tools to use and why:<\/strong> Cloud function metrics, feature flag platform, synthetic monitoring.<br\/>\n<strong>Common pitfalls:<\/strong> Missing fallback credentials in region.<br\/>\n<strong>Validation:<\/strong> Load test fallback path and run localized chaos.<br\/>\n<strong>Outcome:<\/strong> Fallback reduces revenue loss and identifies missing credentials to fix.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Scenario #3 \u2014 Multi-region incident response and postmortem<\/h3>\n\n\n\n<p><strong>Context:<\/strong> A cascading deploy failure results in partial outages across regions during handoff intervals.<br\/>\n<strong>Goal:<\/strong> Resolve outages and root cause analysis without finger-pointing.<br\/>\n<strong>Why Follow the sun matters here:<\/strong> Incidents spanned multiple shifts; smooth handoffs and centralized RCA required.<br\/>\n<strong>Architecture \/ workflow:<\/strong> Global orchestration service with regional deployments and centralized logging.<br\/>\n<strong>Step-by-step implementation:<\/strong> <\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Incident raised and routed to region where failure started. <\/li>\n<li>Regional team mitigates; global team coordinates cross-region rollback. <\/li>\n<li>Handoff summaries produced at shift changes. <\/li>\n<li>Postmortem scheduled with representatives from all regions. <\/li>\n<li>Action items assigned and tracked across regional teams.<br\/>\n<strong>What to measure:<\/strong> Handoff latency, action item completion rate, cross-region MTTR.<br\/>\n<strong>Tools to use and why:<\/strong> Incident platform, centralized logging, collaboration tools.<br\/>\n<strong>Common pitfalls:<\/strong> Incomplete handoff notes leading to wasted time.<br\/>\n<strong>Validation:<\/strong> Tabletop exercises simulating shift overlaps.<br\/>\n<strong>Outcome:<\/strong> RCA identifies integration test gap and updated CI gates implemented.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\">Scenario #4 \u2014 Cost\/performance trade-off (Cost\/Perf)<\/h3>\n\n\n\n<p><strong>Context:<\/strong> Traffic spikes cause autoscaling to spin up cross-region capacity, increasing cost alerts during off-peak in some regions.<br\/>\n<strong>Goal:<\/strong> Balance latency needs and cost constraints while maintaining SLOs.<br\/>\n<strong>Why Follow the sun matters here:<\/strong> Regional teams can tune autoscaling and capacity locally during their hours.<br\/>\n<strong>Architecture \/ workflow:<\/strong> Service deployed in multiple regions with autoscaling policies and central billing alerts.<br\/>\n<strong>Step-by-step implementation:<\/strong> <\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Cost alert triggers regional operations and finance. <\/li>\n<li>Regional team examines load and scales down non-critical components after business-hours windows. <\/li>\n<li>Implement scheduled scaling policies per region aligned to local traffic patterns. <\/li>\n<li>Monitor SLOs to ensure no user impact.<br\/>\n<strong>What to measure:<\/strong> Cost per region, tail latency, scaling events.<br\/>\n<strong>Tools to use and why:<\/strong> Cloud billing dashboards, APM, autoscaler metrics.<br\/>\n<strong>Common pitfalls:<\/strong> Aggressive scaling down causing latency spikes.<br\/>\n<strong>Validation:<\/strong> Simulate traffic and scaling behaviors with load tests.<br\/>\n<strong>Outcome:<\/strong> Cost optimized while maintaining SLOs with scheduled scaling rules.<\/li>\n<\/ol>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Common Mistakes, Anti-patterns, and Troubleshooting<\/h2>\n\n\n\n<p>List 15\u201325 mistakes with Symptom -&gt; Root cause -&gt; Fix (include at least 5 observability pitfalls).<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Symptom: Alerts unacknowledged overnight -&gt; Root cause: No backup escalation -&gt; Fix: Add secondary regional escalation.<\/li>\n<li>Symptom: Repeated incident reopenings -&gt; Root cause: Superficial fixes -&gt; Fix: Enforce thorough root cause checks before close.<\/li>\n<li>Symptom: Conflicting actions from two regions -&gt; Root cause: No incident lock -&gt; Fix: Implement incident locking in orchestration.<\/li>\n<li>Symptom: High MTTA -&gt; Root cause: Alert noise -&gt; Fix: Triage and dedupe alerts; tune thresholds.<\/li>\n<li>Symptom: Missing context on handoff -&gt; Root cause: Free-text handoffs -&gt; Fix: Structured handoff templates and automated enrichment.<\/li>\n<li>Symptom: Automation-induced outages -&gt; Root cause: Unchecked automated playbooks -&gt; Fix: Canary automation and kill switches.<\/li>\n<li>Symptom: Runbooks ignored -&gt; Root cause: Outdated or hard-to-follow runbooks -&gt; Fix: Regular runbook reviews and drills.<\/li>\n<li>Symptom: Inconsistent SLOs across regions -&gt; Root cause: No governance -&gt; Fix: Central SLO policy with regional adjustments.<\/li>\n<li>Symptom: Observability blind spots -&gt; Root cause: Missing telemetry tags for region -&gt; Fix: Add region tags to all telemetry.<\/li>\n<li>Symptom: Logs missing for incidents -&gt; Root cause: Sampling or retention config -&gt; Fix: Adjust sampling for incident windows and retention policies.<\/li>\n<li>Symptom: Traces incomplete -&gt; Root cause: Instrumentation gaps -&gt; Fix: Standardize tracing libraries and injection.<\/li>\n<li>Symptom: Dashboard overload -&gt; Root cause: Many unfocused panels -&gt; Fix: Curate dashboards per role and purpose.<\/li>\n<li>Symptom: Cost spikes unexpectedly -&gt; Root cause: Uncontrolled autoscaling across regions -&gt; Fix: Scheduled scaling and budget alerts.<\/li>\n<li>Symptom: Escalation delays -&gt; Root cause: No covered on-call shifts during holidays -&gt; Fix: Holiday overrides and backups.<\/li>\n<li>Symptom: Compliance block stalls fixes -&gt; Root cause: No pre-approved cross-region processes -&gt; Fix: Define compliant cross-region playbooks.<\/li>\n<li>Symptom: Low runbook usage -&gt; Root cause: Hard to find runbooks -&gt; Fix: Surface runbooks directly in alert payloads.<\/li>\n<li>Symptom: Duplicate incidents -&gt; Root cause: Multiple monitoring sources alert separately -&gt; Fix: Correlate and consolidate alerts upstream.<\/li>\n<li>Symptom: Poor cross-region communication -&gt; Root cause: No overlap period for handoffs -&gt; Fix: Create short overlap windows during shift changes.<\/li>\n<li>Symptom: High alarm fatigue -&gt; Root cause: Low-value alerts -&gt; Fix: Convert low-value alerts to tickets and reduce pages.<\/li>\n<li>Symptom: Security incidents mishandled -&gt; Root cause: Lack of region-aware SOC playbooks -&gt; Fix: Local SOC playbooks and periodic training.<\/li>\n<li>Symptom: Delayed postmortems -&gt; Root cause: Busy regional teams -&gt; Fix: Enforce timelines and lightweight templates.<\/li>\n<li>Symptom: Missing root cause data -&gt; Root cause: Telemetry not retained long enough -&gt; Fix: Extend retention for incident windows.<\/li>\n<li>Symptom: Inadequate validation -&gt; Root cause: No game days -&gt; Fix: Regular game days across regions.<\/li>\n<li>Symptom: Handoff summaries inconsistent -&gt; Root cause: No enforced template -&gt; Fix: Structured fields and automated summary generation.<\/li>\n<li>Symptom: Observability cost explosion -&gt; Root cause: High-cardinality metrics unchecked -&gt; Fix: Instrumentation review and sampling strategies.<\/li>\n<\/ol>\n\n\n\n<p>Observability-specific pitfalls noted above include missing telemetry tags, logs missing, traces incomplete, dashboard overload, and telemetry cost spikes.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Best Practices &amp; Operating Model<\/h2>\n\n\n\n<p>Ownership and on-call:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Prefer regional ownership with a clear global escalation path.<\/li>\n<li>Keep on-call rotas predictable and aligned with local business hours.<\/li>\n<li>Provide compensation and downtime for on-call duties.<\/li>\n<\/ul>\n\n\n\n<p>Runbooks vs playbooks:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Runbooks: step-by-step for specific failures; keep brief and tested.<\/li>\n<li>Playbooks: higher-level decision trees for complex issues; include escalation and communication steps.<\/li>\n<\/ul>\n\n\n\n<p>Safe deployments (canary\/rollback):<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use canaries and automated rollbacks tied to SLO violations.<\/li>\n<li>Automate gradual rollouts and incorporate regional gating.<\/li>\n<\/ul>\n\n\n\n<p>Toil reduction and automation:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Automate repetitive handoffs and incident enrichment.<\/li>\n<li>Use ChatOps to reduce context switching.<\/li>\n<\/ul>\n\n\n\n<p>Security basics:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Least privilege for cross-region operations.<\/li>\n<li>Audit trails for cross-region actions.<\/li>\n<li>Pre-approved secure delegation for emergency actions.<\/li>\n<\/ul>\n\n\n\n<p>Weekly\/monthly routines:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Weekly: Review high-severity incidents and outstanding action items.<\/li>\n<li>Monthly: Review SLOs and error budgets; runbook refresh.<\/li>\n<li>Quarterly: Game days and cross-region drills.<\/li>\n<\/ul>\n\n\n\n<p>What to review in postmortems related to Follow the sun:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Handoff quality and timing metrics.<\/li>\n<li>Automation success\/failure rates.<\/li>\n<li>Error budget impacts per region.<\/li>\n<li>Action item closure and effectiveness.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Tooling &amp; Integration Map for Follow the sun (TABLE REQUIRED)<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table>\n<thead>\n<tr>\n<th>ID<\/th>\n<th>Category<\/th>\n<th>What it does<\/th>\n<th>Key integrations<\/th>\n<th>Notes<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>I1<\/td>\n<td>Monitoring<\/td>\n<td>Detects incidents and metrics<\/td>\n<td>Alerting APM tracing logs<\/td>\n<td>Region tagging required<\/td>\n<\/tr>\n<tr>\n<td>I2<\/td>\n<td>Incident platform<\/td>\n<td>Orchestrates incidents and handoffs<\/td>\n<td>PagerDuty ticketing chat<\/td>\n<td>Use timezone schedules<\/td>\n<\/tr>\n<tr>\n<td>I3<\/td>\n<td>Observability<\/td>\n<td>Traces logs and metrics<\/td>\n<td>Dashboards APM<\/td>\n<td>High-cardinality support helpful<\/td>\n<\/tr>\n<tr>\n<td>I4<\/td>\n<td>CI\/CD<\/td>\n<td>Deploy and rollback code<\/td>\n<td>Artifact registry monitoring<\/td>\n<td>Support regional pipelines<\/td>\n<\/tr>\n<tr>\n<td>I5<\/td>\n<td>Feature flags<\/td>\n<td>Toggle region behavior<\/td>\n<td>CI\/CD runtime<\/td>\n<td>Include emergency toggles<\/td>\n<\/tr>\n<tr>\n<td>I6<\/td>\n<td>Runbook store<\/td>\n<td>Host runbooks and playbooks<\/td>\n<td>Incident platform chat<\/td>\n<td>Versioned and searchable<\/td>\n<\/tr>\n<tr>\n<td>I7<\/td>\n<td>Automation engine<\/td>\n<td>Execute scripted remediations<\/td>\n<td>Cloud APIs monitoring<\/td>\n<td>Provide kill switches<\/td>\n<\/tr>\n<tr>\n<td>I8<\/td>\n<td>Ticketing\/ITSM<\/td>\n<td>Manage incident tickets<\/td>\n<td>Incident platform reporting<\/td>\n<td>Useful for postmortems<\/td>\n<\/tr>\n<tr>\n<td>I9<\/td>\n<td>Security tools<\/td>\n<td>SOC and SIEM functions<\/td>\n<td>Logs alerting IAM<\/td>\n<td>Region-aware rules needed<\/td>\n<\/tr>\n<tr>\n<td>I10<\/td>\n<td>Billing analytics<\/td>\n<td>Cost telemetry and alerts<\/td>\n<td>Cloud provider APIs<\/td>\n<td>Tie to regional cost centers<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/figure>\n\n\n\n<h4 class=\"wp-block-heading\">Row Details (only if needed)<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>None<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently Asked Questions (FAQs)<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What exactly is Follow the sun?<\/h3>\n\n\n\n<p>Follow the sun is a coordinated operational model routing work to teams in their local business hours to maintain continuous coverage while minimizing burnout.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is Follow the sun the same as 24&#215;7 on-call?<\/h3>\n\n\n\n<p>No. 24&#215;7 on-call is a single-team continuous duty model; Follow the sun distributes ownership across regions during local hours.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do you prevent knowledge loss during handoffs?<\/h3>\n\n\n\n<p>Use structured handoff templates, automated enrichment (logs traces links), and short overlap windows for verbal sync when needed.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can automation replace human handoffs?<\/h3>\n\n\n\n<p>Automation can handle repetitive tasks and context transfer but humans remain essential for complex judgement decisions.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do you measure success of a Follow the sun implementation?<\/h3>\n\n\n\n<p>Measure regional MTTR MTTA SLO attainment error budget burn and quality of handoffs using incident metrics and postmortems.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What are the biggest risks?<\/h3>\n\n\n\n<p>Context loss, automation errors, compliance blocks, and escalation gaps are top risks.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do you handle DST and timezone changes?<\/h3>\n\n\n\n<p>Use UTC canonical times internally and timezone-aware scheduling that accounts for DST transitions.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Do you need identical stacks in all regions?<\/h3>\n\n\n\n<p>Not necessarily. Similar operational patterns are required but full stack parity depends on latency, compliance, and cost trade-offs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do you manage sensitive data across regions?<\/h3>\n\n\n\n<p>Follow compliance and data residency rules; use pre-approved cross-region playbooks or local-only remediation where required.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What handoff artifacts are essential?<\/h3>\n\n\n\n<p>Structured summary, recent logs, traces, recent deploy changelog, and active remediation steps are essential.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do you avoid alert fatigue?<\/h3>\n\n\n\n<p>Tune thresholds, dedupe correlated alerts, convert low-priority alerts to tickets, and maintain suppression for noisy maintenance.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Should SLOs be global or regional?<\/h3>\n\n\n\n<p>Both. Regional SLOs reflect local user impact; global SLOs capture system-wide reliability expectations.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How often should runbooks be tested?<\/h3>\n\n\n\n<p>At least quarterly, and after any major platform change; game days validate effectiveness.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What tooling is mandatory?<\/h3>\n\n\n\n<p>No single mandatory tool; however, you need monitoring, an incident platform, observability, and scheduling\/escallation tooling.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How to handle holidays and small regional teams?<\/h3>\n\n\n\n<p>Use backup escalation, on-call swaps, or temporary cross-region coverage agreements.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do you keep postmortems timely across regions?<\/h3>\n\n\n\n<p>Enforce timelines with lightweight templates and schedule cross-region meetings in overlapping hours when possible.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What&#8217;s the role of AI in Follow the sun?<\/h3>\n\n\n\n<p>AI can auto-summarize incidents, suggest remediation steps, and predict error budget burn; oversight and verification still required.<\/p>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Conclusion<\/h2>\n\n\n\n<p>Follow the sun is a mature operational approach combining people, process, and automation to provide continuous, region-aware service coverage. It reduces latency to resolution, aligns response with customer locales, and distributes operational burden when done with clear governance, tooling, and measurement.<\/p>\n\n\n\n<p>Next 7 days plan (5 bullets):<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Day 1: Audit telemetry for region tags and onboard missing metadata.<\/li>\n<li>Day 2: Define regional SLOs and error budget policy draft.<\/li>\n<li>Day 3: Create structured handoff template and embed in alerts.<\/li>\n<li>Day 4: Configure timezone-aware on-call schedules and escalation paths.<\/li>\n<li>Day 5: Run a short tabletop handoff exercise and note gaps.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Appendix \u2014 Follow the sun Keyword Cluster (SEO)<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Primary keywords<\/li>\n<li>Follow the sun<\/li>\n<li>follow the sun model<\/li>\n<li>follow the sun SRE<\/li>\n<li>follow the sun operations<\/li>\n<li>\n<p>follow the sun staffing<\/p>\n<\/li>\n<li>\n<p>Secondary keywords<\/p>\n<\/li>\n<li>regional on-call<\/li>\n<li>global incident routing<\/li>\n<li>time zone handoff<\/li>\n<li>incident orchestration<\/li>\n<li>regional SLOs<\/li>\n<li>handoff automation<\/li>\n<li>follow the sun architecture<\/li>\n<li>cross-region escalation<\/li>\n<li>timezone-aware scheduling<\/li>\n<li>\n<p>runbook automation<\/p>\n<\/li>\n<li>\n<p>Long-tail questions<\/p>\n<\/li>\n<li>What is follow the sun in SRE<\/li>\n<li>How to implement follow the sun in Kubernetes<\/li>\n<li>Follow the sun vs 24&#215;7 on-call pros and cons<\/li>\n<li>How to measure follow the sun success metrics<\/li>\n<li>Best practices for handoffs in follow the sun<\/li>\n<li>How to automate handoffs between regions<\/li>\n<li>How to prevent context loss during follow the sun handoffs<\/li>\n<li>How to design SLOs for follow the sun operations<\/li>\n<li>How to run a game day for follow the sun<\/li>\n<li>What tools support follow the sun incident routing<\/li>\n<li>How to handle DST with follow the sun schedules<\/li>\n<li>How to secure cross-region remediation<\/li>\n<li>What observability signals are critical for follow the sun<\/li>\n<li>How to set escalation policies for follow the sun<\/li>\n<li>\n<p>How to balance cost and performance with follow the sun<\/p>\n<\/li>\n<li>\n<p>Related terminology<\/p>\n<\/li>\n<li>regional ownership<\/li>\n<li>on-call schedule<\/li>\n<li>incident lock<\/li>\n<li>automation engine<\/li>\n<li>chaos engineering<\/li>\n<li>synthetic monitoring<\/li>\n<li>real-user monitoring<\/li>\n<li>global load balancer<\/li>\n<li>active-active deployment<\/li>\n<li>blue-green deployment<\/li>\n<li>canary deployment<\/li>\n<li>synthetic checks<\/li>\n<li>error budget<\/li>\n<li>MTTR metrics<\/li>\n<li>MTTA metrics<\/li>\n<li>runbook store<\/li>\n<li>playbook<\/li>\n<li>observability SLO<\/li>\n<li>SIEM regional rules<\/li>\n<li>RBAC cross-region<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>&#8212;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[149],"tags":[],"class_list":["post-1671","post","type-post","status-publish","format-standard","hentry","category-terminology"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.5 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>What is Follow the sun? Meaning, Architecture, Examples, Use Cases, and How to Measure It (2026 Guide) - SRE School<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/sreschool.com\/blog\/follow-the-sun\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"What is Follow the sun? Meaning, Architecture, Examples, Use Cases, and How to Measure It (2026 Guide) - SRE School\" \/>\n<meta property=\"og:description\" content=\"---\" \/>\n<meta property=\"og:url\" content=\"https:\/\/sreschool.com\/blog\/follow-the-sun\/\" \/>\n<meta property=\"og:site_name\" content=\"SRE School\" \/>\n<meta property=\"article:published_time\" content=\"2026-02-15T05:27:30+00:00\" \/>\n<meta name=\"author\" content=\"Rajesh Kumar\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Rajesh Kumar\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"29 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/sreschool.com\/blog\/follow-the-sun\/\",\"url\":\"https:\/\/sreschool.com\/blog\/follow-the-sun\/\",\"name\":\"What is Follow the sun? Meaning, Architecture, Examples, Use Cases, and How to Measure It (2026 Guide) - SRE School\",\"isPartOf\":{\"@id\":\"https:\/\/sreschool.com\/blog\/#website\"},\"datePublished\":\"2026-02-15T05:27:30+00:00\",\"author\":{\"@id\":\"https:\/\/sreschool.com\/blog\/#\/schema\/person\/0ffe446f77bb2589992dbe3a7f417201\"},\"breadcrumb\":{\"@id\":\"https:\/\/sreschool.com\/blog\/follow-the-sun\/#breadcrumb\"},\"inLanguage\":\"en\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/sreschool.com\/blog\/follow-the-sun\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/sreschool.com\/blog\/follow-the-sun\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/sreschool.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"What is Follow the sun? Meaning, Architecture, Examples, Use Cases, and How to Measure It (2026 Guide)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/sreschool.com\/blog\/#website\",\"url\":\"https:\/\/sreschool.com\/blog\/\",\"name\":\"SRESchool\",\"description\":\"Master SRE. Build Resilient Systems. Lead the Future of Reliability\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/sreschool.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/sreschool.com\/blog\/#\/schema\/person\/0ffe446f77bb2589992dbe3a7f417201\",\"name\":\"Rajesh Kumar\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en\",\"@id\":\"https:\/\/sreschool.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/f901a4f2929fa034a291a8363d589791d5a3c1f6a051c22e744acb8bfc8e022a?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/f901a4f2929fa034a291a8363d589791d5a3c1f6a051c22e744acb8bfc8e022a?s=96&d=mm&r=g\",\"caption\":\"Rajesh Kumar\"},\"sameAs\":[\"http:\/\/sreschool.com\/blog\"],\"url\":\"https:\/\/sreschool.com\/blog\/author\/admin\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"What is Follow the sun? Meaning, Architecture, Examples, Use Cases, and How to Measure It (2026 Guide) - SRE School","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/sreschool.com\/blog\/follow-the-sun\/","og_locale":"en_US","og_type":"article","og_title":"What is Follow the sun? Meaning, Architecture, Examples, Use Cases, and How to Measure It (2026 Guide) - SRE School","og_description":"---","og_url":"https:\/\/sreschool.com\/blog\/follow-the-sun\/","og_site_name":"SRE School","article_published_time":"2026-02-15T05:27:30+00:00","author":"Rajesh Kumar","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Rajesh Kumar","Est. reading time":"29 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/sreschool.com\/blog\/follow-the-sun\/","url":"https:\/\/sreschool.com\/blog\/follow-the-sun\/","name":"What is Follow the sun? Meaning, Architecture, Examples, Use Cases, and How to Measure It (2026 Guide) - SRE School","isPartOf":{"@id":"https:\/\/sreschool.com\/blog\/#website"},"datePublished":"2026-02-15T05:27:30+00:00","author":{"@id":"https:\/\/sreschool.com\/blog\/#\/schema\/person\/0ffe446f77bb2589992dbe3a7f417201"},"breadcrumb":{"@id":"https:\/\/sreschool.com\/blog\/follow-the-sun\/#breadcrumb"},"inLanguage":"en","potentialAction":[{"@type":"ReadAction","target":["https:\/\/sreschool.com\/blog\/follow-the-sun\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/sreschool.com\/blog\/follow-the-sun\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/sreschool.com\/blog\/"},{"@type":"ListItem","position":2,"name":"What is Follow the sun? Meaning, Architecture, Examples, Use Cases, and How to Measure It (2026 Guide)"}]},{"@type":"WebSite","@id":"https:\/\/sreschool.com\/blog\/#website","url":"https:\/\/sreschool.com\/blog\/","name":"SRESchool","description":"Master SRE. Build Resilient Systems. Lead the Future of Reliability","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/sreschool.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en"},{"@type":"Person","@id":"https:\/\/sreschool.com\/blog\/#\/schema\/person\/0ffe446f77bb2589992dbe3a7f417201","name":"Rajesh Kumar","image":{"@type":"ImageObject","inLanguage":"en","@id":"https:\/\/sreschool.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/f901a4f2929fa034a291a8363d589791d5a3c1f6a051c22e744acb8bfc8e022a?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f901a4f2929fa034a291a8363d589791d5a3c1f6a051c22e744acb8bfc8e022a?s=96&d=mm&r=g","caption":"Rajesh Kumar"},"sameAs":["http:\/\/sreschool.com\/blog"],"url":"https:\/\/sreschool.com\/blog\/author\/admin\/"}]}},"_links":{"self":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/1671","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/comments?post=1671"}],"version-history":[{"count":0,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/posts\/1671\/revisions"}],"wp:attachment":[{"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/media?parent=1671"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/categories?post=1671"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sreschool.com\/blog\/wp-json\/wp\/v2\/tags?post=1671"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}