User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 936 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 7 | 0 | 0.0 | 659 ms | 0 |
| Nov 7 | 0 | 0.0 | 650 ms | 0 |
| Nov 8 | 0 | 0.0 | 1093 ms | 0 |
| Nov 8 | 0 | 0.0 | 711 ms | 0 |
| Nov 8 | 0 | 0.0 | 606 ms | 0 |
| Nov 8 | 0 | 0.0 | 1498 ms | 0 |
| Nov 9 | 0 | 0.0 | 593 ms | 0 |
| Nov 9 | 0 | 0.0 | 628 ms | 0 |
| Nov 9 | 0 | 0.0 | 622 ms | 0 |
| Nov 9 | 0 | 0.0 | 622 ms | 0 |
| Nov 10 | 0 | 0.0 | 905 ms | 0 |
| Nov 10 | 0 | 0.0 | 518 ms | 0 |
| Nov 10 | 0 | 0.0 | 596 ms | 0 |
| Nov 10 | 0 | 0.0 | 858 ms | 0 |
| Nov 11 | 0 | 0.0 | 1062 ms | 0 |
| Nov 11 | 0 | 0.0 | 1119 ms | 0 |
| Nov 11 | 0 | 0.0 | 603 ms | 0 |
| Nov 11 | 0 | 0.0 | 732 ms | 0 |
| Nov 12 | 0 | 0.0 | 450 ms | 0 |
| Nov 12 | 0 | 0.0 | 1000 ms | 0 |
| Nov 12 | 0 | 0.0 | 645 ms | 0 |
| Nov 12 | 0 | 0.0 | 1126 ms | 0 |
| Nov 13 | 0 | 0.0 | 469 ms | 0 |
| Nov 13 | 0 | 0.0 | 816 ms | 0 |
| Nov 13 | 0 | 0.0 | 511 ms | 0 |
| Nov 13 | 0 | 0.0 | 821 ms | 0 |
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.
No outages on record for ShareAI yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when ShareAI goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send ShareAI alerts to Slack, Discord or a webhook — free.
ShareAI, at shareai.now, is one of the AI services we monitor. One API to 150+ AI models across many providers. Auto-routing and failover for speed and uptime. Pay per token; 70% goes to the GPUs serving requests.
ShareAI publishes an official status page at status.shareai.now; 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: 713 ms average, 459–1064 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public ShareAI incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
713 ms on average over the last 24 hours (459–1064 ms).
Yes, at https://status.shareai.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 ShareAI here at once, the problem is on ShareAI'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 ShareAI. 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.