Terms of service

They apply to everyone who uses isuptime — the website, the pages for individual services, the stack view, and the public JSON endpoints. Using the site means accepting them. If you do not accept them, do not use the site; there is no account to close, because there are no accounts.

isuptime is an independent project run by one person. It is not affiliated with, endorsed by, or operated by any of the 102 services it monitors.

This is the most important section on the page, because almost every way of being let down by isuptime starts by misreading it.

isuptime reads each provider's own public status feed on a schedule and repeats what it finds. It runs no synthetic checks and never tests a service directly. So a status here is a report of a report: if a provider is slow to admit a problem, has not noticed it, or describes it in a way that normalises oddly, this site will be wrong in exactly the same way and at exactly the same moment.

The percentage shown for each service is labelled “no outage reported” and is not uptime. It is the share of recorded checks in which the provider's own feed was not reporting an outage. Periods a provider called degraded count as no-outage, so a service can be badly impaired and still read 100%. It is not a service level agreement, it is not a measurement of whether the service worked for you, and it must not be compared between providers. The reasoning is set out in how it works.

A green status means a provider is not currently reporting a problem. It never means the service will work for you. Account-scoped failures — rate limits, expired credentials, quota, permissions, regional restrictions — do not appear on any status page and cannot appear here.

isuptime offers optional browser notifications and webhook messages when a status it has read gets worse. That feature is a convenience and is provided on a best-effort basis only. It depends on your browser, on your webhook provider, on this site being reachable, and on the upstream provider having published the change in the first place.

Alerts can be late, duplicated, or missed entirely, and no notice is given when they are. Do not use isuptime as the alerting path for anything that matters. If an outage would cost you something, monitor your own dependencies directly and subscribe to the provider's own status notifications as well.

isuptime is provided “as is” and “as available”, without warranty of any kind, whether express or implied, including any implied warranty of merchantability, fitness for a particular purpose, accuracy, or non-infringement.

No promise is made that the site will be available, that it will be free of errors, that the information on it is accurate, complete or current, or that any particular service will continue to be monitored.

To the fullest extent permitted by law, isuptime and the person who runs it are not liable for any loss or damage arising from your use of the site or your reliance on anything shown on it. That includes lost profits, lost data, missed outages, downtime, business interruption, and decisions taken on the basis of a status, percentage, incident, or alert published here.

The site is free and carries no charge, so there is no fee against which to measure a refund. Where liability cannot be excluded by law, it is limited to the minimum permitted by that law.

You may use isuptime for any lawful purpose. You may not:

• Attack it, or attempt to gain access to any part of it, its data, or its infrastructure that has not been made public.
• Put load on it that interferes with other people using it, or work around the rate limits on the alert and contact endpoints.
• Use the notification endpoint to send unsolicited messages, or to deliver anything to a webhook you do not control.
• Republish what you find here as though it were your own measurement, or in a way that implies isuptime is affiliated with or endorsed by a service it monitors.
• Restate the “no outage reported” percentage as uptime, an SLA figure, or a comparison between providers. It is none of those things, and presenting it as one misleads whoever reads it next.

isuptime exposes its readings as JSON at /api/status, /api/incidents and /api/components, with permissive CORS headers, so they can be read from elsewhere. You are welcome to use them, subject to these terms and to a few practical conditions:

• Be reasonable about frequency. The underlying readings only change when the poller runs, so polling faster than that gains you nothing and costs both of us.
• Carry the caveats with the numbers. If you display the percentage, label it as this site labels it.
• Attribute isuptime and link back, so anyone seeing your copy can find out how the figure was produced.
• Expect them to change. These are the site's own internal endpoints, published for convenience rather than as a versioned public API, and their shape may change or they may be withdrawn without notice.

isuptime may be changed, interrupted, or discontinued at any time, in whole or in part, without notice. Services may be added or removed from monitoring — most often because a provider stops publishing a feed that can be read honestly. Nothing here commits the site to continuing to exist.

If you send a message through the contact form or ask for a service through request a service, it is sent on as an email so it can be read and answered, and nothing is written to a database here. By sending it you allow it to be used to answer you and to decide what to do about it — including acting on a suggestion without owing you anything for it. Do not send confidential or sensitive information, credentials, or personal data about other people. What happens to that message is set out in the privacy policy.

Your stack is stored in your own browser and never reaches this site, so it is yours to keep and yours to lose — clearing site data deletes it, and nothing here can restore it.

Product names, logos and brands shown on isuptime belong to their respective owners and are used only to identify the service whose status is being reported. Their provenance and licensing is documented in the project's NOTICE.md, and summarised under trademarks and logos.

The writing on this site — the explanations, the per-service copy and the articles — belongs to isuptime. Quote it with attribution and a link; do not republish it wholesale as your own.

isuptime links to each provider's own status page, incident reports and documentation. Those sites are not under its control, and once you follow one of those links you are on that company's site, under their terms and their privacy policy.

If these terms change, the date at the top of this page changes with them. Continuing to use the site after a change means accepting the revised terms. Material changes will be described here rather than made quietly.

These terms are governed by the laws of the jurisdiction in which the operator of isuptime is resident, and any dispute is subject to the courts of that jurisdiction, except where mandatory consumer-protection law in your own country gives you rights that cannot be set aside.

Questions about these terms can be sent through the contact page.