Treasure AI Outage History

43 incidents recorded over the last 365 days, 17 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded Treasure AI Incident

Treasure AI incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 20, 2026[EU Region] Database MaintenanceOn Friday, November 20 from 01:00 to 03:00 UTC, we will perform routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to databases used by…2h 0mScheduled
Nov 19, 2026[AP03 Region] Database MaintenanceOn Thursday, November 19 from 01:00 to 03:00 UTC, we will perform routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to databases used…2h 0mScheduled
Nov 18, 2026[Tokyo Region] Database MaintenanceOn Wednesday, November 18 from 01:00 to 03:00 UTC, we will perform routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to databases used…2h 0mScheduled
Nov 17, 2026[US Region] Database MaintenanceOn Tuesday, November 17 from 01:00 to 03:00 UTC, we will perform routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to databases used by…2h 0mScheduled
Nov 16, 2026[Korea Region] Database MaintenanceOn Monday, November 16 from 01:00 to 03:00 UTC, we will perform routine maintenance on the databases that power the Treasure AI Platform. During this maintenance, we will apply patches and updates to databases used by…2h 0mScheduled
Oct 22, 2026[US Region][Tokyo Region][EU Region][AP03 Region] Data Connector Integrations - Date columns from S3 Parquet imports loaded as textThe issue causing Amazon S3 Parquet imports to load date and time columns as text (string) instead of numbers (long) has been resolved. A fix was deployed on October 22, 2026 at 07:40 UTC, and new import jobs load these…6h 51mResolved
Oct 7, 2026[Tokyo Region] Treasure AI Voice - Recordings fail to transfer from the mobile appThe recording transfer failures in Treasure AI Voice have been resolved. All systems are operating normally. Between approximately 22:55 UTC on October 6 and [fix time] UTC on October 7, new recordings could not be…1h 3mResolved
Oct 1, 2026[All Regions] Engage Studio (Email): Planned maintenance for the Email Delivery Events TableThe maintenance and validations are completed. Email campaigns, sending and delivery were not affected, and all other channels remain operation.4h 0mScheduled
Sep 30, 2026[EU01 Tokyo AP03 Regions] Batch Data Load failure for RT2.0Between Sept 28th (5:30 PM UTC) and Sept 29th (6:30 PM UTC) customers with no batch segments who had scheduled attribute updates would have seen failed jobs preventing batch data from loading into Reactor. Customers…0 minResolved
Sep 29, 2026[US Region] Batch Data Load failure for RT2.0This incident has been resolved, and our support team will be following up with affected customers.3h 56mResolved
Sep 28, 2026[All Regions] Live Chat Service UnavailableWe have identified and resolved the issue affecting the Live Chat feature for Corporate and Enterprise support plans. The service has been fully restored and is operating normally. We sincerely apologize for any…9h 35mResolved
Sep 17, 2026[All Regions] Transactional email delivery delaysWe are no longer observing any delivery delays. We have enhanced our monitoring and will continue to watch for disruptions. If you notice any sluggish delivery, please contact our support team for assistance.692h 49mResolved
Sep 3, 2026[AP03 Region] Database MaintenanceThe database maintenance has been completed. All systems are operating normally.2h 0mScheduled
Sep 2, 2026[EU Region] Database MaintenanceThe database maintenance has been completed. All systems are operating normally.2h 0mScheduled
Aug 31, 2026[Tokyo Region] Database MaintenanceThe database maintenance has been completed. All systems are operating normally.2h 0mScheduled
Aug 27, 2026[US Region] Database MaintenanceThe database maintenance has been completed. All systems are operating normally.2h 0mScheduled
Aug 25, 2026[Korea Region] Database MaintenanceThe database maintenance has been completed. All systems are operating normally.2h 0mScheduled
Jul 27, 2026[Tokyo, Ap03 and US Regions] Performance degradation with Bulk Load, Bulk Import and Result Export jobsBetween 7/25 and today, 7/27 at 11:30 AM JST, we experienced a performance degradation issue affecting BulkLoad (Data Connector Import), Result Export (Activation) and Bulk Import. Following reports received this…0 minResolved
Jul 7, 2026[Tokyo Region] - Treasure Work / tdx claude - Degraded PerformanceThis issue has been resolved. Treasure Work and tdx are operating normally, and the Claude Haiku 4.5 model in the Tokyo region is no longer experiencing errors or timeouts. Thank you for your patience.3h 54mResolved
Jun 26, 2026[US Region] - Hive - Query Performance DegradationHive query performance degradation in the US region has been resolved. We have successfully provisioned a new cluster and routed all traffic to it. Systems are now operating normally. Thank you for your patience.3h 24mResolved
Jun 25, 2026[US Region][Tokyo Region][EU Region] - Result/Data Export Job FailuresResolved — Some result export (data export) jobs in the US, Tokyo, and EU regions may have failed or been delayed between June 24, 2026 21:00 UTC and June 25, 2026 05:26 UTC. During this period, underlying compute…0 minResolved
Jun 24, 2026[US Region] - Delay in Email Event Data RecordingWe identified a delay in recording email event data (such as open, click, bounce, delivery events, and error events) to customer event tables. Affected period (approximate): - June 22, 03:45 UTC – June 23, 04:15 UTC -…0 minResolved
May 5, 2026Realtime 2.0 Bulk Storage OutageWe have applied the fix, and are observing that traffic is flowing correctly now.1h 23mResolved
Apr 27, 2026Intermittent 5xx Errors for Ingest and Real-Time APIs (EU01)The upstream provider has restored service.53 minResolved
Apr 15, 2026[EU Region] Scheduled CDP Database MaintenanceThe database maintenance has been completed. All systems are operating normally.1h 0mScheduled
Mar 4, 2026[AP03 Region] Database MaintenanceThe database maintenance has been completed. All systems are operating normally.2h 0mScheduled
Mar 3, 2026[EU Region] Database MaintenanceThe database maintenance has been completed. All systems are operating normally.2h 0mScheduled
Feb 26, 2026[Tokyo Region] Database MaintenanceThe database maintenance has been completed. All systems are operating normally.2h 0mScheduled
Feb 25, 2026[US Region] Database MaintenanceThe scheduled database maintenance is now complete, and all systems have been successfully validated. Services are fully operational, and no further impact is expected. If you encounter any issues, please reach out to…2h 0mScheduled
Feb 24, 2026[Korea Region] Database MaintenanceThe database maintenance has been completed. All systems are operating normally.2h 0mScheduled
Feb 18, 2026US region: Treasure Insights unavailableThis incident has been resolved.1h 15mResolved
Jan 21, 2026[US/Tokyo Region] Performance issues## Post-Mortem Summary This incident was related to a database maintenance performed on January 19, during which management of Plazma table resources was migrated from the existing RDBMS to a dedicated Aurora database…2h 11mResolved
Jan 21, 2026[AP03 Region] Database MaintenanceThe scheduled database maintenance is now complete, and all systems have been successfully validated. Services are fully operational, and no further impact is expected. If you encounter any issues, please reach out to…40 minScheduled
Jan 21, 2026[EU Region] Database MaintenanceThe scheduled database maintenance is now complete, and all systems have been successfully validated. Services are fully operational, and no further impact is expected. If you encounter any issues, please reach out to…40 minScheduled
Jan 20, 2026[Tokyo Region] Database MaintenanceThe scheduled database maintenance is now complete, and all systems have been successfully validated. Services are fully operational, and no further impact is expected. If you encounter any issues, please reach out to…40 minScheduled
Jan 20, 2026[US Region] Database MaintenanceThe scheduled database maintenance is now complete, and all systems have been successfully validated. Services are fully operational, and no further impact is expected. If you encounter any issues, please reach out to…40 minScheduled
Jan 19, 2026[Korea Region] Database MaintenanceThe scheduled database maintenance is now complete, and all systems have been successfully validated. Services are fully operational, and no further impact is expected. If you encounter any issues, please reach out to…40 minScheduled
Jan 5, 2026[US/Tokyo/EU] Realtime 2.0 Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Dec 10, 2025[All Regions] REST API sometimes returns only partial job resultAn unexpected behavior occurred in the REST API "GET /v3/job/result/{job_id}" which caused it to return only a partial set of results. This issue stemmed from an update to the job result download mechanism implemented…0 minResolved
Dec 5, 2025[All Region] Service Disruption on Treasure InsightsWe confirmed the third-party service is now operational. The incident has been resolved.12 minResolved
Dec 3, 2025[All Regions] Database maintenance for AI Agent FoundryThe scheduled maintenance has been completed.3h 0mScheduled
Nov 25, 2025[All Regions] PrecisionML Database MaintenanceThe scheduled maintenance has been finished, with upgrades to all sites finished.1h 0mScheduled
Nov 18, 2025[Tokyo/AP03 Regions] DataTank 2.0 maintenanceThe scheduled maintenance has been completed.3h 0mScheduled

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Treasure AI incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Treasure AI Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Treasure AI acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Treasure AI outage in this window ran 28d 20h, against a mean recovery of 17h 60m. If you depend on Treasure AI in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.