User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Context.dev down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → context.dev—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 18 min ago. Last stored result reached it in 232 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 04 | 0 | 0.0 | 179 ms | 0 |
| Mon 06 | 0 | 0.0 | 163 ms | 0 |
| Mon 08 | 0 | 0.0 | 253 ms | 0 |
| Mon 11 | 0 | 0.0 | 298 ms | 0 |
| Mon 12 | 0 | 0.0 | 181 ms | 0 |
| Mon 13 | 0 | 0.0 | 286 ms | 0 |
| Mon 16 | 0 | 0.0 | 429 ms | 0 |
| Mon 18 | 0 | 0.0 | 227 ms | 0 |
| Mon 20 | 0 | 0.0 | 182 ms | 0 |
| Mon 22 | 0 | 0.0 | 146 ms | 0 |
| Tue 00 | 0 | 0.0 | 297 ms | 0 |
| Tue 02 | 0 | 0.0 | 333 ms | 0 |
| Tue 04 | 0 | 0.0 | 200 ms | 0 |
| Tue 06 | 0 | 0.0 | 201 ms | 0 |
| Tue 08 | 0 | 0.0 | 240 ms | 0 |
| Tue 10 | 0 | 0.0 | 421 ms | 0 |
| Tue 13 | 0 | 0.0 | 394 ms | 0 |
| Tue 15 | 0 | 0.0 | 471 ms | 0 |
| Tue 17 | 0 | 0.0 | 482 ms | 0 |
| Tue 19 | 0 | 0.0 | 356 ms | 0 |
| Tue 22 | 0 | 0.0 | 148 ms | 0 |
| Wed 00 | 0 | 0.0 | 166 ms | 0 |
| Wed 02 | 0 | 0.0 | 177 ms | 0 |
| Wed 04 | 0 | 0.0 | 183 ms | 0 |
| Wed 07 | 0 | 0.0 | 203 ms | 0 |
| Wed 09 | 0 | 0.0 | 197 ms | 0 |
| Wed 11 | 0 | 0.0 | 388 ms | 0 |
| Wed 13 | 0 | 0.0 | 262 ms | 0 |
| Wed 15 | 0 | 0.0 | 154 ms | 0 |
| Wed 17 | 0 | 0.0 | 198 ms | 0 |
| Wed 20 | 0 | 0.0 | 267 ms | 0 |
| Wed 22 | 0 | 0.0 | 217 ms | 0 |
| Thu 00 | 0 | 0.0 | 179 ms | 0 |
| Thu 02 | 0 | 0.0 | 263 ms | 0 |
| Thu 04 | 0 | 0.0 | 204 ms | 0 |
| Thu 06 | 0 | 0.0 | 255 ms | 0 |
| Thu 08 | 0 | 0.0 | 196 ms | 0 |
| Thu 10 | 0 | 0.0 | 116 ms | 0 |
| Thu 12 | 0 | 0.0 | 129 ms | 0 |
| Thu 14 | 0 | 0.0 | 264 ms | 0 |
| Thu 16 | 0 | 0.0 | 236 ms | 0 |
| Thu 19 | 0 | 0.0 | 183 ms | 0 |
| Thu 21 | 0 | 0.0 | 130 ms | 0 |
| Thu 23 | 0 | 0.0 | 322 ms | 0 |
| Fri 01 | 0 | 0.0 | 260 ms | 0 |
| Fri 03 | 0 | 0.0 | 145 ms | 0 |
| Fri 05 | 0 | 0.0 | 145 ms | 0 |
| Fri 07 | 0 | 0.0 | 232 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Context.dev badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Context.dev yet. Outages of 10 minutes or more get their own page here.
Having trouble with Context.dev?
One report per service every 10 minutes from this network. No account.
Follow Context.dev
Get an email when Context.dev goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Context.dev alerts to Slack, Discord or a webhook — free.
About Context.dev
We track Context.dev (context.dev) as part of the AI group. Context.dev is the web scraping API for AI agents: scrape any URL into LLM-ready Markdown, search the live web, crawl entire sites, and extract structured data with one REST API.
Context.dev publishes an official status page at status.context.dev; when we can read it, its incident level is folded into the status shown here.
Common problems for AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 197 ms average, 116–322 ms range across 12 successful checks.
Questions
Is Context.dev down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Context.dev last down?
We have not recorded a public Context.dev incident since monitoring began 7 days ago.
What is Context.dev's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Context.dev respond?
197 ms on average over the last 24 hours (116–322 ms).
Does Context.dev have an official status page?
Yes, at https://status.context.dev.
Context.dev not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Context.dev here at once, the problem is on Context.dev's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Context.dev. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.