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 92 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 11 | 0 | 0.0 | 114 ms | 0 |
| Tue 13 | 0 | 0.0 | 280 ms | 0 |
| Tue 15 | 0 | 0.0 | 233 ms | 0 |
| Tue 18 | 0 | 0.0 | 107 ms | 0 |
| Tue 20 | 0 | 0.0 | 110 ms | 0 |
| Tue 22 | 0 | 0.0 | 293 ms | 0 |
| Wed 00 | 0 | 0.0 | 241 ms | 0 |
| Wed 03 | 0 | 0.0 | 266 ms | 0 |
| Wed 05 | 0 | 0.0 | 179 ms | 0 |
| Wed 07 | 0 | 0.0 | 144 ms | 0 |
| Wed 09 | 0 | 0.0 | 158 ms | 0 |
| Wed 12 | 0 | 0.0 | 77 ms | 0 |
| Wed 14 | 0 | 0.0 | 85 ms | 0 |
| Wed 16 | 0 | 0.0 | 85 ms | 0 |
| Wed 18 | 0 | 0.0 | 156 ms | 0 |
| Wed 20 | 0 | 0.0 | 117 ms | 0 |
| Wed 22 | 0 | 0.0 | 112 ms | 0 |
| Thu 00 | 0 | 0.0 | 137 ms | 0 |
| Thu 03 | 0 | 0.0 | 121 ms | 0 |
| Thu 05 | 0 | 0.0 | 137 ms | 0 |
| Thu 07 | 0 | 0.0 | 91 ms | 0 |
| Thu 09 | 0 | 0.0 | 132 ms | 0 |
| Thu 11 | 0 | 0.0 | 64 ms | 0 |
| Thu 13 | 0 | 0.0 | 151 ms | 0 |
| Thu 15 | 0 | 0.0 | 274 ms | 0 |
| Thu 17 | 0 | 0.0 | 454 ms | 0 |
| Thu 19 | 0 | 0.0 | 136 ms | 0 |
| Thu 21 | 0 | 0.0 | 144 ms | 0 |
| Thu 23 | 0 | 0.0 | 216 ms | 0 |
| Fri 01 | 0 | 0.0 | 140 ms | 0 |
| Fri 03 | 0 | 0.0 | 84 ms | 0 |
| Fri 05 | 0 | 0.0 | 109 ms | 0 |
| Fri 07 | 0 | 0.0 | 81 ms | 0 |
| Fri 09 | 0 | 0.0 | 207 ms | 0 |
| Fri 11 | 0 | 0.0 | 79 ms | 0 |
| Fri 13 | 0 | 0.0 | 93 ms | 0 |
| Fri 15 | 0 | 0.0 | 81 ms | 0 |
| Fri 17 | 0 | 0.0 | 152 ms | 0 |
| Fri 18 | 0 | 0.0 | 196 ms | 0 |
| Fri 19 | 0 | 0.0 | 94 ms | 0 |
| Fri 20 | 0 | 0.0 | 99 ms | 0 |
| Fri 22 | 0 | 0.0 | 100 ms | 0 |
| Sat 00 | 0 | 0.0 | 272 ms | 0 |
| Sat 02 | 0 | 0.0 | 73 ms | 0 |
| Sat 04 | 0 | 0.0 | 160 ms | 0 |
| Sat 05 | 0 | 0.0 | 110 ms | 0 |
| Sat 07 | 0 | 0.0 | 93 ms | 0 |
| Sat 09 | 0 | 0.0 | 92 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for MyArchitectAI 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 MyArchitectAI goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send MyArchitectAI alerts to Slack, Discord or a webhook — free.
MyArchitectAI is listed in our AI category and checked at myarchitectai.com. Create photorealistic AI renders in under 10 seconds. Upload your Sketchup or Archicad designs and our AI rendering tool will do the rest. Get 10 renders free.
MyArchitectAI publishes an official status page at status.myarchitectai.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 124 ms average, 73–272 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 MyArchitectAI incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
124 ms on average over the last 24 hours (73–272 ms).
Yes, at https://status.myarchitectai.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 MyArchitectAI here at once, the problem is on MyArchitectAI'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 MyArchitectAI. 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.