User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is Twind 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 → twind.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 54 min ago. Last stored result reached it in 809 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 |
|---|---|---|---|---|
| 09:15 | 0 | 0.0 | 888 ms | 0 |
| 11:15 | 0 | 0.0 | 974 ms | 0 |
| 13:30 | 0 | 0.0 | 877 ms | 0 |
| 15:30 | 0 | 0.0 | 953 ms | 0 |
| 17:30 | 0 | 0.0 | 930 ms | 0 |
| 19:45 | 0 | 0.0 | 961 ms | 0 |
| 21:45 | 0 | 0.0 | 1024 ms | 0 |
| 23:45 | 0 | 0.0 | 843 ms | 0 |
| 01:45 | 0 | 0.0 | 909 ms | 0 |
| 02:30 | 0 | 0.0 | 948 ms | 0 |
| 04:45 | 0 | 0.0 | 886 ms | 0 |
| 06:45 | 0 | 0.0 | 809 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 Twind 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 Twind yet. Outages of 10 minutes or more get their own page here.
Having trouble with Twind?
One report per service every 10 minutes from this network. No account.
Follow Twind
Get an email when Twind goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Twind alerts to Slack, Discord or a webhook — free.
About Twind
We track Twind (twind.io) as part of the AI group. Twind centralises contractor compliance, document validation and site access in one AI-powered platform. Trusted by 3,500+ companies across 30 countries.
Twind publishes an official status page at status.twind.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: 917 ms average, 809–1024 ms range across 12 successful checks.
Questions
Is Twind down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Twind last down?
We have not recorded a public Twind incident since monitoring began 6 days ago.
What is Twind's uptime?
From our own checks: 100% over 6 days of checks.
How fast does Twind respond?
917 ms on average over the last 24 hours (809–1024 ms).
Does Twind have an official status page?
Yes, at https://status.twind.io.
Twind 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 Twind here at once, the problem is on Twind'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 Twind. 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.