Skip to main content

Is OpenSea Down?

No — OpenSea is up

Reachable from all 8 checked regions

Average response time: 219ms

Last checked · checks run every 6 hours

Official status page: https://status.opensea.io

OpenSea uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
269ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 75 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

75-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 31 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 40 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 31 checks
Oct 1: 100.00% uptime, 29 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 24 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

cdg
130ms
DNS 27ms TCP 2ms TLS 9ms TTFB 98ms
dfw
335ms
DNS 152ms TCP 1ms TLS 6ms TTFB 293ms
ewr
191ms
DNS 61ms TCP 2ms TLS 7ms TTFB 150ms
fra
143ms
DNS 27ms TCP 2ms TLS 11ms TTFB 117ms
gru
112ms
DNS 21ms TCP 2ms TLS 7ms TTFB 91ms
iad
141ms
DNS 46ms TCP 1ms TLS 6ms TTFB 113ms
jnb
469ms
DNS 180ms TCP 0ms TLS 17ms TTFB 439ms
lax
234ms
DNS 76ms TCP 2ms TLS 7ms TTFB 198ms

What OpenSea does

OpenSea is a marketplace for trading NFTs and tokens across several blockchains. It provides the listings, search and trading interface, but the assets themselves and the transactions that move them live on chain. That split matters during an outage: the marketplace can be unreachable while the items it lists are entirely unaffected.

What an outage looks like

Listings fail to load or show stale prices, and collection pages return errors while the wallet connects normally. Attempts to list or buy hang at the signing step, or the transaction submits and the interface never updates to reflect it. Search returns nothing. Mobile app and website can fail independently, and API consumers see errors while the site itself loads.

What to do about it

Check status.opensea.io, which tracks the website, the API, the mobile application and support separately, and publishes platform response time and Polygon transaction processing time as live metrics. If a transaction was already signed and broadcast, check a block explorer rather than the marketplace, because it may have settled on chain even though the interface never showed it. Do not re-sign a transaction until you have confirmed that.

Is it down for everyone, or just you?

If this page says OpenSea is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

OpenSea outage FAQ

Are my NFTs safe if OpenSea is down?
Yes. Assets are held in your own wallet on chain, not by the marketplace, so an OpenSea outage affects only your ability to browse and trade through their interface. Ownership is unchanged and the items remain visible in your wallet and through any other marketplace or block explorer that reads the same chain.
My transaction is stuck. Did it go through?
Check a block explorer rather than the OpenSea interface. Once a transaction is signed and broadcast it is in the hands of the network, so it can confirm on chain while the marketplace front end fails to reflect it. Re-signing before checking is how people pay gas twice for the same action. The explorer is authoritative here, not the site.
Is it OpenSea or the blockchain that is having problems?
They are different failures and OpenSea helps distinguish them by publishing Polygon transaction processing time alongside its own platform response time. Slow or failed transactions with a healthy marketplace point at network congestion, while pages that will not load at all point at OpenSea. A block explorer confirms whether the chain itself is producing blocks normally.
Does the mobile app work when the website is down?
Sometimes, because they are separate components. OpenSea tracks the website and the mobile application individually, so one can be operational while the other is not. The API is listed separately again, which means third party tools and portfolio trackers reading OpenSea data can break while both the site and the app are working normally.
Will an active listing expire during an outage?
Listings are recorded with their own duration and are not cancelled by the marketplace being unavailable. The practical risk is that a listing you intended to update or cancel stays live because the interface would not accept the change. If cancelling matters urgently, the transaction can be made directly rather than through the site, though that requires care.

How we measure this

  • We request OpenSea's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where OpenSea publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when OpenSea goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required