✦ network status

Network status.

When an artwork is slow to load or briefly disappears, it's almost never the museum — it's the blockchain or a provider along the way. This page explains what each failure means and shows the last one your browser recorded.

Last loaded status.

read from browser — · 24h window

route/gallery

Collection

✓ no failure recorded in the last 24h.

route/nft/$id

Artwork page

✓ no failure recorded in the last 24h.

The museum keeps no history beyond what's in your own browser. If nothing shows up, nothing has failed for you.

Failure categories.

The museum classifies every on-chain error into one of these categories before logging telemetry and drawing the error panel.

01 / 06↑ top

timeout [timeout]

The blockchain took too long to respond.

The request was canceled before the RPC node finished responding — usually short-lived congestion on the network or provider. Automatic failover already tries a second provider before surfacing this error.

http code: no HTTP code (the connection was aborted before any response)
what to do: Wait a few seconds and try again. If it keeps happening, check the provider status.

02 / 06↑ top

rate limit [rate-limit]

The RPC provider throttled the request.

We exceeded the provider per-second call quota (Alchemy). It happens during visit spikes. The exponential backoff on the 'try again' button spaces out retries to reduce pressure.

http code: HTTP 429 — Too Many Requests
what to do: Wait 30–60s. If it happens often, it's time to review the provider plan.

03 / 06↑ top

rpc unavailable [rpc-down]

The RPC node responded with a 5xx error.

The blockchain provider is unstable — gateway, upstream or service down. Failover already tries a secondary endpoint before showing this failure.

http code: HTTP 500–599 (502 Bad Gateway, 503 Service Unavailable, 504 Gateway Timeout)
what to do: Check the public provider and Cloudflare status pages; it usually resolves in minutes.

04 / 06↑ top

no connection [network]

We couldn't reach the blockchain from this browser.

The request failed before it reached the provider — DNS, refused connection, firewall, offline browser or an ad blocker filtering the RPC domain.

http code: no HTTP code (the request never left the browser)
what to do: Check your connection, disable VPN/extensions and try again.

05 / 06↑ top

client error [client-error]

The request was rejected by the provider.

Probably an invalid API key, malformed address or non-existent contract. This isn't a transient failure — retrying with the same data won't help.

http code: HTTP 400, 401, 403, 404 and similar
what to do: Flag the admin: the configuration needs review (key, network, contract).

06 / 06↑ top

unknown failure [unknown]

Error not classified by the museum.

The error message didn't match any of the categories above. Telemetry records the full technical message for later analysis.

http code: varies
what to do: Try again. If it persists, copy the technical message and send it to support.

Public status pages.

Before reporting a problem, it's worth checking whether the incident is already being investigated by one of the providers in the chain.

still stuck?

Copy the technical message and reach out to the curation team.

contact@nftmuseum.art →

← back to museum