Skip to main content

Is Meshy Down?

No — Meshy is up

Reachable from all 8 checked regions

Average response time: 734ms

Last checked · checks run every 6 hours

Official status page: https://status.meshy.ai

Meshy uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
804ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 16 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

16-day clean streak
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: 100.00% uptime, 32 checks
Aug 4: 100.00% uptime, 32 checks
Aug 5: 100.00% uptime, 32 checks
Aug 6: 100.00% uptime, 32 checks
Aug 7: 100.00% uptime, 40 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 32 checks
Aug 12: 100.00% uptime, 32 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 40 checks
Aug 18: 100.00% uptime, 40 checks
Jul 20 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
820ms
DNS 0ms TCP 1ms TLS 268ms TTFB 418ms
arn
943ms
DNS 0ms TCP 0ms TLS 306ms TTFB 476ms
bom
1410ms
DNS 0ms TCP 2ms TLS 462ms TTFB 713ms
cdg
826ms
DNS 0ms TCP 0ms TLS 269ms TTFB 419ms
dfw
255ms
DNS 0ms TCP 0ms TLS 77ms TTFB 137ms
ewr
379ms
DNS 0ms TCP 0ms TLS 120ms TTFB 197ms
sjc
193ms
DNS 0ms TCP 2ms TLS 39ms TTFB 79ms
syd
863ms
DNS 0ms TCP 1ms TLS 281ms TTFB 441ms
yyz
381ms
DNS 0ms TCP 0ms TLS 120ms TTFB 199ms

What Meshy does

Meshy is an AI tool that generates 3D models from text prompts or images, producing meshes and textures that game developers and 3D artists take into engines and modelling software. Generation runs as a queued job on Meshy's own infrastructure, so an outage stops new work being produced rather than touching assets already exported.

What an outage looks like

Generation jobs are the part that fails: prompts submit but tasks sit queued or return errors while the site itself loads normally. Assets already generated and downloaded are unaffected, since they live in your own files once exported. Meshy reports a single service rather than separate components, so the status page cannot narrow down which stage of the pipeline is failing.

What to do about it

Check status.meshy.ai, which runs on PagerDuty and reports meshy.ai as one service with a seven-day uptime figure and a status history behind it. It offers a subscription for updates. Because it tracks a single component rather than separate site and generation lines, a green page during a stuck job is not conclusive, and the incident history is the more useful half.

Is it down for everyone, or just you?

If this page says Meshy is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Meshy outage FAQ

My Meshy generation is stuck. Is Meshy down?
Not necessarily, and the status page may not settle it. Meshy reports meshy.ai as a single service rather than breaking out the generation queue, so a job that sits pending while the site loads normally will not necessarily register as an incident. Check the status history for anything recent before concluding the job itself has failed.
Are models I already downloaded affected by a Meshy outage?
No. Once a model is generated and exported it is a file on your own machine or storage, and Meshy's availability has no bearing on it. An outage affects producing new models and reaching anything still held in your Meshy library online, not assets you have already brought into an engine or modelling tool.
How much uptime history does Meshy publish?
Seven days on the main view, with a status history behind it. That is a shorter headline window than most vendors show, so a problem from two weeks ago will not appear in the percentage on the front page. The history view is where a recurring pattern would become visible.
How do I get told when Meshy recovers?
The status page offers a subscription for updates, which is the practical option given that it reports a single service and changes infrequently. It runs on PagerDuty's status product, so those notifications come from there rather than from Meshy directly. There are no separate components to subscribe to individually.

How we measure this

  • We request Meshy's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Meshy publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Meshy goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required