Is Nuxt.Cloud down today?

Real-time Nuxt.Cloud outage reports and status worldwide!

Nuxt.Cloud

Nuxt.Cloud is a cloud-provider

Access problems:
hour:0 day:0

Nuxt.Cloud outage chart



24 hours

                            Nuxt.Cloud status online

Tag cloud

Here will be tags, when there will be more data

based on user reports and queries over the last 24 hours

Nuxt.Cloud outage statistics

What countries is Nuxt.Cloud down in right now?

During last hour where are reports about Nuxt.Cloud not working in regions:

Which devices has problems opening Nuxt.Cloud?

Operating systems of devices, from which fault reports are arriving:

52.6% Windows21.1% Android15.8% iOS10.5% Mac OS X Others

From which telecom providers networks are arriving complains about Nuxt.Cloud?

Fault reports are arriving from the networks of this telecom providers:

11.1%11.1%11.1%11.1%5.6% Others

* for the last hour

Deployment fails without clear error

Build succeeds locally but breaks on Nuxt.Cloud? First check the Node.js version in your project settings — it must match what you use locally. Then look at the build logs line by line: most failures come from missing environment variables or incompatible dependencies. Add all required .env values in the dashboard under Project → Environment Variables before re-triggering the deploy.

Site returns 500 after fresh deploy

This almost always means a server-side runtime error, not a build issue. Open the Functions log in the dashboard and look for the first uncaught exception. Common culprits:

- a module that works in Node but not in the edge runtime

- missing runtime config keys (runtimeConfig in nuxt.config.ts must have all keys defined, not just set via env)

- dynamic imports that aren''t compatible with SSR

Switch the route to client-only rendering as a quick workaround while you debug.

Static assets load but pages don''t

If CSS and images come through but navigating to any route gives a blank screen or 404, the issue is usually with the output mode. Make sure output is set to ''server'' if you need SSR, or ''static'' for a fully pre-rendered site. Mixing them without explicit route rules causes exactly this behavior.

Edge functions respond slowly

High latency on API routes deployed as edge functions is often caused by cold starts triggered by low traffic. To reduce this:

- keep function bundles small — avoid importing heavy libraries like lodash or moment

- use server routes only for logic that genuinely needs the server

- cache responses where possible using useStorage or HTTP cache headers

Preview deployments not updating

Pushing to a branch but the preview URL still shows old content? Check that the Git integration is connected to the correct repository and branch in the dashboard. If the webhook fired but the build didn''t start, revoke and re-authorize the GitHub or GitLab connection — token permissions sometimes expire after repo transfers.

Environment variables missing at runtime

Variables set in the dashboard are only injected at build time unless you explicitly mark them as runtime variables. Any key you need accessible via useRuntimeConfig() must be listed under runtimeConfig in nuxt.config.ts. Without that, the value will be undefined even if it''s correctly set in the project settings.

You might be interested in the current status of the following services

Status of Serverspace servicesServerspace Status of U1 HOST servicesU1 HOST
Status of Investing.com servicesInvesting.com Status of Amazon Web Services servicesAmazon Web Services