OpenSea status history

Current state: operational — “All Systems Operational” per https://status.opensea.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

0incidents, last 30 days

1incidents, last 90 days

3incidents on record

Incidents per week, last 12 weeks:

Get OpenSea alerts in your Slack — free template RSS for OpenSea

How long do OpenSea incidents last?

5.6 hmedian incident duration3 measured

14.7 h90th percentile1 in 10 ran longer

2.8 hmedian, major/critical only2 incidents

From 3 incidents with a vendor-posted start and resolve time. Longest on record: Partial Service Degradation Due to Third-Party Provider Issue — 14.7 h (2025-10-20 16:20 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (3)

Started	Incident	Status	Impact	Duration
2026-07-01 18:06 UTC	Token balance processing delayed	resolved	critical	5 h 34 min
2025-10-21 01:09 UTC	The incident has been resolved	resolved	critical	0 min
2025-10-20 16:20 UTC	Partial Service Degradation Due to Third-Party Provider Issue	resolved	minor	14 h 42 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch OpenSea with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "opensea"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}