An API fails on the server's side
Weik.io 2026.2At least 5 % of at least 20 calls to an API version failed on the server's side in 15 minutes. From 25 %, the problem is an error. Video
Watch: Watch the calls, 3:33
The video finds each call on the Requests page and follows one of them into its trace.
This part of the video couldn't be loaded.
| Kind | Severity | Who sees it |
|---|---|---|
api- |
Warning, and an error from 25 % of the calls | Platform administrators and members whose grant covers the API |
Its row in the problem list has a figure such as 8 of 130 calls failed on the server side in 15 min.
What it means#
Calls to an API version fail on the server’s side. A call fails there when it ends with a status of 500 or above, or when its upstream can’t be reached or doesn’t answer in time. A call relayed to a gateway at a site also fails on the server’s side when that gateway doesn’t take it in time. A call that fails because of the caller, or that the gateway’s rules block, counts among the calls but not as a failure.
What raises it#
Weik.io checks the calls in each environment where the API version is deployed. You don’t see this problem for a version that is no longer deployed, or on an installation set up without the hub’s metric store. If you can read the integration behind the API, the problem’s detail shows that integration.
What to check#
See the API’s calls with their failures and response times:
$ weikio metrics --api <project>/<api>@<version> --env <environment> --since 1hOpen the failed calls’ traces, which continue into the integration behind the API:
$ weikio traces --api <project>/<api>@<version> --env <environment> --errors --since 15mRead the version’s routes and upstreams:
$ weikio describe apiversion <project>/<api>@<version>How to fix it#
- When the upstream is one of your integrations, find the cause in its traces and logs or in its rows in the problem list.
- When the upstream is another system, check that it answers at the address in the version’s cluster.
- When a version broke the API, roll the version back to the definition it served before.
To roll the version back, run:
$ weikio api rollback <project>/<api>@<version> --env <environment>