Skip to main content
Vendor reliability

Vendor record

Sanity

Vendor reports Operational

Checked

Front door check counts and Sanity’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We send a request to a documented Sanity endpoint and count the checks that got the answer it is documented to give.

  • Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    Endpoint checked
    api.sanity.io
    Scope
    apiNo vendor region
    First check in this window
    Latest clear answer

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Sanity product, region or your app worked.

How we count front door checks

Sanity says

Incident posts from Sanity’s status page, with its titles, impact levels and times. They say what Sanity chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

9

incidents Sanity posted, last 90 days

Median recorded duration: 2h 52m. From 9 incidents with vendor-supplied starts and recorded closure times.

All vendors’ incidents

Most recent records · all dates

  • Intermittent increased API latency for some customers

    Minor

    Started, per Sanity

    Closed in our record(22h 6m)

    Sanity’s post
  • Elevated listener latency affecting Studio performance

    Major

    Started, per Sanity

    Closed in our record(14h 11m)

    Sanity’s post
  • Elevated listener latency and error rate impacting Studio loading

    Critical

    Started, per Sanity

    Closed in our record(4h 35m)

    Sanity’s post
  • Content Agent - Elevated error rates

    Major

    Started, per Sanity

    Closed in our record(1h)

    Sanity’s post
  • Elevated listener latency impacting Studio performance

    Minor

    Started, per Sanity

    Closed in our record(1h 42m)

    Sanity’s post
8 older records
  • Elevated API Errors

    Minor

    Started, per Sanity

    Closed in our record(43m)

    Sanity’s post
  • Elevated API and API CDN rates

    Major

    Started, per Sanity

    Closed in our record(53m)

    Sanity’s post
  • Studio Connectivity Issues

    Major

    Started, per Sanity

    Closed in our record(6h 24m)

    Sanity’s post
  • Issue Viewing Webhooks

    Minor

    Started, per Sanity

    Closed in our record(2h 52m)

    Sanity’s post
  • Slow Query Performance for Some Customers

    Major

    Started, per Sanity

    Closed in our record(4h 25m)

    Sanity’s post
  • Content Agent - Delivery issue with some longer-running threads

    Minor

    Started, per Sanity

    Closed in our record(6h 1m)

    Sanity’s post
  • Sanity MCP Server Unavailability

    Major

    Started, per Sanity

    Closed in our record(12h 35m)

    Sanity’s post
  • Issues with Loading Document Lists in Sanity Studio

    Minor

    Started, per Sanity

    Closed in our record(6h 14m)

    Sanity’s post

Your code, your dependencies

See which of your code paths call Sanity

Connect GitHub or GitLab to find where your public or private repository uses Sanity. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add Sanity status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · SanityStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/sanity?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="Sanity status badge"></iframe>

Frequently Asked Questions

Is Sanity currently down?

Sanity's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did Sanity last have an outage?

The most recent closed incident record began 2 days ago and spans 22h 6m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.

Does CheckUpstream publish an uptime percentage for Sanity?

No. CheckUpstream checks Sanity’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.

How do I monitor Sanity in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track Sanity?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.