boost ai Incident History

1. resolvedAug 11 · 12:30 UTC

   On 11 August 2026, from 14:30 to 19:50 CEST, a subset of virtual agent instances experienced degraded performance on conversations processed via the OpenAI (via boost.ai) vendor configuration, caused by elevated latency on the upstream provider's models. During this window, affected conversations experienced extended processing times and a elevated number of timeouts or errors. Provider latency returned to normal at 19:50 CEST, after which all affected instances were stable. Total duration of degraded performance: 5 hours 20 minutes. Note: this incident entry was published retroactively on the 20th of August as part of our commitment to a complete and accurate public service record.

Reported by boost ai on their status page.

1. resolvedAug 6 · 13:30 UTC

   On 6 August 2026, from 15:28 to 18:53 CEST, a subset of virtual agent instances experienced degraded performance on conversations processed via the OpenAI (via boost.ai) vendor configuration, caused by elevated latency on the upstream provider's models. During this window, affected conversations experienced extended processing times and a elevated number of timeouts or errors. Provider latency returned to normal at 18:53 CEST, after which all affected instances were stable. Total duration of degraded performance: approximately 3 hours 25 minutes. Note: this incident entry was published retroactively on the 20th of August as part of our commitment to a complete and accurate public service record.

Reported by boost ai on their status page.

1. resolvedJul 28 · 11:00 UTC

   On 28 July 2026, from 13:03 to 19:50 CEST, a subset of virtual agent instances experienced degraded performance on conversations processed via the OpenAI (via boost.ai) vendor configuration, caused by elevated latency on the upstream provider's models. During this window, affected conversations experienced extended processing times and a elevated number of timeouts or errors. Provider latency returned to normal at 19:50 CEST, after which all affected instances were stable. Total duration of degraded performance: approximately 6 hours 47 minutes. Note: this incident entry was published retroactively on the 20th of August as part of our commitment to a complete and accurate public service record.

Reported by boost ai on their status page.