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 344 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 10 | 0 | 0.0 | 87 ms | 0 |
| Tue 12 | 0 | 0.0 | 105 ms | 0 |
| Tue 15 | 0 | 0.0 | 144 ms | 0 |
| Tue 17 | 0 | 0.0 | 531 ms | 0 |
| Tue 19 | 0 | 0.0 | 82 ms | 0 |
| Tue 22 | 0 | 0.0 | 152 ms | 0 |
| Wed 00 | 0 | 0.0 | 301 ms | 0 |
| Wed 02 | 0 | 0.0 | 509 ms | 0 |
| Wed 04 | 0 | 0.0 | 439 ms | 0 |
| Wed 06 | 0 | 0.0 | 128 ms | 0 |
| Wed 09 | 0 | 0.0 | 173 ms | 0 |
| Wed 11 | 0 | 0.0 | 85 ms | 0 |
| Wed 13 | 0 | 0.0 | 196 ms | 0 |
| Wed 15 | 0 | 0.0 | 136 ms | 0 |
| Wed 17 | 0 | 0.0 | 231 ms | 0 |
| Wed 20 | 0 | 0.0 | 144 ms | 0 |
| Wed 22 | 0 | 0.0 | 107 ms | 0 |
| Thu 00 | 0 | 0.0 | 260 ms | 0 |
| Thu 02 | 0 | 0.0 | 139 ms | 0 |
| Thu 04 | 0 | 0.0 | 132 ms | 0 |
| Thu 06 | 0 | 0.0 | 165 ms | 0 |
| Thu 08 | 0 | 0.0 | 232 ms | 0 |
| Thu 10 | 0 | 0.0 | 252 ms | 0 |
| Thu 12 | 0 | 0.0 | 99 ms | 0 |
| Thu 14 | 0 | 0.0 | 158 ms | 0 |
| Thu 17 | 0 | 0.0 | 226 ms | 0 |
| Thu 19 | 0 | 0.0 | 103 ms | 0 |
| Thu 21 | 0 | 0.0 | 297 ms | 0 |
| Thu 23 | 0 | 0.0 | 102 ms | 0 |
| Fri 01 | 0 | 0.0 | 142 ms | 0 |
| Fri 02 | 0 | 0.0 | 292 ms | 0 |
| Fri 04 | 0 | 0.0 | 380 ms | 0 |
| Fri 06 | 0 | 0.0 | 176 ms | 0 |
| Fri 08 | 0 | 0.0 | 262 ms | 0 |
| Fri 10 | 0 | 0.0 | 123 ms | 0 |
| Fri 12 | 0 | 0.0 | 129 ms | 0 |
| Fri 15 | 0 | 0.0 | 313 ms | 0 |
| Fri 17 | 0 | 0.0 | 117 ms | 0 |
| Fri 18 | 0 | 0.0 | 117 ms | 0 |
| Fri 19 | 0 | 0.0 | 128 ms | 0 |
| Fri 21 | 0 | 0.0 | 127 ms | 0 |
| Fri 23 | 0 | 0.0 | 654 ms | 0 |
| Sat 01 | 0 | 0.0 | 73 ms | 0 |
| Sat 02 | 0 | 0.0 | 137 ms | 0 |
| Sat 04 | 0 | 0.0 | 73 ms | 0 |
| Sat 05 | 0 | 0.0 | 119 ms | 0 |
| Sat 07 | 0 | 0.0 | 170 ms | 0 |
| Sat 10 | 0 | 0.0 | 344 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 Ryze AI 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 Ryze AI goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Ryze AI alerts to Slack, Discord or a webhook — free.
We track Ryze AI (get-ryze.ai) as part of the AI group. AI copilot for performance marketers. Ryze AI manages ads across Google, Meta, ChatGPT, TikTok, LinkedIn, Microsoft and more. Our AI for marketing reviews your ad data, suggests changes, generates new creatives, and helps you find wasted spend, fix structure, and scale winning campaigns.
Ryze AI publishes an official status page at status.get-ryze.ai; 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: 186 ms average, 73–654 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 Ryze AI incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
186 ms on average over the last 24 hours (73–654 ms).
Yes, at https://status.get-ryze.ai.
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 Ryze AI here at once, the problem is on Ryze AI'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 Ryze AI. 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.