Live / Treasure AI / Incident
Treasure AI: [Tokyo Region] Treasure AI Voice - Recordings fail to transfer from the mobile app
Treasure AI · treasuredata.comMajor incidentResolved2026-10-07 05:24 UTC
Public — what happened
Summary
Treasure AI said that users of its Treasure AI Voice mobile app in the Tokyo region were unable to send new recordings from their devices starting around 22:55 UTC on October 6, with transfers over both Wi-Fi and Bluetooth stopping on an "Unauthorized" error. The company said recordings already uploaded, along with their transcripts and summaries, were unaffected. By 04:21 UTC on October 7 it said it had found the cause, though it did not describe it, and at 04:54 UTC it reported a fix on its servers that got transfers working again without any app update. Treasure AI said recordings that failed could be sent again from the device, and it marked the incident resolved at 05:24.
Affected
Treasure AI Voice
Timeline
- Started — 2026-10-07 04:21 UTC
- Identified — 2026-10-07 04:21 UTC (2 updates)
- Monitoring — 2026-10-07 04:54 UTC
- Resolved — 2026-10-07 05:24 UTC · 1h 04m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Treasure AI against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Treasure AI: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Treasure AI report →
More from Treasure AI
Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.