w6w docs

Reliability

Reliability shows the health of every API your project depends on, first-party and third-party alike, in one board. Each service gets two signals:

  • Ops: how your own calls through W6W went: errors and latency.
  • API: what the vendor’s own status page says, when it publishes one.

A service can be fine on one and not the other. Your calls can fail because a key was revoked while the vendor reports all green, and the vendor can report an incident that hasn’t touched your calls yet.

The services listed are the integrations across your account. The numbers come from the project you’re in.

Read the board

  1. In the sidebar, under Observe, click Reliability.
  2. Read Service reliability for the window shown (the last 30 days):
    • Needs attention: services with a problem now, or earlier in the window, as cards at the top;
    • Performance across your APIs: a chart of the services;
    • a table with Service, Status (the Ops and API lines), a bar for the Last 30 days, and Latency.
  3. Click a service to open its detail page.

How you know everything’s fine: the board shows All clear: every service you called in the window came back without degraded stretches or outages.

Statuses read Operational, Degraded, Down, Unknown or Unavailable. Unknown means W6W has no recent evidence either way; Unavailable on the API line means the vendor’s status page couldn’t be read.

Look at one service

The detail page has:

  • Calls in window, p95 latency, Last call and Errors;
  • Error mix: which kinds of error, and how many;
  • API status: what was read from the vendor’s own status page, including any incidents;
  • Last 30 days: the day-by-day bar;
  • Recent calls: up to the latest 50, with When, Action, Method, Status and Took.

← Back to all services returns to the board.

Troubleshooting

SymptomCauseWhat to do
No services yet — connect an integration or use a service in this project.Nothing has been called from this project.Add an integration and call it.
A service shows UnknownNo calls in the window and no health check result.Call it, or Test connection on its integration.
Ops is down but API is operationalThe problem is on your side: credentials, permissions or the parameters you send.Open Recent calls and Error mix, then check the integration.
Select a project to see its reliability.No project is selected.Pick one with the Project switcher.

Where to next

  • Integrations: fix or rotate a failing service’s credentials.
  • History: the runs behind a failure.
  • Dashboard: the compact version of this board.