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 16 min ago. Last stored result reached it in 123 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 164 ms | 0 |
| Mon 19 | 0 | 0.0 | 112 ms | 0 |
| Mon 21 | 0 | 0.0 | 237 ms | 0 |
| Tue 00 | 0 | 0.0 | 142 ms | 0 |
| Tue 02 | 0 | 0.0 | 183 ms | 0 |
| Tue 04 | 0 | 0.0 | 169 ms | 0 |
| Tue 06 | 0 | 0.0 | 125 ms | 0 |
| Tue 08 | 0 | 0.0 | 81 ms | 0 |
| Tue 10 | 0 | 0.0 | 242 ms | 0 |
| Tue 12 | 0 | 0.0 | 120 ms | 0 |
| Tue 15 | 0 | 0.0 | 190 ms | 0 |
| Tue 17 | 0 | 0.0 | 159 ms | 0 |
| Tue 19 | 0 | 0.0 | 75 ms | 0 |
| Tue 21 | 0 | 0.0 | 137 ms | 0 |
| Wed 00 | 0 | 0.0 | 180 ms | 0 |
| Wed 02 | 0 | 0.0 | 219 ms | 0 |
| Wed 04 | 0 | 0.0 | 189 ms | 0 |
| Wed 06 | 0 | 0.0 | 135 ms | 0 |
| Wed 09 | 0 | 0.0 | 257 ms | 0 |
| Wed 11 | 0 | 0.0 | 188 ms | 0 |
| Wed 13 | 0 | 0.0 | 240 ms | 0 |
| Wed 15 | 0 | 0.0 | 152 ms | 0 |
| Wed 17 | 0 | 0.0 | 218 ms | 0 |
| Wed 20 | 0 | 0.0 | 80 ms | 0 |
| Wed 22 | 0 | 0.0 | 101 ms | 0 |
| Thu 00 | 0 | 0.0 | 255 ms | 0 |
| Thu 02 | 0 | 0.0 | 196 ms | 0 |
| Thu 04 | 0 | 0.0 | 169 ms | 0 |
| Thu 06 | 0 | 0.0 | 141 ms | 0 |
| Thu 08 | 0 | 0.0 | 125 ms | 0 |
| Thu 10 | 0 | 0.0 | 84 ms | 0 |
| Thu 12 | 0 | 0.0 | 143 ms | 0 |
| Thu 14 | 0 | 0.0 | 130 ms | 0 |
| Thu 17 | 0 | 0.0 | 173 ms | 0 |
| Thu 19 | 0 | 0.0 | 130 ms | 0 |
| Thu 21 | 0 | 0.0 | 197 ms | 0 |
| Thu 23 | 0 | 0.0 | 115 ms | 0 |
| Fri 01 | 0 | 0.0 | 114 ms | 0 |
| Fri 03 | 0 | 0.0 | 113 ms | 0 |
| Fri 05 | 0 | 0.0 | 121 ms | 0 |
| Fri 06 | 0 | 0.0 | 178 ms | 0 |
| Fri 08 | 0 | 0.0 | 455 ms | 0 |
| Fri 10 | 0 | 0.0 | 220 ms | 0 |
| Fri 12 | 0 | 0.0 | 121 ms | 0 |
| Fri 14 | 0 | 0.0 | 116 ms | 0 |
| Fri 16 | 0 | 0.0 | 147 ms | 0 |
| Fri 17 | 0 | 0.0 | 136 ms | 0 |
| Fri 18 | 0 | 0.0 | 123 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 Weaverse 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 Weaverse goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Weaverse alerts to Slack, Discord or a webhook — free.
Weaverse, at weaverse.io, is one of the AI services we monitor. The first AI-powered visual page builder designed specifically for Shopify Hydrogen themes. Create lightning-fast headless ecommerce stores with React components, AI automation, and professional design tools. Weaverse: AI Shopify theme builder, not Weverse entertainment platform.
Weaverse publishes an official status page at status.weaverse.io; 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: 164 ms average, 113–455 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Weaverse incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
164 ms on average over the last 24 hours (113–455 ms).
Yes, at https://status.weaverse.io.
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 Weaverse here at once, the problem is on Weaverse'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 Weaverse. 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.