Is Boost AI down?
Last checked 5h agoNo incidents right now.
Boost AI is operational right now. Last checked 5h ago; the most recent incident resolved 22d ago.
Real-time Boost AI status, recent outages, and incident history: pulled directly from Boost AI's official status page at status.boost.ai every 5 minutes. Pingoru tracks 6 Boost AI services and has captured 4 incidents in the last 90 days (99.81% uptime). Get email, Slack, Discord, or webhook alerts the moment Boost AI reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- Boost.ai Provided LLM
Timeline · 3 updates
- investigating · Sep 30, 2026, 04:52 PM UTC
We are currently observing increased processing times for requests to the OpenAI model text-embedding-3-large in the US region. Requests may consequently take longer than usual. Our team is investigating the cause. We will provide an update as soon as more information is available.
- monitoring · Sep 30, 2026, 06:05 PM UTC
We are currently seeing improvements and increased stability across affected environments following the earlier disruption impacting the OpenAI model. Processing times have returned toward normal levels, and most requests are now processing with normal processing time. We are continuing to closely monitor system performance.
- resolved · Sep 30, 2026, 08:25 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
-
Timeline · 1 update
- resolved · Aug 20, 2026, 09:48 AM 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.
Latest: 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 co…
-
-
Timeline · 1 update
- resolved · Aug 20, 2026, 09:42 AM 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.
Latest: 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 con…
-
-
Timeline · 1 update
- resolved · Aug 20, 2026, 09:36 AM 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.
Latest: 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 conf…
-
Incident record
Since October 2026 · Statuspage by Atlassian · 6 components checked every 5 minutesThe longest incident in the last year, Performance degradation of Azure OpenAI model for Few-Shot and Out-of-Scope Detection on April 15, 2026, ran for 10 hours.
Most affected components, last 12 months
- Boost.ai Provided LLM5
Latest incidents
- Increased processing time of OpenAI model text-embedding-3-large in US region
We are currently observing increased processing times for requests to the OpenAI model text-embedding-3-large in the US region. Requests may consequently take…
- Performance degradation of OpenAI models
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…
- Performance degradation of OpenAI models
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…
- Started Sep 30, 2026, 04:52 PM UTC · Resolved Sep 30, 2026, 08:25 PM UTC · 3h 33m
- Started Aug 11, 2026, 12:30 PM UTC · Resolved Aug 11, 2026, 05:50 PM UTC · 5h 20m
- Started Aug 06, 2026, 01:28 PM UTC · Resolved Aug 06, 2026, 04:53 PM UTC · 3h 25m
- Started Jul 28, 2026, 11:03 AM UTC · Resolved Jul 28, 2026, 05:50 PM UTC · 6h 47m