Gorgasali Street · Level 7

Last Tuesday’s gateway traffic, drawn so a person can point at it.


Bundled network cables feeding a gateway cabinet

Cables into a cabinet — the physical side of the routes we later draw.

We keep a small analytics desk in Batumi for teams who already run an API through a gateway and need the week’s requests turned into charts a room can argue over.

Bring a slice of access logs, a list of routes, and the hours that worried you. We plot latency tails, status-code weather, and which upstreams actually took the weight. The sitting is a conversation over those sheets, not a login to a product you must keep feeding.

A chart that cannot be held across a table is not finished.

Send the log window

Inside a Gateway Traffic Review

Flagship

The flagship sitting is a ten-working-day reading of a named log window. We do not take live control of the gateway. We receive files, draw the traffic, and sit with the people who own the routes.

  1. You name the window and the routes that matter. We send a short intake list: log format, clock timezone, and which fields you can actually export.
  2. The desk plots request volume, latency percentiles, and error clusters by route and upstream. Odd spikes get a caption in the margin, not a dashboard tile.
  3. We meet in Batumi or by video with the printed briefing. You leave with the sheets and a list of questions still open in the logs.

Read the full sitting

Other sittings we keep

The full list
Rows of network equipment in a dim cabinet aisle

Desk review and sitting

Gateway Traffic Review

A ten-day reading of a named log window, returned as annotated charts and a sitting over the sheets.

Close view of labelled copper and fibre in a tray

Charted map and short sitting

API Path Mapping

A drawn map of how requests actually walk the gateway: clients, routes, and the upstreams that answer.

An analog clock face in warm low light

Urgent reading and annotated strip

Incident Timeline Reconstruction

After an outage, a minute-by-minute visual ledger of gateway errors, timeouts, and the deploys that sat beside them.

A quiet office interior with long tables and daylight

Recurring sitting

Standing Monthly Review

A reserved morning each month to read the previous window of gateway traffic and update the working charts.

A letter after a nine-minute burst

They asked us to treat a Tuesday morning as a single weather event, not as a monthly average. The briefing opened on the minute the 502s began, marked the upstream that sat silent, and left the TLS handshake times in a side column so we could see they were innocent. I still keep the centre sheet on the cabinet door.

M. Kapanadze · payments API, Kutaisi shop-front

More client word

From the field notes

The ledger