User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Sequel 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 → sequel.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 2 hr ago. Last stored result reached it in 206 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 09 | 0 | 0.0 | 845 ms | 0 |
| Mon 12 | 0 | 0.0 | 101 ms | 0 |
| Mon 14 | 0 | 0.0 | 243 ms | 0 |
| Mon 16 | 0 | 0.0 | 203 ms | 0 |
| Mon 18 | 0 | 0.0 | 87 ms | 0 |
| Mon 20 | 0 | 0.0 | 229 ms | 0 |
| Mon 22 | 0 | 0.0 | 290 ms | 0 |
| Tue 00 | 0 | 0.0 | 221 ms | 0 |
| Tue 02 | 0 | 0.0 | 242 ms | 0 |
| Tue 04 | 0 | 0.0 | 112 ms | 0 |
| Tue 07 | 0 | 0.0 | 102 ms | 0 |
| Tue 09 | 0 | 0.0 | 228 ms | 0 |
| Tue 11 | 0 | 0.0 | 165 ms | 0 |
| Tue 13 | 0 | 0.0 | 209 ms | 0 |
| Tue 15 | 0 | 0.0 | 216 ms | 0 |
| Tue 18 | 0 | 0.0 | 163 ms | 0 |
| Tue 20 | 0 | 0.0 | 117 ms | 0 |
| Tue 22 | 0 | 0.0 | 179 ms | 0 |
| Wed 00 | 0 | 0.0 | 312 ms | 0 |
| Wed 02 | 0 | 0.0 | 416 ms | 0 |
| Wed 05 | 0 | 0.0 | 433 ms | 0 |
| Wed 07 | 0 | 0.0 | 91 ms | 0 |
| Wed 09 | 0 | 0.0 | 651 ms | 0 |
| Wed 12 | 0 | 0.0 | 92 ms | 0 |
| Wed 14 | 0 | 0.0 | 195 ms | 0 |
| Wed 16 | 0 | 0.0 | 279 ms | 0 |
| Wed 18 | 0 | 0.0 | 397 ms | 0 |
| Wed 20 | 0 | 0.0 | 234 ms | 0 |
| Wed 22 | 0 | 0.0 | 122 ms | 0 |
| Thu 01 | 0 | 0.0 | 184 ms | 0 |
| Thu 03 | 0 | 0.0 | 146 ms | 0 |
| Thu 05 | 0 | 0.0 | 391 ms | 0 |
| Thu 07 | 0 | 0.0 | 134 ms | 0 |
| Thu 09 | 0 | 0.0 | 282 ms | 0 |
| Thu 11 | 0 | 0.0 | 251 ms | 0 |
| Thu 13 | 0 | 0.0 | 258 ms | 0 |
| Thu 15 | 0 | 0.0 | 130 ms | 0 |
| Thu 17 | 0 | 0.0 | 110 ms | 0 |
| Thu 19 | 0 | 0.0 | 91 ms | 0 |
| Thu 21 | 0 | 0.0 | 114 ms | 0 |
| Thu 23 | 0 | 0.0 | 474 ms | 0 |
| Fri 01 | 0 | 0.0 | 310 ms | 0 |
| Fri 03 | 0 | 0.0 | 505 ms | 0 |
| Fri 05 | 0 | 0.0 | 129 ms | 0 |
| Fri 07 | 0 | 0.0 | 130 ms | 0 |
| Fri 09 | 0 | 0.0 | 106 ms | 0 |
| Fri 12 | 0 | 0.0 | 177 ms | 0 |
| Fri 14 | 0 | 0.0 | 206 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 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Sequel 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 Sequel yet. Outages of 10 minutes or more get their own page here.
Having trouble with Sequel?
One report per service every 10 minutes from this network. No account.
Follow Sequel
Get an email when Sequel goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Sequel alerts to Slack, Discord or a webhook — free.
About Sequel
Sequel is listed in our AI category and checked at sequel.io. Host webinars on your domain with AI-driven action. Capture full buyer context, convert intent in real-time, and turn events into pipeline.
Sequel publishes an official status page at status.sequel.io; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 194 ms average, 38–505 ms range across 14 successful checks.
Questions
Is Sequel down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Sequel last down?
We have not recorded a public Sequel incident since monitoring began 8 days ago.
What is Sequel's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Sequel respond?
194 ms on average over the last 24 hours (38–505 ms).
Does Sequel have an official status page?
Yes, at https://status.sequel.io.
Sequel 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 Sequel here at once, the problem is on Sequel'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 Sequel. 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.