Faultline
Five responders are on this incident

Severity 2 incident

INC-2291 Checkout latency over its objective in eu-central

Sev 2 Investigating
Detected
03:12 UTC
Elapsed
Loading the incident clock
Commander
Priya Raman
Next update due
04:15 UTC
Time to detect
6m 41sObjective is 10m
Checkouts affected
12,4801,340 more than at 03:40
Error budget spent
38%11% at the start of the week
Actions still open
10Three closed in the last hour

Workstream board

Drag a card, or use the arrows on it, to move one stage.Use the arrows on a card to move it one stage.

Priya Raman moved FAULT-118 to Mitigating 40 seconds ago

Your board still shows it in Investigating. Their change is the one that saved.

Triage 0
Investigating 0
Mitigating 0
Verifying 0

Customer impact 0

Oldest before mitigating —

  • FAULT-121Support

    Refund queue backing up behind the dropped checkouts

    Sana Okonjo Open for 22m
  • FAULT-118Blocking

    Checkout p99 sitting at 4.8s against a 1.2s objective

    Priya Raman changed this

    Priya Raman Open for 1h 47m
  • FAULT-119Partial

    Shed a fifth of checkout traffic onto the retry path

    Dev Krishnamurthy Open for 41m

    Platform 0

    Oldest before mitigating —

    • FAULT-124Unassigned

      Connection pool saturation on payments-eu-3

      Nobody yet Open for 9m
    • FAULT-116Tracing

      Line up the latency step with the 02:58 payments-api release

      Marco Lindqvist Open for 1h 12m
    • FAULT-123Read only

      Check whether the read replicas took the same step

      Priya Raman Open for 14m
    • FAULT-120Rolling

      Pin payments-api to 4.19.1 across eu-central

      Marco Lindqvist Open for 33m

      Comms and stakeholders 0

      Oldest before mitigating —

      • FAULT-125Standby

        Draft the regulator note in case impact passes two hours

        Alex Whitfield Open for 4m
      • FAULT-122Hourly

        Merchant success update, then every hour until close

        Alex Whitfield Open for 26m
      • FAULT-115Published

        Status page carries the eu-central checkout notice

        Alex Whitfield Open for 1h 28m

        Design notes

        Shape of the page
        A board. Four columns of work crossed by three teams, and a card moves across it.
        What it leads with
        The board. The figures along the top are a summary of it, not a screen of their own.
        Spacing
        Atlassian's own defaults, unchanged. A board is read at a glance, and its spacing is what makes the columns legible from across a room.
        The one bold decision
        Severity reads as length. Each bar shows how long an incident has been open against its own clock, and the head of a column carries the same bar for its oldest unresolved card. Three of those bars on one edge say which column is stuck before a single card has been read.
        Where the colour comes from
        Every colour, size and corner on the page is Atlassian's own published set, taken from the system rather than sampled by eye. The same set supplies the light theme and the dark one.
        Readability, card text
        Text on a card measures 14.34:1 light and 9.84:1 dark, against a floor of 4.5.
        Readability, the age bar
        The bar measures 4.51:1 light and 9.78:1 dark, against the floor of 3 that a drawn mark needs. Atlassian ships a paler version of the same colour that would not have cleared it, and the page does not use it.
        What we changed
        • The page carries its own light and dark switch. Inside Jira the theme belongs to the workspace, but this page stands on its own.
        • Atlassian keeps its own typeface for its own products, so the page falls back to the stack Atlassian names for everybody else.
        • On a narrow screen the four columns become a switcher showing one column at a time. Side by side they need two and a half phone screens of sideways scrolling, with the column name scrolled off.