Canva status

How we check Canva

We watch canva.com from all five of our probe regions, every 2 minutes. A region that sees a failure does not make this page say "down" on its own: a second region has to agree first, the same confirmation rule every YoPingMe monitor uses.

We watch Canva's own web host and pin the specific response an anonymous request receives, rather than assuming a 2xx. The Connect API for developer integrations runs separately with its own availability, so this reads the design editor and web app that almost everyone checking this page actually means.

What is Canva?

Canva is a design tool built around a browser-based editor, which means almost everything about using it depends on a live, working connection in a way that a locally installed application does not. That dependency shapes what an incident looks like far more than the product's design features do, and it is worth understanding before treating any editor hiccup as a platform outage.

Autosave is the feature most worth understanding on its own terms, because it is also the source of the most common worry during any disruption. The editor saves continuously in the background rather than on an explicit save action, which is convenient until a connection drops mid-edit and leaves a design in an uncertain state. This is a property of how browser-based editing works generally, not something unique to Canva having a bad day, and refreshing periodically during long sessions is a reasonable habit independent of the platform's health.

Published and embedded designs are worth separating from the live editor entirely. Once a design has been exported or published, viewing it is a different operation from editing it, often served as a static file rather than requiring the full editor to load. An incident affecting the editing experience does not necessarily touch content that was already published elsewhere, and the two failing together is not guaranteed even during a real platform issue.

Developer integrations built on Canva's Connect API depend on separate infrastructure from the web editor most people use directly. An integration failing with API errors is not automatically the same incident as the editor being slow or unreachable, and checking whether the trouble is isolated to API calls specifically is worth doing before assuming a broader outage is underway.

The practical takeaway for anyone relying on Canva for something with a deadline is the same as for any browser-based editing tool: treat network stability as part of the dependency, save deliberately during important sessions rather than trusting autosave alone during known bad connectivity, and check whether a problem is isolated to editing, viewing, or the API before concluding the whole platform is affected.

Frequently asked questions

Is Canva down right now?

Check the board above; it reflects our own probes against Canva from all five of our regions, refreshed every couple of minutes and confirmed across two regions before this page would call it down.

My design will not load or save but this page shows Canva up. What should I check?

Check your own network and browser first, since these cause far more editor trouble than a platform outage. A slow or unstable connection can interrupt autosave mid-edit, a browser extension can interfere with the editor's canvas, and a stale cached tab left open for hours can behave oddly until refreshed, all while Canva's servers answer normally.

Does a Canva outage lose unsaved changes to a design?

It can, since the editor autosaves continuously and depends on a live connection to do so. A brief outage during active editing carries the same risk any autosave-based tool does, which is why refreshing periodically during long editing sessions and confirming a save completed before closing a tab are worth doing regardless of whether Canva is having a good day.

Does a Canva outage affect designs shared publicly or embedded elsewhere?

Viewing an already-published design and editing one are different operations, and a platform issue affecting the editor does not necessarily affect previously published or exported content that is already served as a static file elsewhere. The two can fail independently of each other.

My integration built on Canva's Connect API is failing. Is that the same incident as the editor being down?

Not necessarily. The Connect API for developer integrations runs on separate infrastructure from the web editor, so one can be degraded without the other. Check whether the failure is isolated to API calls specifically before assuming it reflects a broader Canva outage.