Kore.ai Outage History

Kore.ai is up right now

Pingoru has recorded 97 incidents for Kore.ai: 93 in the last 12 months and 26 in the last 90 days.

Source: status.kore.com

97incidents recorded
93last 12 months
26last 90 days
8 hourstypical duration
Incidents per month
01020AprMayJunJulAugSepOct8
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking Kore.ai in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20261432 of 720 (4%)
May 2026920 of 744 (3%)
June 2026824 of 720 (3%)
July 20261357 of 744 (8%)
August 2026844 of 744 (6%)
September 2026815 of 720 (2%)
October 202686 of 591 (1%)

Incidents, newest first

Critical July 22, 2026 US SaaS - Issue observed with Search Assist 19m Web Crawler, Application Service, Search Service

Started Jul 22, 2026, 03:40 PM UTC· resolved Jul 22, 2026, 04:00 PM UTC

  1. investigating Jul 22, 2026, 03:40 PM UTC

    We are currently experiencing an issue with Search Assist. Our team is actively investigating the issue and working toward a resolution. We will continue to provide updates as more information becomes available. We sincerely apologize for any inconvenience caused.

  2. monitoring Jul 22, 2026, 03:50 PM UTC

    The team had identified and fixed the issue. The Search Assist is stable now. We'll be monitoring for sometime

  3. resolved Jul 22, 2026, 04:00 PM UTC

    The issue is now resolved. Thank You for your patience.

Read the full incident report →

Notice July 16, 2026 Kore.ai Developer Portal Accessibility Issue 57m

Started Jul 16, 2026, 03:00 AM UTC· resolved Jul 16, 2026, 03:57 AM UTC

  1. resolved Jul 16, 2026, 09:27 AM UTC

    We are notifying you that our Developer Portal (https://developer.kore.ai) experienced a service disruption on 16 July 2026 from 8:30 AM IST to 9:27 AM IST, lasting approximately 56 minutes. During this period, the Developer Portal, including access to product documentation, was unavailable. The service has since been fully restored, and the Developer Portal is now operating normally. We sincerely apologize for the inconvenience this may have caused and appreciate your patience and understanding.

Read the full incident report →

Minor July 13, 2026 Investigating Performance Degradation – UAE Instance 22h 57m

Started Jul 13, 2026, 02:09 PM UTC· resolved Jul 14, 2026, 01:06 PM UTC

  1. resolved Jul 13, 2026, 03:56 PM UTC

    We observed intermittent performance degradation on the UAE Instance between 07:39 PM IST and 08:06 PM IST (06:09 PM GST and 06:36 PM GST, UAE Time). The issue was identified by our teams and mitigation actions have been applied. Service performance has since stabilized, and we continue to monitor the environment closely to ensure normal operations. We apologize for any inconvenience caused and will provide further updates if necessary.

Read the full incident report →

Minor July 1, 2026 UAE Region - Intermittent response drops were obeserved for some time. 8h 38m

Started Jul 01, 2026, 07:35 PM UTC· resolved Jul 02, 2026, 04:14 AM UTC

  1. resolved Jul 01, 2026, 07:35 PM UTC

    This is to notify the users of the UAE region that their apps or bots may have faced intermittent issues like sporadic response failures or call drops in the UAE region. Incident lasted for approximately 28 minutes between Wed Jul 1, 2026 2:44 PM EST to Wed, Jul 1, 2026 3:12 PM EST. This incident was internally identified by our proactive monitoring. Note - There is no outage right now and the alert has recovered. We are continuing to monitor the environment. We sincerely apologize for any inconvenience caused and thank you for your continued trust in us.

Read the full incident report →

Major July 1, 2026 Kore Japan Region - Kore Voice gateway service is experiencing a partial service disruption 1d 3h Kore IVR

Started Jul 01, 2026, 08:16 AM UTC· resolved Jul 02, 2026, 11:26 AM UTC

  1. investigating Jul 01, 2026, 08:16 AM UTC

    **Kore Japan Region:** We are again experiencing a recurring partial disruption affecting both inbound and outbound calling through the Kore Voice Gateway service. We understand the impact this may have on your operations and sincerely apologize for the inconvenience. Our engineering and operations teams are actively investigating the issue, working to identify the underlying cause, and implementing remediation measures to restore full service as quickly as possible. We will continue to provide timely updates as more information becomes available and appreciate your patience and understanding.

  2. monitoring Jul 01, 2026, 10:14 AM UTC

    Kore Japan Region: Mitigation measures have been implemented for the issue affecting inbound and outbound voice calling services, and operations are currently stable. Our teams remain actively engaged and are closely monitoring the environment to validate the effectiveness of the fix and ensure ongoing service reliability. We appreciate your continued patience and will provide further updates if necessary.

  3. resolved Jul 02, 2026, 11:26 AM UTC

    The issue impacting inbound and outbound calling services through the Kore Voice Gateway in the Japan region has been resolved. No further issues have been observed by our monitoring systems or reported by customers during the extended monitoring period. We appreciate your patience, cooperation, and understanding throughout this incident.

Read the full incident report →

Minor July 1, 2026 Intermittent Issues Affecting App/Bot Training on JP Search Instance 3h 9m Search Service

Started Jul 01, 2026, 06:17 AM UTC· resolved Jul 01, 2026, 09:27 AM UTC

  1. investigating Jul 01, 2026, 06:17 AM UTC

    We are currently observing intermittent issues affecting the App/Bot Training on the JP Search instance. Our engineering team is actively investigating the issue and working to identify the root cause and restore normal service as quickly as possible. We will continue to provide updates as more information becomes available.

  2. monitoring Jul 01, 2026, 06:32 AM UTC

    The App/Bot Training issue has been resolved, and the affected functionality has been restored. Our teams will continue to closely monitor the system to ensure stability and verify that the issue does not recur.

  3. monitoring Jul 01, 2026, 06:32 AM UTC

    We are continuing to monitor the system to ensure stability

  4. resolved Jul 01, 2026, 09:27 AM UTC

    This incident has been resolved at 11:45 AM IST.

Read the full incident report →

Major July 1, 2026 Intermittent Issues Affecting Analytics on IND Instance 2h 32m Analytics

Started Jul 01, 2026, 05:50 AM UTC· resolved Jul 01, 2026, 08:23 AM UTC

  1. investigating Jul 01, 2026, 05:50 AM UTC

    We are currently observing intermittent issues affecting the Analytics section on the IND instance. Our teams are actively investigating the issue and working to identify the root cause and restore normal service as quickly as possible. Please note that there is no impact on platform runtime. We will continue to provide updates as more information becomes available.

  2. monitoring Jul 01, 2026, 07:45 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jul 01, 2026, 08:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 30, 2026 US Central Region - Call recording availability is impacted 23m Kore IVR

Started Jun 30, 2026, 05:17 PM UTC· resolved Jun 30, 2026, 05:40 PM UTC

  1. investigating Jun 30, 2026, 05:17 PM UTC

    Dear Users, We want to let you know that the bot developers and admins are currently facing issues in accessing the call recording in the XOCC dashboard in the US Central region. We are addressing this issue as soon as possible. We will keep you posted. Please note that there is no impact on service availability in general and runtime is not impacted.

  2. monitoring Jun 30, 2026, 05:21 PM UTC

    We identified the issue and fixed it. Currently, we are monitoring the progress

  3. monitoring Jun 30, 2026, 05:28 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jun 30, 2026, 05:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 25, 2026 US Region (Standalone SearchAI) - Brief intermittent service disruptions observed on Standalone SearchAI apps –

Started Jun 25, 2026, 09:15 PM UTC· resolved Jun 25, 2026, 09:15 PM UTC

  1. resolved Jun 25, 2026, 09:28 PM UTC

    This is to keep our users updated that we observed a brief partial service disruption on Standalone SearchAI on our US region between Thu, Jun 25, 2026 4:52:09 PM EST and Thu, Jun 25, 2026 5:00:26 PM EST. Some search integration calls may have failed during this time. We sincerely apologize for the inconvenience caused due to this brief partial service disruption

Read the full incident report →

Notice June 11, 2026 Azure OpenAI Service Degradation – GPT‑4.1 Mini 5XX Errors and Latency Across Multiple Regions 1h 16m

Started Jun 11, 2026, 03:58 AM UTC· resolved Jun 11, 2026, 05:14 AM UTC

  1. investigating Jun 11, 2026, 03:58 AM UTC

    Dear User, This is to keep you informed that Microsoft Azure has reported an ongoing platform issue affecting the Azure OpenAI Service across multiple regions since 01:02 UTC on 11 June 2026. The issue is impacting the GPT-4.1 Mini (version 2025-04-14) model, where customers may experience: HTTP 5XX errors on LLM requests Request timeouts and intermittent failures Increased response latency and degraded performance Interruptions to applications and workflows dependent on successful model responses Current Status: Microsoft has identified that a sudden increase in request volume on a subset of service endpoints has resulted in capacity constraints, causing request failures and performance degradation. The Azure team is actively investigating, analyzing service telemetry, and scaling resources to stabilize the affected endpoints. Potential Impact: Customers using GPT-4.1 Mini may experience intermittent failures, delayed responses, or unsuccessful completions for chat and prompt requests. We are actively monitoring the situation and coordinating with Microsoft for further updates. Additional information will be shared as it becomes available.

  2. resolved Jun 11, 2026, 05:14 AM UTC

    Microsoft has confirmed that the issue has been mitigated.

Read the full incident report →

Critical June 11, 2026 Experiencing Outage with Kore.ai Agent Platform On US Region 36m Agentic App, Tool, Model Studio, Prompt Studio and 4 more

Started Jun 11, 2026, 12:26 AM UTC· resolved Jun 11, 2026, 01:02 AM UTC

  1. investigating Jun 11, 2026, 12:26 AM UTC

    We are currently experiencing a service disruption affecting the Agent Platform in the US region. Our engineering team is actively investigating the issue and working to restore normal service as quickly as possible. We will continue to provide updates as more information becomes available and progress is made.

  2. resolved Jun 11, 2026, 01:02 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 10, 2026 US Region - AI for Process (AI4P) service disruption 9h 9m

Started Jun 10, 2026, 11:10 PM UTC· resolved Jun 11, 2026, 08:19 AM UTC

  1. resolved Jun 12, 2026, 09:23 PM UTC

    We would like to report an incident that we observed with AI for Process product on 11 June between 4:40 AM IST and 1:49 PM IST. The automation executions were impacted. On successful resolution of the incident, the automations resumed. We deeply apologize for the inconvenience caused by this incident to our AI4P users and customers. We are doing everything we can to avoid any recurrence of such incidents.

Read the full incident report →

Major June 5, 2026 Kore.ai is Investigating on the Issue with Standalone SearchAI Causing No Search Results Across Chat and Voice Agents with US Region 1h 28m Search Service

Started Jun 05, 2026, 05:38 PM UTC· resolved Jun 05, 2026, 07:07 PM UTC

  1. investigating Jun 05, 2026, 05:38 PM UTC

    Our customers who are all using standalone SearchAI are facing an impact with the Search results across the chats and voice agents. We are actively investigating the issue on our end. Please note that there is no impact on the SearchAI - UXO platform. We will keep you updated once the cause is identified.

  2. identified Jun 05, 2026, 06:34 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jun 05, 2026, 06:48 PM UTC

    We are monitoring the results.

  4. resolved Jun 05, 2026, 07:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 5, 2026 Investigating issues with Agent Platform on the JP Instance. 12h 10m Agentic Apps

Started Jun 05, 2026, 01:53 AM UTC· resolved Jun 05, 2026, 02:03 PM UTC

  1. investigating Jun 05, 2026, 01:53 AM UTC

    Dear Users, We are aware of an issue impacting the Agent Platform JP instance and are actively investigating it. Our teams are working to mitigate the issue, and we will share further updates as they become available. Thank you for your patience.

  2. investigating Jun 05, 2026, 02:13 AM UTC

    Investigation is ongoing. Our teams are actively working to identify the root cause and restore full service functionality. We will provide further updates as progress is made.

  3. investigating Jun 05, 2026, 02:36 AM UTC

    Our teams continue to investigate the issue and work toward a resolution. We are assessing the underlying cause and will share additional updates as soon as more information becomes available.

  4. investigating Jun 05, 2026, 03:19 AM UTC

    Our teams are actively analyzing the issue and implementing corrective measures. We will continue to provide updates as the investigation progresses and additional details become available.

  5. investigating Jun 05, 2026, 04:01 AM UTC

    Our teams are continuing to investigate the issue and work toward a resolution. We will share further updates as more information becomes available and progress is made.

  6. identified Jun 05, 2026, 04:35 AM UTC

    The issue has been identified and the teams are working on implementing a fix.

  7. identified Jun 05, 2026, 06:20 AM UTC

    The implementation of the proposed fix is currently in progress. We will provide further updates as work advances and additional details become available.

  8. identified Jun 05, 2026, 07:57 AM UTC

    The implementation of the proposed fix is currently underway. The service provider is actively working on mitigation efforts to address the issue. We will continue to share updates as progress is made and additional information becomes available.

  9. identified Jun 05, 2026, 09:42 AM UTC

    Mitigation efforts are currently in progress with the service provider. We will share further updates as soon as additional information becomes available.

  10. monitoring Jun 05, 2026, 10:32 AM UTC

    The fix has been deployed, and the team is actively monitoring the platform to ensure service stability.

  11. resolved Jun 05, 2026, 02:03 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 4, 2026 Investigating issues with XO 10 Platform on the UAE Instance. 37m Bot Uptime, Bot Builder

Started Jun 04, 2026, 01:30 AM UTC· resolved Jun 04, 2026, 02:07 AM UTC

  1. investigating Jun 04, 2026, 01:30 AM UTC

    Dear USers, We are currently experiencing issues with bot responses across both XO 10 and XO 11UAE instances. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. We will provide further updates as more information becomes available.

  2. investigating Jun 04, 2026, 01:44 AM UTC

    The investigation is ongoing, and we are working to determine the cause of the issue.

  3. monitoring Jun 04, 2026, 02:02 AM UTC

    The issue has been successfully mitigated. We will continue to monitor the environment closely and provide updates if any further concerns are identified.

  4. resolved Jun 04, 2026, 02:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 29, 2026 US Region - Dialog GPT Response Latency observed for Customer using MS Azure Open AI 6h 50m Bot Uptime

Started May 29, 2026, 03:29 PM UTC· resolved May 29, 2026, 10:20 PM UTC

  1. investigating May 29, 2026, 03:29 PM UTC

    We are currently observing increased latency for multiple services hosted in the Microsoft Azure West US 2 region. This appears to be related to an ongoing Azure platform incident: https://azure.status.microsoft/en-gb/status. Our teams are actively monitoring the situation. At this time, we would like to clarify that there is no service degradation from the Kore application perspective, and the impact is due to external infrastructure factors. We will continue to monitor the situation and keep this page updated.

  2. resolved May 29, 2026, 10:20 PM UTC

    The incident at Azure’s end stands resolved as per https://azure.status.microsoft/en-gb/status. We are resolving this incident as it was created with the intention to make our users and subscribers aware of this issue.

Read the full incident report →

Major May 21, 2026 US Region - AI4Work is experiencing intermittent service disruptions 46m AI for Work - USA

Started May 21, 2026, 08:55 PM UTC· resolved May 21, 2026, 09:41 PM UTC

  1. investigating May 21, 2026, 08:55 PM UTC

    Dear Users, This is to notify you that the AI4Work product is experiencing intermittent service disruptions currently. We are working on high priority to remediate the issue. We will keep you posted on the resolution.

  2. monitoring May 21, 2026, 09:24 PM UTC

    Update - The issue has been mitigated. We are continuing to monitor. Most functionalities should be restored now.

  3. resolved May 21, 2026, 09:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 21, 2026 US Region - Degraded performance of analytics dashboard observed on XO11. 49m Bot Builder

Started May 21, 2026, 05:31 PM UTC· resolved May 21, 2026, 06:21 PM UTC

  1. investigating May 21, 2026, 05:31 PM UTC

    We are currently investigating the issue.

  2. identified May 21, 2026, 05:51 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring May 21, 2026, 06:03 PM UTC

    A fix has been implemented and we are monitoring the system behaviour.

  4. resolved May 21, 2026, 06:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 21, 2026 US Region - Observing Intermittent timeout errors with the Orchestrator /GPT Module 48m Bot Builder

Started May 21, 2026, 01:04 PM UTC· resolved May 21, 2026, 01:53 PM UTC

  1. identified May 21, 2026, 01:04 PM UTC

    We are currently investigating intermittent timeout errors impacting the Orchestrator / GPT Module. We understand this may be affecting customer experience and appreciate your patience while our teams work to resolve the issue. A fix is currently in progress, and we will continue to share updates as more information becomes available. We apologise for the incovenience caused. Please note: This is not a full outage, and services remain partially operational.

  2. resolved May 21, 2026, 01:53 PM UTC

    We'd like to let you know that the fix has been implemented and validated from our end. The issue is now resolved. We really appreciate your patience.

Read the full incident report →

Minor May 19, 2026 US Region - Analytics dashboard - XO10 and XO11 - Data not loading for May 18th onwards 41m Bot Builder

Started May 19, 2026, 08:14 PM UTC· resolved May 19, 2026, 08:55 PM UTC

  1. investigating May 19, 2026, 08:14 PM UTC

    Dear Users, We are observing that the dashboard and analytics data is not loading for May 18th onwards. The technical team is trying to resolve this on high priority. We will keep you updated. Please note - 1. There is no outage as such. The dashboard and analytics have been observed to be loading data until 17th May 2026. 2. Conversation History API is not impacted. It is pulling the data as expected for 18th and 19th May.

  2. resolved May 19, 2026, 08:55 PM UTC

    The incident has ben resolved now. We will continuing to monitor the situation at our end.

Read the full incident report →

Major May 18, 2026 US Region - XO10 - Search AI integrations - Partial service disruption 2h 33m Application Service, Search Service

Started May 18, 2026, 03:12 PM UTC· resolved May 18, 2026, 05:46 PM UTC

  1. investigating May 18, 2026, 04:47 PM UTC

    Dear Users, We are experiencing a partial service disruption on SearchAI on US region. XO10 integrations are impacted intermittently. We will keep you updated on the resolution of the incident. We apologize for the inconvenience caused and we appreciate your patience while we work through the resolution.

  2. resolved May 18, 2026, 05:46 PM UTC

    This incident has now been resolved. Our team will continue to monitor to avoid any further disriptions

Read the full incident report →

Major May 15, 2026 US Region - Degraded performance of analytics dashboard observed across XO10 and XO11. 3h 24m Bot Builder

Started May 15, 2026, 03:01 PM UTC· resolved May 15, 2026, 06:26 PM UTC

  1. investigating May 15, 2026, 03:01 PM UTC

    Hello Users, We are observing degraded performance in the loading of dashboards across XO10 on XO11 in the US region. Please be assured that the experts are looking into it and trying to remediate the issue as soon as possible. We would also like to call out that there is no run-time impact: Bot responses for both digital and IVR type of channels are not impacted. Hence there is no outage as such on the Kore platform.

  2. investigating May 15, 2026, 04:24 PM UTC

    Update-we are continuing to investigate the issue on high priority. Please be assured that it is a priority for us to remediate the issue.

  3. monitoring May 15, 2026, 04:55 PM UTC

    Update - The issue is partially resolved. While the dashboards should be loading now. It may take 2-3 hours more for the bot analytics related dashboards like performance dashboards to load the data. We will keep you updated on the complete resolution of the issue.

  4. resolved May 15, 2026, 06:26 PM UTC

    Update - The issue with the dashboard should be resolved now. We will continue to monitor from our end as well.

Read the full incident report →

Major May 8, 2026 US region - Kore voice gateway - partial service disruption 2h 20m Kore IVR

Started May 08, 2026, 12:14 AM UTC· resolved May 08, 2026, 02:34 AM UTC

  1. investigating May 08, 2026, 12:14 AM UTC

    Our internal monitoring has detected that one of the SBC servers 3.224.189.218 is currently down. We are working with AWS to resolve the issue as soon as possible. The impacted server is in US east 1 region.

  2. investigating May 08, 2026, 01:05 AM UTC

    We are continuing to investigate the issue with the service provider. More details available at https://health.aws.amazon.com/health/status

  3. investigating May 08, 2026, 02:03 AM UTC

    Below is the latest update from the Service Provider: We continue to work towards mitigating the increased temperatures to its normal levels in the affected Availability Zone (use1-az4) in the US-EAST-1 Region. Other AWS services that depend on the affected EC2 instances and EBS volumes in this Availability Zone, may also experience impairments. We have weighed away traffic for most services at this time. Customers may experience longer than usual provisioning times. We will provide an update by 7:45 PM PDT, or sooner if we have additional information to share.

  4. monitoring May 08, 2026, 02:15 AM UTC

    A fix has been implemented and we will continue to monitor the system.

  5. resolved May 08, 2026, 02:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 7, 2026 An intermittent issue with bot responses has been observed for some bots/apps on the US instance. 1h 23m Bot Uptime

Started May 07, 2026, 12:20 AM UTC· resolved May 07, 2026, 01:44 AM UTC

  1. investigating May 07, 2026, 12:38 AM UTC

    We are currently investigating the issue.

  2. investigating May 07, 2026, 01:10 AM UTC

    We are continuing to investigate the issue.

  3. monitoring May 07, 2026, 01:34 AM UTC

    The issue has been mitigated and we will continue to monitor the System behaviour.

  4. resolved May 07, 2026, 01:44 AM UTC

    This incident has been resolved.

  5. postmortem May 07, 2026, 03:04 AM UTC

    Dear Users, We would like to inform you about a network connectivity issue identified during a recent incident triage involving access to our platform \( XO 11 US Instance\) through the AWS Global Accelerator \(GA\) service. To ensure continued platform availability and avoid any potential service disruption, we have temporarily rerouted traffic directly through our Application Load Balancers \(ALBs\) by bypassing the AWS Global Accelerator layer. ### Potential Impact Customers who have whitelisted the previously provided static IP addresses within their enterprise networks may experience connectivity issues as a result of this change. This is because ALBs use dynamically assigned IP addresses rather than static ones. ### Recommended Action To help avoid any interruption in service access, we kindly request customers to temporarily: * Whitelist the domain: `platform.kore.ai` within their enterprise network * Remove the existing static IP-based restrictions until further notice Previously shared static IPs: * `166.117.119.104` * `166.117.234.93` ### Next Steps Our engineering and DevOps team is actively working with AWS to isolate and resolve the underlying issue as soon as possible. Once the issue is resolved, we will share updated guidance along with any revised IP details, if applicable. We sincerely apologize for any inconvenience this may cause and appreciate everyone’s patience, understanding, and cooperation while we work toward a resolution.

Read the full incident report →

Minor April 28, 2026 SaaS US Region - Issues observed with analytics and dashboard sync. 3h 6m Bot Builder

Started Apr 28, 2026, 03:48 PM UTC· resolved Apr 28, 2026, 06:54 PM UTC

  1. identified Apr 28, 2026, 03:48 PM UTC

    Dear Users, In our US region, we are observing a sync failure with our data-lake that caters to dashboards and analytics. We are engaged with AWS to understand the root cause and remediate as soon as possible. Impact: The dashboards and analytics will load but any transaction data on of after 9:40 am EST 28 Apr 2026 will not be reported on the dashboard until this issue is resolved.

  2. identified Apr 28, 2026, 06:11 PM UTC

    Update - We continue to work with AWS to remediate the issue. Revised impact assessment: 1. The dashboards and analytics will load but any transaction data on of after 9:40 am EST 28 Apr 2026 will not be reported on the dashboard until this issue is resolved. 2. Ability to export dashboard data may be impacted. 3. Custom dashboards may also be impacted.

  3. resolved Apr 28, 2026, 06:54 PM UTC

    This incident has been resolved.

Read the full incident report →