DownForAI

in3D status: API, auth, latency & outage reports

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

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

DownForAI monitors in3D via a single endpoint — in3D Web. Current status: operational — all surfaces are responding normally. Measured uptime over the last 24 hours: 100.0%. Median response time (24 h): 450 ms; p95: 745 ms.

DownForAI has not recorded any in3D 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 37 min ago · 1 monitored surface · 1 with 24 h latency data

Current Status

Operational
Everything works normally
Checked by our probes · 641ms
Verified 37m ago
No major incident reported
No reports in the last 24h

Having issues?

Help other users by reporting if in3D is not working for you.

0reports in the last 24 hours

Surface Health

in3D WebOperational
HTTP 200p50 450ms37m ago

Uptime — last 24h

100.0%

Network latency — last 20 probes

Loading…

What DownForAI can verify about in3D

No confirmed provider-side issue detected
DownForAI currently sees in3D 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 in3D in the last 24 hours.

Known error signatures

Common failure patterns and how to diagnose them

Provider details

in3D creates full-body 3D avatars from phone scans through its iOS app and an SDK for apps, on free and developer plans. Scans are processed in the cloud; failures are processing stuck and SDK calls failing.

What we monitor
in3D appScanning
Processing backendScan to avatar
SDK / APIDeveloper integration
Ecosystem dependencies
Apple App Store

Fallback alternatives

What to use if this service is down

in3D is down
Avaturn (monitored on DownForAI) builds avatars from a selfie
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.

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

Community Discussion

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

Still having issues with in3D?

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