Platform Report — Q3 2026

This whole page is one Markdown file. The prose is CommonMark, and every figure in it is a Comark component block that resolves to a markdown-graphs React component at render time. No MDX, no compile step: the file is read and parsed on each request, so the same code path would serve Markdown arriving from a database or a model.

[ Quarter at a glance ]

99.98%
Availability
SLO 99.95%
128ms
p95 response
-14% vs Q2
41.2M
Requests
peak 890 rps
312
Deploys
3.4 per weekday

Traffic

Requests grew through the quarter without a matching rise in latency. The September step comes from the search rollout described further down.

[ Requests per week (millions) ]

4.30

4.3

JulOct

Latency held flat while volume rose by two thirds. The p95 line is the one we report against; p99 stayed inside budget but is noisier.

[ p95 server response ]

128 ms

14-week trend

budget 200 ms, never breached

Where the time goes

Latency by region and hour of day, in UTC. Ap-southeast is the one region without a local read replica, and it shows.

[ p95 by region and hour (UTC) ]

000204060810121416182022

us-east-1
us-west-2
eu-west-1
ap-southeast-1

Darker is slower. Scale is relative to the worst cell.

LessMore

Delivery

Twelve of thirteen weeks were fully green. The 12 August window was a degraded config push, caught by canary and rolled back in nine minutes.

[ Daily status, last 13 weeks ]

98%

Jul 1Sep 30

█ up▒ slow· down

Bundle sizes are the one budget we came close to breaking. /search is over its allowance and is the first thing on next quarter's list.

[ Route bundles against budget ]

Route	First load	Budget	Headroom

/	94 kB	110 kB	+16 kB
/docs	121 kB	140 kB	+19 kB
/dashboard	168 kB	180 kB	+12 kB
/search	204 kB	180 kB	-24 kB

4 routes	587 kB	610 kB	+23 kB

[ Test coverage ]

86%

86% of statements, up from 79%

The search rollout

Search shipped behind a flag on 2 August and reached everyone on 14 September. The request path picked up two hops, which is where the September latency step in the traffic chart comes from.

[ Request path after the rollout ]

client

edge cache

router

search api

index shard

router

app server

postgres

[ Rollout ]

Aug 2Flag on for staff
Aug 195% of traffic
Sep 350%, replicas added
Sep 14Full rollout
Oct 6Remove the flag
Oct 20Retire the old path

Adoption ran roughly a third of sessions, and converted better than browse.

[ Search sessions to result click ]

Sessions412k
Opened search142k34%
Typed a query120k29%
Saw results118k29%
Clicked a result88k21%

Next quarter

[ Committed work ]

Split /search bundle
ap-southeast replica
Retire legacy path
Config canary v2
Cost review

OctNovDec

[ Exit criteria ]

SLO holds at 99.95%
p95 under 200 ms128 ms
Every route inside budget/search over by 24 kB
Legacy search path removedblocked on the flag
Runbook reviewed

Every figure above is a ::graph-* block in content/report.md. Switch to the source view to read the block that produced any of them, or see the catalog for the rest of the components.

1---2title: Platform Report3period: Q3 20264author: Platform Infrastructure5summary: Traffic, latency and delivery for the quarter, with the figures written inline.6---7 8# Platform Report — Q3 20269 10This whole page is one Markdown file. The prose is CommonMark, and every figure11in it is a [Comark](https://comark.dev) component block that resolves to a12[markdown-graphs](https://mdx-graphs.kshv.me) React component at render time.13No MDX, no compile step: the file is read and parsed on each request, so the14same code path would serve Markdown arriving from a database or a model.15 16::graph-stat17---18title: Quarter at a glance19items:20  - { value: "99.98%", label: "Availability", hint: "SLO 99.95%", accent: true }21  - { value: "128ms", label: "p95 response", hint: "-14% vs Q2" }22  - { value: "41.2M", label: "Requests", hint: "peak 890 rps" }23  - { value: "312", label: "Deploys", hint: "3.4 per weekday" }24---25::26 27## Traffic28 29Requests grew through the quarter without a matching rise in latency. The30September step comes from the search rollout described further down.31 32::graph-plot33---34title: Requests per week (millions)35data: [2.4, 2.5, 2.7, 2.6, 2.9, 3.1, 3.0, 3.3, 3.5, 3.4, 3.8, 4.1, 4.0, 4.3]36labels: [Jul, Aug, Sep, Oct]37variant: area38height: 839palette: duo40---41::42 43Latency held flat while volume rose by two thirds. The p95 line is the one we44report against; p99 stayed inside budget but is noisier.45 46::graph-kpi47---48title: p95 server response49value: 128 ms50label: 14-week trend51hint: budget 200 ms, never breached52data: [186, 181, 174, 178, 165, 160, 158, 149, 151, 142, 139, 134, 130, 128]53---54::55 56### Where the time goes57 58Latency by region and hour of day, in UTC. Ap-southeast is the one region59without a local read replica, and it shows.60 61::graph-heatmap62---63title: p95 by region and hour (UTC)64columns: ["00", "02", "04", "06", "08", "10", "12", "14", "16", "18", "20", "22"]65max: 966legend: true67caption: Darker is slower. Scale is relative to the worst cell.68rows:69  - { label: "us-east-1", values: [1, 1, 1, 2, 3, 4, 5, 6, 6, 5, 3, 2] }70  - { label: "us-west-2", values: [1, 1, 1, 1, 2, 3, 4, 5, 5, 4, 2, 1] }71  - { label: "eu-west-1", values: [3, 4, 5, 6, 6, 5, 4, 3, 2, 2, 1, 2] }72  - { label: "ap-southeast-1", values: [6, 7, 8, 9, 9, 8, 7, 5, 4, 3, 4, 5] }73---74::75 76## Delivery77 78Twelve of thirteen weeks were fully green. The 12 August window was a79degraded config push, caught by canary and rolled back in nine minutes.80 81::graph-uptime82---83title: Daily status, last 13 weeks84from: Jul 185to: Sep 3086columns: 2687days: [ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, degraded, degraded, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok, ok]88---89::90 91Bundle sizes are the one budget we came close to breaking. `/search` is over92its allowance and is the first thing on next quarter's list.93 94::graph-table95---96title: Route bundles against budget97headers: [Route, First load, Budget, Headroom]98align: [left, right, right, right]99rows:100  - ["/", "94 kB", "110 kB", "+16 kB"]101  - ["/docs", "121 kB", "140 kB", "+19 kB"]102  - ["/dashboard", "168 kB", "180 kB", "+12 kB"]103  - ["/search", "204 kB", "180 kB", "-24 kB"]104footer: [4 routes, "587 kB", "610 kB", "+23 kB"]105---106::107 108::graph-meter{title="Test coverage" value=0.86 ticks=28 caption="86% of statements, up from 79%"}109::110 111## The search rollout112 113Search shipped behind a flag on 2 August and reached everyone on 14 September.114The request path picked up two hops, which is where the September latency step115in the traffic chart comes from.116 117::graph-flow118---119title: Request path after the rollout120rows:121  - nodes:122      - { label: "client" }123      - { label: "edge cache", tone: muted }124      - { label: "router", stretch: true }125  - nodes:126      - { label: "router" }127      - { label: "search api", tone: accent }128      - { label: "index shard", tone: accent }129  - nodes:130      - { label: "router" }131      - { label: "app server" }132      - { label: "postgres", tone: muted }133---134::135 136::graph-timeline137---138title: Rollout139events:140  - { date: "Aug 2", label: "Flag on for staff", state: done }141  - { date: "Aug 19", label: "5% of traffic", state: done }142  - { date: "Sep 3", label: "50%, replicas added", state: done }143  - { date: "Sep 14", label: "Full rollout", state: done }144  - { date: "Oct 6", label: "Remove the flag", state: now }145  - { date: "Oct 20", label: "Retire the old path", state: next }146---147::148 149Adoption ran roughly a third of sessions, and converted better than browse.150 151::graph-funnel152---153title: Search sessions to result click154stage: 7-day window, all regions155ticks: 32156steps:157  - { label: "Sessions", value: 1000, display: "412k" }158  - { label: "Opened search", value: 344, display: "142k" }159  - { label: "Typed a query", value: 291, display: "120k" }160  - { label: "Saw results", value: 286, display: "118k" }161  - { label: "Clicked a result", value: 214, display: "88k" }162---163::164 165## Next quarter166 167::graph-gantt168---169title: Committed work170stage: Oct — Dec171columns: 24172progress: 0.08173ticks: [Oct, Nov, Dec]174items:175  - { label: "Split /search bundle", start: 0, end: 6, accent: true, complete: 0.15 }176  - { label: "ap-southeast replica", start: 2, end: 9, accent: true }177  - { label: "Retire legacy path", start: 6, end: 12 }178  - { label: "Config canary v2", start: 9, end: 17 }179  - { label: "Cost review", start: 16, end: 23 }180---181::182 183::graph-check184---185title: Exit criteria186items:187  - { label: "SLO holds at 99.95%", done: true }188  - { label: "p95 under 200 ms", done: true, note: "128 ms" }189  - { label: "Every route inside budget", note: "/search over by 24 kB" }190  - { label: "Legacy search path removed", note: "blocked on the flag" }191  - { label: "Runbook reviewed", done: true }192---193::194 195---196 197Every figure above is a `::graph-*` block in `content/report.md`. Switch to the198source view to read the block that produced any of them, or see the199[catalog](/catalog) for the rest of the components.