DownForAI

Polycam status: API, auth, latency & outage reports

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

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

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

Polycam has had no tracked outages since joining the DownForAI monitoring network. No community reports have been filed in the last 24 hours.

Data confidence: LowLast checked 2h 37m ago · 1 monitored surface · 1 with 24 h latency data

Current Status

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

Having issues?

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

0reports in the last 24 hours

Surface Health

Polycam WebOperational
HTTP 200p50 311ms2h ago

Uptime — last 24h

100.0%

Network latency — last 20 probes

Loading…

What DownForAI can verify about Polycam

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

Known error signatures

Common failure patterns and how to diagnose them

Provider details

Polycam captures objects and spaces as 3D models with LiDAR, photogrammetry and Gaussian splats on iOS, Android and the web, with cloud processing for photo captures, on freemium plans. Incidents are cloud processing stuck and sign-in or sync failures.

What we monitor
Polycam apps and webCapture and library
Cloud processingPhotogrammetry and splats
Sync and sharingLibrary and public links
Ecosystem dependencies
App stores
Operator notes
  • learn.poly.cam refuses automated requests (403) but is Polycam's help centre.

Fallback alternatives

What to use if this service is down

Polycam is down
Luma Genie (monitored on DownForAI) sits alongside Luma's capture tools; LiDAR scans keep working on-device
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.

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

Community Discussion

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

Still having issues with Polycam?

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