DownForAI

Shap-E status: API, auth, latency & outage reports

Shap-E is operational right now. DownForAI checks Shap-E every ~75 minutes across 1 monitored surface, with 0 community reports in the last 24 hours.

Operational
Last probe 51 min ago·1 surface
Probe-monitoredLow confidence
📚 Docs →
100.0%
24h Uptime
385ms
p50 Network Latencyⓘ
472ms
p95 Network Latencyⓘ
0
Incidents (30d)

DownForAI monitors Shap-E via a single endpoint — Shap-E. Current status: operational — all surfaces are responding normally. Measured uptime over the last 24 hours: 100.0%. Median response time (24 h): 385 ms; p95: 472 ms.

DownForAI has not recorded any Shap-E 3D generation disruptions. The service is probed approximately every 75 minutes; no user reports have been received in the last 24 hours.

Data confidence: LowLast checked 51 min ago · 1 monitored surface · 1 with 24 h latency data

Current Status

✅
Operational
Everything works normally
✓Checked by our probes · 391ms
Verified 50m ago
✓No major incident reported
ⓘNo reports in the last 24h

Having issues?

Help other users by reporting if Shap-E is not working for you.

0reports in the last 24 hours

Surface Health

Shap-EOperational
HTTP 200p50 385ms50m ago

Uptime — last 24h

100.0%

Network latency — last 20 probes

Loading…

What DownForAI can verify about Shap-E

No confirmed provider-side issue detected
DownForAI currently sees Shap-E as operational based on available monitoring signals.
Signal source: public surface check · Monitoring confidence: Low
Still having trouble?

The issue may be account-specific, regional, network-related, or related to authentication, billing, quota, or rate limits.

Incident history (30d)

✓No incidents recorded in the past 30 days.

Reported symptoms

No user reports for Shap-E in the last 24 hours.

Known error signatures

Common failure patterns and how to diagnose them

Provider details

Shap-E is OpenAI's open-source conditional 3D generation model (implicit functions), published as code and weights on GitHub with no hosted service. Availability concerns the repository only.

What we monitor
github.com/openai/shap-e — Repository
Ecosystem dependencies
GitHubOpenAI checkpoint storage
Operator notes
  • Research code, not a service: DownForAI monitors the GitHub page only.

Fallback alternatives

What to use if this service is down

You need hosted text-to-3D
Meshy or Tripo AI (monitored on DownForAI)
Moderate effort

How we monitor

DownForAI checks monitored AI service surfaces on a rotating schedule, roughly every 75 minutes per surface, from a single centralized probe infrastructure. For services with an official machine-readable status page, we use that official status signal when available. For other services, we perform a basic public-surface check. Some services block datacenter probes; in those cases we mark them as “Monitoring limited” instead of treating a failed probe as a confirmed outage. Status is classified as Operational, Degraded, or Outage. Network latency (check response time) measures how long the monitored endpoint took to respond to our probe — it is not model inference speed, time-to-first-token, or tokens-per-second performance. We are independent of all providers listed and receive no compensation to report any particular status.

Shap-E statusEmbed this status badgeREADME · docs ▾
Markdown
[![Shap-E status](https://downforai.com/api/badge/shap-e.svg)](https://downforai.com/shap-e)
HTML
<a href="https://downforai.com/shap-e"><img src="https://downforai.com/api/badge/shap-e.svg" alt="Shap-E status" /></a>

Community Discussion

0/1000
No comments yet. Be the first to share your experience!

Still having issues with Shap-E?

Let the community know and help others experiencing the same problem.