# Service status and reporting an outage

> How to check whether RemakeCV is up, distinguish a service problem from a local one, and report an outage effectively.

Source: https://www.remakecv.com/help/reference/service-status
Last updated: 2026-08-21

---
To check whether RemakeCV is up, call the API health endpoint first — `GET /api/public/v1/health` returns `{"status":"ok"}` without authentication, so it separates a service outage from a credential or network problem. If it responds but the app does not work for you, the problem is likely local. Report outages to support@remakecv.com.

## Is it us or you?

### Check the health endpoint

    ```bash
    curl https://app.remakecv.com/api/public/v1/health
    ```
A response of `{"status":"ok"}` means the service is reachable. No authentication needed. See [`GET /health`](https://www.remakecv.com/help/api-reference/endpoints/health.md).

### Ask a colleague

If it works for them, the problem is your browser, network or account rather than the service.

### Try a different browser or network

Rules out an extension, a cached asset, or a corporate firewall.

### Read the error carefully

Many apparent outages are account conditions — "No credits left" and "credit limit reached" both stop processing without anything being down. See [error codes](https://www.remakecv.com/help/troubleshooting/error-codes.md).

## Slow is not always down

Some things are legitimately slower:

| Situation | Expected |
|---|---|
| Text-based CV | 10–30 seconds |
| Scanned CV requiring OCR | Noticeably longer |
| Bulk batch | Five concurrent, the rest queued |
| Large file | Longer upload before processing starts |

Before reporting slowness, process a small text-based CV. If that is fast, the pipeline is healthy and the delay is input-specific.

## Reporting an outage

Email support@remakecv.com with:

- **What you were doing** — uploading, downloading, using an integration
- **What happened** — the exact message, or a description
- **When** — approximate time and timezone
- **Scope** — just you, or everyone at your agency
- **`request_id`** — if it was an API call. This is the single most useful thing you can include

> **Tip:** 
Screenshot the error before dismissing it. A description of a message is much harder to trace than the message itself.

## What if I am mid-submission?

If you have a formatted CV open, download it before troubleshooting. Even if it is imperfect, a downloaded file is a file you can send.

If CV storage is disabled for your company, this matters more — there is no history to return to. See [CV history](https://www.remakecv.com/help/formatting-cvs/cv-history.md).

## Frequently asked questions

### How do I check if RemakeCV is down?

Call GET /api/public/v1/health. It requires no authentication and returns {"status":"ok"} when the service is reachable.

### Processing is slow but not failing. Is that an outage?

Not necessarily. Scanned CVs run through OCR and are legitimately slower. Compare against a text-based CV before reporting it.

### What should I include when reporting a problem?

What you were doing, what happened, the time, and the request_id if it was an API call.