Server status.

Q: What does each component cover?

Website and dashboard: clousd.com, sign-in and the dashboard, served by the same web server that runs these checks. API: the public REST API at api.clousd.com. Live screens and ADB relay: the gateway that streams device screens to your browser and relays ADB sessions.

Q: Can I get notified when something breaks?

For your own devices, yes: webhooks send health.problem and health.resolved events to your endpoint, signed with HMAC-SHA256. This page itself does not send email or feed alerts.

Real checks of the website, the API and the gateway behind live screens and ADB. Our web server runs them when this page is opened, at most every five minutes, and keeps 90 days of results. Nothing here is typed in by hand.

All systems operationalThe website, the API and live screens answered the last check.

Checked just now

Website and dashboardclousd.com

Operational18 ms

90 days ago45 days ago 100% uptime over 1 day with checks Today

APIapi.clousd.com

Operational156 ms

90 days ago45 days ago 100% uptime over 1 day with checks Today

Live screens and ADB relayStreaming and ADB gateway

Operational60 ms

90 days ago45 days ago 100% uptime over 1 day with checks Today

99% of checks or more 90% to 99% Under 90% No data Days in UTC

About this page.

When someone opens this page, and at most once every five minutes, our web server runs three checks and stores the result. The bars above are built from those results only.

What counts as up. The website is up when it serves this page and reads its database. The API is up when api.clousd.com answers a request without a key; an “unauthorized” answer counts, because it came from the API. Live screens and ADB are up when their gateway answers its health check. Each check waits up to four seconds.

Your own devices. This page covers shared services, not single devices. Health, incidents and what we did about them are in the dashboard and in the API, and webhooks tell your systems when a device has a problem and when it is resolved.

Report a problem Read the docs

Latest checks, UTC	Website	API	Live screens
28 Sep, 13:09	OK	156 ms	60 ms
28 Sep, 10:35	OK	430 ms	115 ms

Questions, answered.

Something not covered here? Write to support and a person answers, usually within a working day.

How often is this page updated?

A new check runs at most once every five minutes, when the page is opened. The time of the last check is shown at the top; reload the page to see the latest result.

What does each component cover?

Website and dashboard: clousd.com, sign-in and the dashboard, served by the same web server that runs these checks. API: the public REST API at api.clousd.com. Live screens and ADB relay: the gateway that streams device screens to your browser and relays ADB sessions.

Everything is green, but my device is not working.

This page checks shared services, not single devices. Open the device in the dashboard to see its health and incidents, or ask the API. If it is still unclear, write to support with the device ID.

Why are some days gray?

Gray means there were no checks that day. The history starts on the day this page went live, and we do not fill in days we did not measure. Uptime is counted over days with checks only.

Can I get notified when something breaks?

For your own devices, yes: webhooks send health.problem and health.resolved events to your endpoint, signed with HMAC-SHA256. This page itself does not send email or feed alerts.

Your first device is a minute away. The first 30 are free.

No card, no top-up.
Create an account, launch a device, use it for half an hour.
If it does the job, add funds and keep going. If not, you have lost nothing.

Start free trial Contact support

Stopped phones cost nothingOne trial per account, the device keeps its state