Status

Every Achar environment is a set of AWS resources in one account, so the honest answer to "is Achar up" is: the API you are calling is up or it is not, and you can ask it.

Asking your own deployment

`GET /v1/info` is the one route that needs no token. It answers with the service name, its version, the stage, the region, and whether the token you sent resolved to a person. A monitor pointed at it tells you more about your environment than any page we could publish.

curl -s https://your-api.example.com/v1/info

Where the failures show up

A request that reaches a function and fails is a 5xx with an error envelope and a request id. That id is the string to search CloudWatch for, and the console's Logs tab searches a stage's functions by name and by filter pattern.

• A failed deploy is in CloudFormation, and the console reads its events rather than remembering them.
• A webhook that could not be delivered is retried five times and then kept in a dead-letter queue, which the console reports on.
• A document that will not save is a validation issue, and the studio lists them beside the fields that caused them.