Service status

How to verify the health of the files.link platform — the API, uploads, CDN delivery, and dashboard — yourself, and how to report an incident if something looks wrong. This page is not a live dashboard.

Platform components

The moving parts of the platform, and what each one does. Use the checks in the next section to confirm whether a given component is healthy right now.

API

REST endpoints under /v1 — file creation, presigned upload URLs, and confirm-upload. This is the surface your build scripts and integrations call.

Uploads

Presigned PUT uploads and the confirm-upload step that finalizes a file once the transfer completes.

CDN delivery

Public link serving over our global CDN, plus signed URLs for private files.

Dashboard

The web app for managing projects, folders, files, API keys, billing, and credits.

We don't render a live status indicator here, because we have no independent monitoring feed wired into this page — a hardcoded "operational" badge would stay green during a real outage, and that would be dishonest. We also don't publish a fabricated uptime percentage or a synthetic historical SLA. If something looks degraded, verify it directly with the checks below and reach us.

Check it yourself

files.link is developer infrastructure, so the most reliable signal is the one your own code already gets. If you want to confirm the platform is healthy from your side, the fastest checks are:

API: issue an authenticated request to a /v1 endpoint using your API key in the Authorization header (the raw key, with no Bearer prefix). A normal 2xx response means the API tier is serving requests.
Uploads: run the three-call upload flow — POST /v1/files/{folderId} to mint a presigned URL, PUT the bytes to that URL, then POST /v1/files/confirm-upload. A clean round-trip confirms uploads end to end.
CDN delivery: open a known public link in a fresh tab (or fetch a signed URL for a private file). A 200 with your file body confirms delivery is healthy.
Dashboard: load the app and confirm your projects and files render.

Report an incident

Seeing errors, timeouts, slow delivery, or upload failures that don't match the status above? Tell us — a real report from your account is often the first signal we get, and it helps us scope the problem fast.

Email contact@files.link and include, where you can:

Which component is affected (API, uploads, CDN, dashboard).
The exact endpoint or link, the HTTP status code, and any error body you received.
A timestamp (with timezone) and, for API issues, the request ID if your client logged one.
The account email or project the request was made under — never send us your API key or password.

Build on infrastructure you can verify

files.link is a prepaid, pay-as-you-go platform — you pay only for what you store and serve. No invoices, no surprise plans.

Get started

Questions about uptime, maintenance windows, or SLAs for a larger integration? Reach contact@files.link.