Skip to main content

Is Meshy Down?

No — Meshy is up
Meshy's status page
Not available · we could not read it
FlareWarden checks
Website reachable · 8 of 8 regions · 799 ms

Right now

We could not read Meshy's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

meshy.ai from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
799 ms
Checked

By region

  • Amsterdam reachable, 1010 ms
  • Dallas reachable, 485 ms
  • Newark reachable, 630 ms
  • Paris reachable, 969 ms
  • San Jose reachable, 304 ms
  • Stockholm reachable, 1104 ms
  • Sydney reachable, 1195 ms
  • Toronto reachable, 699 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Amsterdam146 ms5 ms273 ms596 ms
Dallas224 ms1 ms76 ms365 ms
Newark207 ms1 ms125 ms427 ms
Paris120 ms9 ms266 ms560 ms
San Jose156 ms1 ms39 ms242 ms
Stockholm168 ms1 ms303 ms643 ms
Sydney282 ms0 ms280 ms727 ms
Toronto290 ms16 ms112 ms514 ms
We check that meshy.ai loads, not every feature behind it. Test it yourself

History

Meshy website availability

Measured by FlareWarden · meshy.ai

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

Last 30 days

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

Measured by FlareWarden's own checks of meshy.ai from multiple regions every 6 hours. Meshy's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 83 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 up to 17 cities across three 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 — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • 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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Meshy itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when Meshy goes down

We check Meshy every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required