User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Set1 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 → set1.io—
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 41 min ago. Last stored result reached it in 164 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 16 | 0 | 0.0 | 484 ms | 0 |
| Mon 18 | 0 | 0.0 | 270 ms | 0 |
| Mon 20 | 0 | 0.0 | 564 ms | 0 |
| Mon 22 | 0 | 0.0 | 450 ms | 0 |
| Tue 00 | 0 | 0.0 | 560 ms | 0 |
| Tue 02 | 0 | 0.0 | 85 ms | 0 |
| Tue 04 | 0 | 0.0 | 26 ms | 0 |
| Tue 07 | 0 | 0.0 | 69 ms | 0 |
| Tue 09 | 0 | 0.0 | 533 ms | 0 |
| Tue 11 | 0 | 0.0 | 257 ms | 0 |
| Tue 13 | 0 | 0.0 | 286 ms | 0 |
| Tue 15 | 0 | 0.0 | 508 ms | 0 |
| Tue 18 | 0 | 0.0 | 93 ms | 0 |
| Tue 20 | 0 | 0.0 | 546 ms | 0 |
| Tue 22 | 0 | 0.0 | 113 ms | 0 |
| Wed 00 | 0 | 0.0 | 146 ms | 0 |
| Wed 02 | 0 | 0.0 | 130 ms | 0 |
| Wed 05 | 0 | 0.0 | 97 ms | 0 |
| Wed 07 | 0 | 0.0 | 37 ms | 0 |
| Wed 09 | 0 | 0.0 | 60 ms | 0 |
| Wed 12 | 0 | 0.0 | 469 ms | 0 |
| Wed 14 | 0 | 0.0 | 76 ms | 0 |
| Wed 16 | 0 | 0.0 | 141 ms | 0 |
| Wed 18 | 0 | 0.0 | 148 ms | 0 |
| Wed 20 | 0 | 0.0 | 68 ms | 0 |
| Wed 22 | 0 | 0.0 | 456 ms | 0 |
| Thu 01 | 0 | 0.0 | 68 ms | 0 |
| Thu 03 | 0 | 0.0 | 74 ms | 0 |
| Thu 05 | 0 | 0.0 | 116 ms | 0 |
| Thu 07 | 0 | 0.0 | 69 ms | 0 |
| Thu 09 | 0 | 0.0 | 472 ms | 0 |
| Thu 11 | 0 | 0.0 | 81 ms | 0 |
| Thu 13 | 0 | 0.0 | 152 ms | 0 |
| Thu 15 | 0 | 0.0 | 499 ms | 0 |
| Thu 17 | 0 | 0.0 | 297 ms | 0 |
| Thu 19 | 0 | 0.0 | 496 ms | 0 |
| Thu 21 | 0 | 0.0 | 81 ms | 0 |
| Thu 23 | 0 | 0.0 | 47 ms | 0 |
| Fri 01 | 0 | 0.0 | 512 ms | 0 |
| Fri 02 | 0 | 0.0 | 104 ms | 0 |
| Fri 04 | 0 | 0.0 | 109 ms | 0 |
| Fri 06 | 0 | 0.0 | 30 ms | 0 |
| Fri 08 | 0 | 0.0 | 49 ms | 0 |
| Fri 10 | 0 | 0.0 | 484 ms | 0 |
| Fri 11 | 0 | 0.0 | 85 ms | 0 |
| Fri 12 | 0 | 0.0 | 39 ms | 0 |
| Fri 14 | 0 | 0.0 | 50 ms | 0 |
| Fri 16 | 0 | 0.0 | 164 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 6 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Set1 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 Set1 yet. Outages of 10 minutes or more get their own page here.
Having trouble with Set1?
One report per service every 10 minutes from this network. No account.
Follow Set1
Get an email when Set1 goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Set1 alerts to Slack, Discord or a webhook — free.
About Set1
Set1, at set1.io, is one of the AI services we monitor. Set1 is the protection and intelligence layer for the AI-driven internet, built to understand, verify, and safeguard activity across human, AI, and automated interactions.
Set1 publishes an official status page at status.set1.io; 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 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 190 ms average, 30–538 ms range across 15 successful checks.
Questions
Is Set1 down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Set1 last down?
We have not recorded a public Set1 incident since monitoring began 6 days ago.
What is Set1's uptime?
From our own checks: 100% over 6 days of checks.
How fast does Set1 respond?
190 ms on average over the last 24 hours (30–538 ms).
Does Set1 have an official status page?
Yes, at https://status.set1.io.
Set1 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 Set1 here at once, the problem is on Set1'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 Set1. 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.