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 8 min ago. Last stored result reached it in 124 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 05 | 0 | 0.0 | 400 ms | 0 |
| Tue 07 | 0 | 0.0 | 181 ms | 0 |
| Tue 09 | 0 | 0.0 | 301 ms | 0 |
| Tue 11 | 0 | 0.0 | 311 ms | 0 |
| Tue 13 | 0 | 0.0 | 304 ms | 0 |
| Tue 15 | 0 | 0.0 | 181 ms | 0 |
| Tue 18 | 0 | 0.0 | 140 ms | 0 |
| Tue 20 | 0 | 0.0 | 178 ms | 0 |
| Tue 22 | 0 | 0.0 | 216 ms | 0 |
| Wed 00 | 0 | 0.0 | 173 ms | 0 |
| Wed 03 | 0 | 0.0 | 414 ms | 0 |
| Wed 05 | 0 | 0.0 | 261 ms | 0 |
| Wed 07 | 0 | 0.0 | 192 ms | 0 |
| Wed 09 | 0 | 0.0 | 308 ms | 0 |
| Wed 10 | 0 | 0.0 | 276 ms | 0 |
| Wed 12 | 0 | 0.0 | 365 ms | 0 |
| Wed 14 | 0 | 0.0 | 150 ms | 0 |
| Wed 16 | 0 | 0.0 | 232 ms | 0 |
| Wed 18 | 0 | 0.0 | 154 ms | 0 |
| Wed 20 | 0 | 0.0 | 203 ms | 0 |
| Wed 23 | 0 | 0.0 | 182 ms | 0 |
| Thu 01 | 0 | 0.0 | 211 ms | 0 |
| Thu 03 | 0 | 0.0 | 187 ms | 0 |
| Thu 05 | 0 | 0.0 | 178 ms | 0 |
| Thu 07 | 0 | 0.0 | 474 ms | 0 |
| Thu 09 | 0 | 0.0 | 195 ms | 0 |
| Thu 11 | 0 | 0.0 | 355 ms | 0 |
| Thu 13 | 0 | 0.0 | 119 ms | 0 |
| Thu 15 | 0 | 0.0 | 202 ms | 0 |
| Thu 17 | 0 | 0.0 | 169 ms | 0 |
| Thu 19 | 0 | 0.0 | 225 ms | 0 |
| Thu 21 | 0 | 0.0 | 179 ms | 0 |
| Thu 23 | 0 | 0.0 | 184 ms | 0 |
| Fri 02 | 0 | 0.0 | 337 ms | 0 |
| Fri 04 | 0 | 0.0 | 132 ms | 0 |
| Fri 06 | 0 | 0.0 | 125 ms | 0 |
| Fri 08 | 0 | 0.0 | 183 ms | 0 |
| Fri 10 | 0 | 0.0 | 281 ms | 0 |
| Fri 11 | 0 | 0.0 | 279 ms | 0 |
| Fri 13 | 0 | 0.0 | 138 ms | 0 |
| Fri 15 | 0 | 0.0 | 206 ms | 0 |
| Fri 17 | 0 | 0.0 | 296 ms | 0 |
| Fri 18 | 0 | 0.0 | 207 ms | 0 |
| Fri 19 | 0 | 0.0 | 178 ms | 0 |
| Fri 21 | 0 | 0.0 | 197 ms | 0 |
| Fri 22 | 0 | 0.0 | 315 ms | 0 |
| Sat 00 | 0 | 0.0 | 120 ms | 0 |
| Sat 02 | 0 | 0.0 | 124 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for YCharts 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 YCharts goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send YCharts alerts to Slack, Discord or a webhook — free.
YCharts, at ycharts.com, is one of the AI services we monitor. YCharts.com is the premier web based financial research and analysis platform for asset managers and advisors. Build custom Model Portfolios and generate proposals for client communications.
YCharts publishes an official status page at status.ycharts.com; 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 199 ms average, 120–315 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public YCharts incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
199 ms on average over the last 24 hours (120–315 ms).
Yes, at https://status.ycharts.com.
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 YCharts here at once, the problem is on YCharts'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 YCharts. 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.