User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / AI
Is awork.com 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 → awork.com—
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 20 min ago. Last stored result reached it in 137 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 |
|---|---|---|---|---|
| Tue 02 | 0 | 0.0 | 263 ms | 0 |
| Tue 04 | 0 | 0.0 | 131 ms | 0 |
| Tue 06 | 0 | 0.0 | 118 ms | 0 |
| Tue 08 | 0 | 0.0 | 68 ms | 0 |
| Tue 11 | 0 | 0.0 | 129 ms | 0 |
| Tue 13 | 0 | 0.0 | 102 ms | 0 |
| Tue 15 | 0 | 0.0 | 370 ms | 0 |
| Tue 17 | 0 | 0.0 | 259 ms | 0 |
| Tue 20 | 0 | 0.0 | 251 ms | 0 |
| Tue 22 | 0 | 0.0 | 190 ms | 0 |
| Wed 00 | 0 | 0.0 | 224 ms | 0 |
| Wed 02 | 0 | 0.0 | 196 ms | 0 |
| Wed 04 | 0 | 0.0 | 120 ms | 0 |
| Wed 07 | 0 | 0.0 | 188 ms | 0 |
| Wed 09 | 0 | 0.0 | 99 ms | 0 |
| Wed 11 | 0 | 0.0 | 173 ms | 0 |
| Wed 13 | 0 | 0.0 | 186 ms | 0 |
| Wed 15 | 0 | 0.0 | 161 ms | 0 |
| Wed 17 | 0 | 0.0 | 192 ms | 0 |
| Wed 20 | 0 | 0.0 | 192 ms | 0 |
| Wed 22 | 0 | 0.0 | 122 ms | 0 |
| Thu 00 | 0 | 0.0 | 141 ms | 0 |
| Thu 02 | 0 | 0.0 | 157 ms | 0 |
| Thu 04 | 0 | 0.0 | 190 ms | 0 |
| Thu 06 | 0 | 0.0 | 75 ms | 0 |
| Thu 08 | 0 | 0.0 | 253 ms | 0 |
| Thu 10 | 0 | 0.0 | 215 ms | 0 |
| Thu 12 | 0 | 0.0 | 159 ms | 0 |
| Thu 15 | 0 | 0.0 | 262 ms | 0 |
| Thu 17 | 0 | 0.0 | 158 ms | 0 |
| Thu 19 | 0 | 0.0 | 186 ms | 0 |
| Thu 21 | 0 | 0.0 | 287 ms | 0 |
| Thu 23 | 0 | 0.0 | 253 ms | 0 |
| Fri 01 | 0 | 0.0 | 149 ms | 0 |
| Fri 04 | 0 | 0.0 | 249 ms | 0 |
| Fri 06 | 0 | 0.0 | 200 ms | 0 |
| Fri 08 | 0 | 0.0 | 158 ms | 0 |
| Fri 10 | 0 | 0.0 | 136 ms | 0 |
| Fri 12 | 0 | 0.0 | 149 ms | 0 |
| Fri 14 | 0 | 0.0 | 168 ms | 0 |
| Fri 16 | 0 | 0.0 | 191 ms | 0 |
| Fri 17 | 0 | 0.0 | 176 ms | 0 |
| Fri 19 | 0 | 0.0 | 209 ms | 0 |
| Fri 20 | 0 | 0.0 | 74 ms | 0 |
| Fri 21 | 0 | 0.0 | 191 ms | 0 |
| Fri 22 | 0 | 0.0 | 159 ms | 0 |
| Sat 00 | 0 | 0.0 | 171 ms | 0 |
| Sat 02 | 0 | 0.0 | 137 ms | 0 |
Reliability
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 9 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live awork.com 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 awork.com yet. Outages of 10 minutes or more get their own page here.
Having trouble with awork.com?
One report per service every 10 minutes from this network. No account.
Follow awork.com
Get an email when awork.com goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send awork.com alerts to Slack, Discord or a webhook — free.
About awork.com
We track awork.com (awork.com) as part of the AI group. The AI platform for agencies: every feature your agency needs, AI powered by real project context instead of separate licences, plus agent templates.
awork.com publishes an official status page at status.awork.com; 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 167 ms average, 74–249 ms range across 16 successful checks.
Questions
Is awork.com down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was awork.com last down?
We have not recorded a public awork.com incident since monitoring began 9 days ago.
What is awork.com's uptime?
From our own checks: 100% over 9 days of checks.
How fast does awork.com respond?
167 ms on average over the last 24 hours (74–249 ms).
Does awork.com have an official status page?
Yes, at https://status.awork.com.
awork.com 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 awork.com here at once, the problem is on awork.com'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 awork.com. 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.