Context.dev logo

Is Context.dev down?

No reported issues

From status.context.dev · checked 1 minute ago · every 5 minutes

Get alerts for Context.dev

An email when it goes down, and when it’s back.

As of 03:30 UTC on 12 November 2026, Context.dev's status page reports no issues. Its last reported problem was on 10 November 2026: “api.context.dev/v1/web/sic is down”, major outage, for 15 min from 17:13 UTC.

Last problem
10 Nov · 15 min
Problems, last 30 days
8
Typical incident
15 min
Longest in 90 days
1 h 18 min · 14 Oct

Uptime

Context.dev, last 30 days

99.64 %

100%95%90%
Oct 14 Today

Biggest dip: Context.dev, 1.3 h of major outage on Oct 14.

Incidents

Started in the last 7 days

3

210
FSSMTWToday

This week Week before

Latest: Context.dev, major outage on Nov 10.

Recovery

Median time back online

10 min

1 h 18 min0
30 days ago Today

7 of 8 were over within an hour. Each dot is one incident; the dashed line is the median.

Components 23

All online

Websites 2 parts
  • context.dev
  • docs.context.dev
APIs 18 parts
  • api.context.dev/v1/web/scrape/markdown
  • api.context.dev/v1/web/scrape/html
  • api.context.dev/v1/web/scrape/images
  • api.context.dev/v1/web/scrape/sitemap
  • api.context.dev/v1/web/crawl
  • api.context.dev/v1/web/screenshot
  • api.context.dev/v1/web/styleguide
  • api.context.dev/v1/web/fonts
  • api.context.dev/v1/web/naics
  • api.context.dev/v1/web/sic
  • api.context.dev/v1/brand/retrieve
  • api.context.dev/v1/brand/retrieve-by-name
  • api.context.dev/v1/brand/retrieve-by-email
  • api.context.dev/v1/brand/retrieve-by-ticker
  • api.context.dev/v1/brand/retrieve-simplified
  • api.context.dev/v1/brand/transaction_identifier
  • api.context.dev/v1/brand/prefetch
  • api.context.dev/v1/brand/prefetch-by-email
CDN 3 parts
  • logos.context.dev
  • logos.brand.dev (legacy)
  • media.brand.dev

Last 90 days

12 incidents in 47 days tracked · no reported issues 99.4% of the time · typical incident 15 min

Aug 15 Today (UTC)

Recent incidents

Times in UTC

  1. Major outage
    api.context.dev/v1/web/sic is down 15 min
  2. Major outage
    api.context.dev/v1/web/sic is down 10 min
  3. Major outage
    logos.brand.dev (legacy) is down 5 min
  4. Major outage
    logos.context.dev is down 10 min
  5. Major outage
    logos.context.dev is down 5 min
  6. Major outage
    api.context.dev/v1/web/sic is down 10 min
  7. Major outage
    api.context.dev/v1/brand/prefetch and api.context.dev/v1/brand/prefetch-by-email are down and 1 more 15 min
  8. Major outage
    api.context.dev/v1/web/naics and api.context.dev/v1/web/sic are down 1 h 18 min
  9. Major outage
    api.context.dev/v1/web/naics is down 30 min
  10. Major outage
    api.context.dev/v1/web/crawl is down and 3 more 35 min
All incidents on status.context.dev ↗

Where this comes from

Stackpulse reads Context.dev’s official status page at status.context.dev every 5 minutes and keeps 90 days of what changed. We don’t test Context.dev ourselves, so a problem shows here once Context.dev reports it.

Stackpulse isn’t affiliated with Context.dev. Names and logos belong to their owners.

For agents and scripts

The same data as Markdown for AI agents, updated every 30 seconds. With Pro, the API and the MCP server give scripts and AI assistants every service and your own dashboards.