<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.unity.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.unity.com"/>
  <link rel="self" type="application/atom+xml" href="https://status.unity.com/history.atom"/>
  <title>Unity Status - Incident History</title>
  <updated>2026-07-28T20:39:41Z</updated>
  <author>
    <name>Unity Services</name>
  </author>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/383603</id>
    <published>2026-08-01T21:00:00Z</published>
    <category term="event:end" label="2026-08-01T21:00:00Z"/>
    <updated>2026-07-04T21:01:00Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/383603"/>
    <title>Unity Build Automation Scheduled Maintenance</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - Collaboration / Unity DevOps, Unity Build Automation, Backend Service, Queue Performance - Mac Builders, Queue Performance - Windows Builders, License Activations - Unity Editor, Cost &amp; Usage Reporting&lt;/p&gt;&lt;p&gt;&lt;small&gt;July  4, 2026 · 21:01 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Team Unity Build Automation will be performing scheduled maintenance on a recurring basis. Please expect minor disruptions to the services during these times. We appreciate your patience and understanding as we work to improve our services. We thank you for your cooperation.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/389014</id>
    <published>2026-07-28T15:50:00Z</published>
    <category term="event:end" label="2026-07-28T15:54:00Z"/>
    <updated>2026-07-28T15:59:17Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/389014"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;July 28, 2026 · 21:26 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mtu1xp environment, its resolved now&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started - 15:50 UTC  &lt;br /&gt;
Usage recovery - 15:54 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox Operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/388953</id>
    <published>2026-07-28T13:23:45Z</published>
    <category term="event:end" label="2026-07-28T13:56:19Z"/>
    <updated>2026-07-28T13:56:19Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/388953"/>
    <title>Service Unity Source Code seems to be down</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Major incident&lt;/strong&gt; - Source Code, Unity Source Code&lt;/p&gt;&lt;p&gt;&lt;small&gt;July 28, 2026 · 13:56 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Service is back up.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July 28, 2026 · 13:23 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
According to our monitoring system this service has become unresponsive, we’re investigating.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/388957</id>
    <published>2026-07-28T12:22:00Z</published>
    <category term="event:end" label="2026-07-28T20:20:00Z"/>
    <updated>2026-07-28T20:39:41Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/388957"/>
    <title>Investigating issue on Udash Integration (mtu1xp)</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;July 28, 2026 · 18:49 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
12:22 UTC: We are investigating a potential issue in services for your platform. We are currently assessing player impact, if any.&lt;/p&gt;
&lt;p&gt;
12:32 UTC: We have confirmed and identified the issue with your platform and are working to resolve it. &lt;/p&gt;
&lt;p&gt;
We are performing a couple of emergency restart on your voice platform due to an issue with one of your signaling servers.  &lt;br /&gt;
There will be a brief interruption to a percentage of player sessions, but players should be able to connect back after the restart.&lt;/p&gt;
&lt;p&gt;
20:20 UTC : We have resolved the identified issue and are currently seeing recovery in the systems and player access. &lt;/p&gt;
&lt;p&gt;
Apologies for any inconvenience this may have caused.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/388753</id>
    <published>2026-07-27T08:49:00Z</published>
    <category term="event:end" label="2026-07-27T13:08:32Z"/>
    <updated>2026-07-27T13:08:32Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/388753"/>
    <title>Source Code Seat Assignments Disruption</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Source Code, Unity Source Code&lt;/p&gt;&lt;p&gt;&lt;small&gt;July 27, 2026 · 13:07 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The issue affecting seat assignment provisioning for Unity Source Code has been resolved. New seat assignments are now processing normally. Existing user access to Unity Source Access was not impacted at any point during this incident. We apologize for any inconvenience this may have caused and thank you for your patience.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July 27, 2026 · 08:49 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We have identified an issue affecting user access to Unity Source Code. As a result, new seat assignments are not currently being processed. Existing user access to Unity Source Code remains uninterrupted and unaffected. We are actively working to resolve the underlying issue. In the meantime, new seat assignment changes may be delayed. We apologize for any inconvenience this may cause and appreciate your patience as we work to fully resolve the issue.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/388718</id>
    <published>2026-07-27T04:19:00Z</published>
    <category term="event:end" label="2026-07-27T04:21:00Z"/>
    <updated>2026-07-27T04:25:40Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/388718"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mt2p Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;July 27, 2026 · 09:53 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mt2p environment, its resolved now&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started     04:19 UTC  &lt;br /&gt;
Usage recovery 04:21 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox Operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/388720</id>
    <published>2026-07-26T23:06:00Z</published>
    <category term="event:end" label="2026-07-26T23:10:00Z"/>
    <updated>2026-07-27T04:43:57Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/388720"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mt2p Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;July 27, 2026 · 04:41 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mtu1xp environment, its resolved now&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started     04:36 UTC  &lt;br /&gt;
Usage recovery 04:40 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox Operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/387563</id>
    <published>2026-07-21T17:58:41Z</published>
    <category term="event:end" label="2026-07-21T19:22:44Z"/>
    <updated>2026-07-21T19:22:44Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/387563"/>
    <title> Secret Manager errors affecting Cloud Code and Matchmaker</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - LiveOps, Cloud Code&lt;/p&gt;&lt;p&gt;&lt;small&gt;July 21, 2026 · 19:21 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
A fix has been deployed, services back to normal.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July 21, 2026 · 19:19 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are confident that Cloud Code and Matchmaker have returned to stable operation. Our team will continue to monitor the service.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July 21, 2026 · 17:58 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We’re aware of an issue where requests to Secret Manager via Cloud Code and Matchmaker are returning “Bad Gateway” errors. Our team is actively investigating the root cause and working to restore normal service.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/387149</id>
    <published>2026-07-21T15:49:00Z</published>
    <category term="event:end" label="2026-07-29T16:49:00Z"/>
    <updated>2026-07-21T15:49:00Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/387149"/>
    <title>Upcoming migration: please verify your auth token formatting</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - LiveOps, Cloud Save, Leaderboards&lt;/p&gt;&lt;p&gt;&lt;small&gt;July 21, 2026 · 16:00 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We’re migrating traffic for the Leaderboards and Cloud Save services to an updated backend infrastructure. As part of this change, authorization token parsing will become stricter.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;In some cases, tokens containing extra characters such as a trailing newline or other invisible/whitespace characters that currently work without issue&lt;/strong&gt; may start returning a 401 Authorization header should contain ‘Basic &lt;public-identifier&gt;:&lt;secret&gt;’ error after the migration.&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;What to do:&lt;/strong&gt; Before July 28 we recommend double-checking how your auth token is generated and stored to ensure it doesn’t contain unexpected trailing characters.&lt;/p&gt;
&lt;p&gt;
If you run into issues, please reach out to Unity Support and reference this notice.&lt;/p&gt;
&lt;p&gt;
Thank you&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/386306</id>
    <published>2026-07-16T15:10:41Z</published>
    <category term="event:end" label="2026-07-16T20:08:29Z"/>
    <updated>2026-07-16T20:08:29Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/386306"/>
    <title>Matchmaker Missing Logs</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Multiplayer, Matchmaker&lt;/p&gt;&lt;p&gt;&lt;small&gt;July 16, 2026 · 20:06 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are confident that Matchmaker logs have returned to stable operation. Our team will continue to monitor, but at this time we consider the incident resolved.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July 16, 2026 · 15:10 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are aware of an issue affecting Matchmaker logs and are currently investigating. Matchmaker services are operational. Our team is actively working to identify the cause and assess the impact. We will provide further updates as soon as more information becomes available.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/385845</id>
    <published>2026-07-14T10:24:00Z</published>
    <category term="event:end" label="2026-07-15T10:41:08Z"/>
    <updated>2026-07-15T10:41:08Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/385845"/>
    <title>[Leaderboards] Scheduled Resets</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - LiveOps, Leaderboards&lt;/p&gt;&lt;p&gt;&lt;small&gt;July 15, 2026 · 10:41 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The incident has been resolved and we are monitoring the situation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July 14, 2026 · 14:11 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
&lt;strong&gt;Update&lt;/strong&gt;  &lt;br /&gt;
A fix has been deployed to resolve the  Scheduled Leaderboards Reset issue identified earlier today. &lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;Impact&lt;/strong&gt;  &lt;br /&gt;
Leaderboards scheduled resets were unable to execute successfully between 09:52 - 11:38 UTC today 14th July 2026. Any leaderboard resets scheduled to occur during the affected window would not have executed successfully. &lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;Recommendation&lt;/strong&gt;  &lt;br /&gt;
Customers, particularly those with longer leaderboard duration resets scheduled to occur during this time must manually reset the leaderboard in the Unity dashboard. &lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;Status&lt;/strong&gt;  &lt;br /&gt;
We are continuing to monitor the service and will update accordingly.  &lt;br /&gt;
Apologies for the inconvenience&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July 14, 2026 · 10:34 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are currently investigating an issue relating to scheduled resets of UGS Leaderboards. Our engineering team is actively triaging the situation, and we will provide an update as soon as we have more information.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/384997</id>
    <published>2026-07-13T15:00:00Z</published>
    <category term="event:end" label="2026-07-13T15:30:00Z"/>
    <updated>2026-07-13T15:30:00Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/384997"/>
    <title>Scheduled Maintenance Update for MTU1XP</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;July  9, 2026 · 13:58 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Hello team, &lt;/p&gt;
&lt;p&gt;
We are planning to perform maintenance on your voice platform on Monday July 13th at 11:00AM EDT. The maintenance is expected to take less than 15 minutes. However, we will continue to monitor the voice platform for 1 hour. Players in channel will be affected during this time. Please reply to this email if you have any questions with regard to this planned maintenance. Thank you!  &lt;br /&gt;
Sincerely,&lt;/p&gt;
&lt;p&gt;
The Unity Vivox Team&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/384411</id>
    <published>2026-07-07T12:26:52Z</published>
    <category term="event:end" label="2026-07-07T18:45:00Z"/>
    <updated>2026-07-08T11:08:20Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/384411"/>
    <title>Investigating latency with Cloud Save writes.</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Major incident&lt;/strong&gt; - LiveOps, Cloud Save&lt;/p&gt;&lt;p&gt;&lt;small&gt;July  8, 2026 · 11:06 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
After monitoring yesterday, we confirmed this issue is resolved&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July  7, 2026 · 13:33 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The service is now in a stable state. We continue monitoring the services and will remove the incident status as soon as we can confirm everything is in a healthy state.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July  7, 2026 · 12:26 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are investigating an increase in write latency to Cloud Save.  &lt;br /&gt;
We are upscaling services to reduce latency. &lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/384147</id>
    <published>2026-07-06T18:00:00Z</published>
    <category term="event:end" label="2026-07-07T13:45:00Z"/>
    <updated>2026-07-08T11:06:26Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/384147"/>
    <title>Cloud Save service calls are timing out</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Major incident&lt;/strong&gt; - LiveOps, Cloud Code, Cloud Save&lt;/p&gt;&lt;p&gt;&lt;small&gt;July  8, 2026 · 10:58 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The service has been fully restored and is operating normally.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July  7, 2026 · 19:23 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The incident has been resolved.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July  6, 2026 · 21:30 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The service has been fully restored and is operating normally.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July  6, 2026 · 20:33 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Services are returning. We continue to monitor the service while services comes back online.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July  6, 2026 · 20:23 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Our team is investigating an issue with the underlying persistence layer for Cloud Save. We will provide more information shortly.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July  6, 2026 · 18:57 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are currently investigating an issue with Cloud Save that is impacting read and write functionality. This will also impact down stream users of Cloud Code where they are using Cloud Save in their modules. Our engineering team is actively triaging the situation, and we will provide an update as soon as we have more information.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/383979</id>
    <published>2026-07-06T08:14:00Z</published>
    <category term="event:end" label="2026-07-06T09:44:53Z"/>
    <updated>2026-07-06T09:44:53Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/383979"/>
    <title>[Cloud Code] C# Modules Incident</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - LiveOps, Cloud Code&lt;/p&gt;&lt;p&gt;&lt;small&gt;July  6, 2026 · 09:42 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The issue with Cloud Code C# Module deployment and the admin dashboard has been resolved. &lt;/p&gt;
&lt;p&gt;
Apologies for the inconvenience.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July  6, 2026 · 08:43 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The issue with Cloud Code Modules has been resolved, and the admin dashboard and deployment functionality have been restored. &lt;/p&gt;
&lt;p&gt;
We will continue to monitor the service to ensure there are no further issues. &lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July  6, 2026 · 08:14 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are investigating an issue with Cloud Code C# Modules. Dashboard functionality and deployment appear to be impacted. &lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/383938</id>
    <published>2026-07-06T00:00:00Z</published>
    <category term="event:end" label="2026-07-06T17:40:30Z"/>
    <updated>2026-07-06T17:40:30Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/383938"/>
    <title>Friends service - low rate of failures</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Multiplayer, Friends&lt;/p&gt;&lt;p&gt;&lt;small&gt;July  6, 2026 · 17:40 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The incident has been resolved and we are monitoring the situation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July  6, 2026 · 04:08 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are experiencing intermittent issues with our Friends service, the team are currently investigating the issue, some customers may experience a low rate of intermittent failures.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/377623</id>
    <published>2026-07-04T21:00:00Z</published>
    <category term="event:end" label="2026-07-04T21:00:00Z"/>
    <updated>2026-06-06T21:00:01Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/377623"/>
    <title>Unity Build Automation Scheduled Maintenance</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - Collaboration / Unity DevOps, Unity Build Automation, Backend Service, Queue Performance - Mac Builders, Queue Performance - Windows Builders, License Activations - Unity Editor, Cost &amp; Usage Reporting&lt;/p&gt;&lt;p&gt;&lt;small&gt;June  6, 2026 · 21:00 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Team Unity Build Automation will be performing scheduled maintenance on a recurring basis. Please expect minor disruptions to the services during these times. We appreciate your patience and understanding as we work to improve our services. We thank you for your cooperation.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/383223</id>
    <published>2026-07-03T19:44:00Z</published>
    <category term="event:end" label="2026-07-03T19:48:00Z"/>
    <updated>2026-07-03T19:56:10Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/383223"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;July  4, 2026 · 01:24 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mtu1xp environment, its resolved now&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started     19:44 UTC  &lt;br /&gt;
Usage recovery 19:48 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox Operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/383021</id>
    <published>2026-07-02T21:26:00Z</published>
    <category term="event:end" label="2026-07-02T22:48:00Z"/>
    <updated>2026-07-03T19:53:54Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/383021"/>
    <title>Vivox DDOS, Stats lock up and VAA failure service issues </title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Multiplayer, Matchmaker, Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;July  3, 2026 · 03:25 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mtu1xp environment pointing towards the mim nodes. We have morpheus on HOS 2 and performed the mnesia wipe on the cluster, its resolved now.&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started     21:26 UTC  &lt;br /&gt;
Usage recovery 22:48 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox Operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/382940</id>
    <published>2026-07-02T11:32:00Z</published>
    <category term="event:end" label="2026-07-02T18:39:49Z"/>
    <updated>2026-07-02T18:39:49Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/382940"/>
    <title>Intermittent two-factor failures when logging in through login.unity.com</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Websites, Unity ID/Login, Unity Login&lt;/p&gt;&lt;p&gt;&lt;small&gt;July  2, 2026 · 18:39 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The incident has been resolved and we are monitoring the situation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July  2, 2026 · 18:36 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
A fix has been implemented and we are monitoring the situation to ensure stability.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July  2, 2026 · 15:49 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We have identified the issue and are working towards a fix. As a workaround, please use id.unity.com to log in for the timebeing. We apologize for the incident.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July  2, 2026 · 15:40 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We have identified the issue and are working towards a fix. We apologize for the incident.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July  2, 2026 · 11:39 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are currently investigating an issue. Our engineering team is actively triaging the situation, and we will provide an update as soon as we have more information.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/382765</id>
    <published>2026-07-01T08:52:14Z</published>
    <category term="event:end" label="2026-07-01T09:49:05Z"/>
    <updated>2026-07-01T09:49:05Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/382765"/>
    <title>[Analytics] Data Explorer - Unexpected  &apos;You are not allowed to perform this operation.&apos; errors</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Analytics, Gaming Services, Dashboards and Reporting&lt;/p&gt;&lt;p&gt;&lt;small&gt;July  1, 2026 · 09:48 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We have identified the cause of the Data Explorer page loading permission errors and deployed a fix. &lt;/p&gt;
&lt;p&gt;
Apologies for the inconvenience.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;July  1, 2026 · 08:52 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are investigating reports of  ‘You are not allowed to perform this operation.’ page load error messages impacting a subset of Analytics users. &lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/382220</id>
    <published>2026-06-29T15:17:00Z</published>
    <category term="event:end" label="2026-06-29T15:23:00Z"/>
    <updated>2026-06-29T15:28:33Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/382220"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 29, 2026 · 20:56 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mtu1xp environment, its resolved now&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started     15:17 UTC  &lt;br /&gt;
Usage recovery 15:23 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox Operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/382232</id>
    <published>2026-06-28T20:38:00Z</published>
    <category term="event:end" label="2026-06-28T21:02:00Z"/>
    <updated>2026-06-29T16:16:38Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/382232"/>
    <title>HOS lock up issue</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 29, 2026 · 21:40 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
HOS got locked up due to quesicing the PP.  Affected signalling services on mtu1xp environment, its resolved now post restarting morpheus on the HOS&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started     20:38 UTC  &lt;br /&gt;
Usage recovery 21:02 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox Operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/381963</id>
    <published>2026-06-28T08:20:00Z</published>
    <category term="event:end" label="2026-06-28T08:26:00Z"/>
    <updated>2026-06-28T14:07:50Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/381963"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 28, 2026 · 14:05 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mtu1xp environment, its resolved now.&lt;/p&gt;
&lt;p&gt;
Drop started - 01:50 PM UTC  &lt;br /&gt;
Usage recovery - 01:56 PM UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/381948</id>
    <published>2026-06-28T06:35:00Z</published>
    <category term="event:end" label="2026-06-28T06:41:00Z"/>
    <updated>2026-06-28T12:18:06Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/381948"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 28, 2026 · 12:15 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mtu1xp environment, its resolved now.&lt;/p&gt;
&lt;p&gt;
Drop started - 12:05 UTC  &lt;br /&gt;
Usage recovery - 12:11 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/381893</id>
    <published>2026-06-27T18:06:00Z</published>
    <category term="event:end" label="2026-06-27T18:10:00Z"/>
    <updated>2026-06-27T18:16:33Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/381893"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 27, 2026 · 23:43 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mtu1xp environment, its resolved now&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started - 18:06 UTC  &lt;br /&gt;
Usage recovery - 18:10 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox Operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/381748</id>
    <published>2026-06-26T20:23:00Z</published>
    <category term="event:end" label="2026-06-26T20:30:00Z"/>
    <updated>2026-06-26T20:44:26Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/381748"/>
    <title> Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mt1s Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 27, 2026 · 02:07 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mt1s environment, its resolved now&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started  - 20:23 UTC  &lt;br /&gt;
Usage recovery - 20:30 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox Operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/381595</id>
    <published>2026-06-26T01:21:00Z</published>
    <category term="event:end" label="2026-06-26T01:30:00Z"/>
    <updated>2026-06-26T01:33:40Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/381595"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 26, 2026 · 07:01 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mtu1xp environment, its resolved now&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started     01:21 UTC  &lt;br /&gt;
Usage recovery 01:30 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox Operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/381591</id>
    <published>2026-06-26T01:02:00Z</published>
    <category term="event:end" label="2026-06-26T01:06:00Z"/>
    <updated>2026-06-26T01:08:22Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/381591"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 26, 2026 · 06:36 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mtu1xp environment, its resolved now&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started     01:02 UTC  &lt;br /&gt;
Usage recovery 01:06 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox Operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/381546</id>
    <published>2026-06-25T15:05:00Z</published>
    <category term="event:end" label="2026-06-25T15:20:00Z"/>
    <updated>2026-06-25T21:01:42Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/381546"/>
    <title>Parsec - Issue with Signaling Service</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Parsec, Parsec Signaling Service&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 25, 2026 · 20:52 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
A bad deployment cause an issue with the signaling service that may have prevented clients from connecting to their hosts. We reverted the deployment and confirmed the issue was resolved.&lt;/p&gt;
&lt;p&gt;
We are exploring additional controls to prevent this from occurring in the future.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/381363</id>
    <published>2026-06-25T07:50:00Z</published>
    <category term="event:end" label="2026-06-25T08:14:05Z"/>
    <updated>2026-06-25T10:56:46Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/381363"/>
    <title>Login failures through login.unity.com</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Major incident&lt;/strong&gt; - Websites, Unity ID/Login, Unity Login&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 25, 2026 · 08:14 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The incident has been resolved and we are monitoring the situation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;June 25, 2026 · 08:11 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We identified a likely cause and is waiting for the fix to be deployed&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/380899</id>
    <published>2026-06-23T07:28:00Z</published>
    <category term="event:end" label="2026-06-23T07:33:00Z"/>
    <updated>2026-06-23T07:46:13Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/380899"/>
    <title> Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 23, 2026 · 13:11 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mt1p environment, its resolved now&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started  - 07:28 UTC  &lt;br /&gt;
Usage recovery - 07:33 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox Operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/380807</id>
    <published>2026-06-22T15:37:00Z</published>
    <category term="event:end" label="2026-06-24T09:03:20Z"/>
    <updated>2026-06-24T09:03:20Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/380807"/>
    <title>Admin API - degraded performance</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - LiveOps, Leaderboards&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 24, 2026 · 09:03 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The issue with the Leaderboards Admin API has been resolved and we are monitoring for any changes. Contact the Gaming Services support team if you see any further instances of 404s for the admin API&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;June 22, 2026 · 15:52 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We’ve confirmed an issue impacting the Leaderboards Admin API.  &lt;br /&gt;
Users may see unexpected 404 errors as a symptom of this incident.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/380017</id>
    <published>2026-06-22T14:00:00Z</published>
    <category term="event:end" label="2026-06-22T15:00:00Z"/>
    <updated>2026-06-22T15:00:00Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/380017"/>
    <title>Scheduled Maintenance Update for MTU1XP</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 17, 2026 · 15:49 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Hello Unity Vivox Users,&lt;/p&gt;
&lt;p&gt;
We are planning to perform maintenance on your voice platform on June 22nd 2026 at 10:00AM EDT. The maintenance is expected to take less than 20 minutes. However, we will continue to monitor the voice platform for 1 hour. Players in channel will be affected during this time. Please reply to this email if you have any questions with regard to this planned maintenance. Thank you!&lt;/p&gt;
&lt;p&gt;
Sincerely,  &lt;br /&gt;
The Unity Vivox Team&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/378566</id>
    <published>2026-06-22T07:00:00Z</published>
    <category term="event:end" label="2026-06-22T07:55:00Z"/>
    <updated>2026-06-22T07:58:11Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/378566"/>
    <title>Asset Manager scheduled maintenance</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - Collaboration / Asset Manager, Asset Transformations, Asset Manager Data Streaming, Asset Manager Storage&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 10, 2026 · 11:48 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The Asset Manager service will undergo routine maintenance on:&lt;/p&gt;
&lt;p&gt;
Wednesday, June 22, from 7:00 AM to 7:15 AM UTC&lt;/p&gt;
&lt;p&gt;
Although we expect the downtime to be minimal, services may be interrupted during this maintenance window. Maintenance is necessary to ensure continued reliability and optimal performance.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/380003</id>
    <published>2026-06-17T13:53:00Z</published>
    <category term="event:end" label="2026-06-17T16:52:08Z"/>
    <updated>2026-06-17T16:52:08Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/380003"/>
    <title>Degraded leaderboard performance</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - LiveOps, Leaderboards&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 17, 2026 · 16:52 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We’ve identified the cause and applied mitigations, and are continuing to watch Leaderboard responses to ensure it resolves things&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;June 17, 2026 · 14:23 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We’ve identified an issue causing Leaderboards to run slower than usual, which may impact load times for end users.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/381141</id>
    <published>2026-06-17T13:41:00Z</published>
    <category term="event:end" label="2026-06-25T12:11:06Z"/>
    <updated>2026-06-25T12:11:06Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/381141"/>
    <title>Diagnostics Lag</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Collaboration / Unity DevOps, Diagnostics&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 25, 2026 · 12:11 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The incident has been resolved and we are monitoring the situation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;June 23, 2026 · 18:31 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
There was an issue with diagnostics data. The team fixed the underlying issue and is now backfilling the data so there is some lag.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/379914</id>
    <published>2026-06-17T05:04:00Z</published>
    <category term="event:end" label="2026-06-17T05:07:00Z"/>
    <updated>2026-06-17T05:17:25Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/379914"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 17, 2026 · 10:38 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mt1p environment, its resolved now&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started - 05:04 UTC  &lt;br /&gt;
Usage recovery - 05:07 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox Operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/379883</id>
    <published>2026-06-17T01:26:00Z</published>
    <category term="event:end" label="2026-06-17T01:29:00Z"/>
    <updated>2026-06-17T01:34:26Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/379883"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 17, 2026 · 07:00 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mt1p environment, its resolved now&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started - 01:26 UTC  &lt;br /&gt;
Usage recovery - 01:29 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox Operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/379668</id>
    <published>2026-06-15T19:00:00Z</published>
    <category term="event:end" label="2026-06-16T13:55:00Z"/>
    <updated>2026-06-16T14:02:19Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/379668"/>
    <title>Instability serving content on docs.unity3d.com</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Major incident&lt;/strong&gt; - Websites, Unity Docs&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 16, 2026 · 13:55 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The service has been fully restored and is operating normally.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;June 16, 2026 · 13:44 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are currently investigating an issue. Our engineering team is actively triaging the situation, and we will provide an update as soon as we have more information.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/379020</id>
    <published>2026-06-13T01:01:23Z</published>
    <category term="event:end" label="2026-06-13T02:09:04Z"/>
    <updated>2026-06-13T02:09:04Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/379020"/>
    <title>UPM Registry service is down (Package Manager)</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Major incident&lt;/strong&gt; - Editor Services, Package Manager&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 13, 2026 · 02:08 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The internal infrastructure issue has been resolved, and the UPM Registry is fully operational.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;June 13, 2026 · 01:01 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The service is currently unavailable due to internal infrastructure issues.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/378764</id>
    <published>2026-06-11T13:45:00Z</published>
    <category term="event:end" label="2026-06-11T16:33:21Z"/>
    <updated>2026-06-11T16:33:21Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/378764"/>
    <title>Dashboard fails to load the new experience</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Websites, Unity Dashboard&lt;/p&gt;&lt;p&gt;&lt;small&gt;June 11, 2026 · 20:32 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The issue has been fixed.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;June 11, 2026 · 15:12 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Currently, loading the cloud.unity.com in the new experience will result in an &lt;code class=&quot;inline&quot;&gt;Unexpected error occurred when trying to show content&lt;/code&gt;. The issue has been identified and we are working on getting it resolved. &lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/378061</id>
    <published>2026-06-08T14:52:00Z</published>
    <category term="event:end" label="2026-06-08T16:38:16Z"/>
    <updated>2026-06-08T16:38:16Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/378061"/>
    <title>Analytics billing reporting delay </title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Analytics, Gaming Services, Dashboards and Reporting&lt;/p&gt;&lt;p&gt;&lt;small&gt;June  8, 2026 · 16:37 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The issue has been resolved, and the billing reports will update themselves on the next 12hourly update.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;June  8, 2026 · 15:43 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
we’ve confirmed that MAU tracking for analytics billing is working again, and are waiting for confirmation that reporting dashboard has caught up.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/369892</id>
    <published>2026-06-06T21:00:00Z</published>
    <category term="event:end" label="2026-06-06T22:00:00Z"/>
    <updated>2026-06-06T22:00:00Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/369892"/>
    <title>Unity Build Automation Scheduled Maintenance</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - Collaboration / Unity DevOps, Unity Build Automation, Backend Service, Queue Performance - Mac Builders, Queue Performance - Windows Builders, License Activations - Unity Editor, Cost &amp; Usage Reporting&lt;/p&gt;&lt;p&gt;&lt;small&gt;May  2, 2026 · 21:01 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Team Unity Build Automation will be performing scheduled maintenance on a recurring basis. Please expect minor disruptions to the services during these times. We appreciate your patience and understanding as we work to improve our services. We thank you for your cooperation.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/377622</id>
    <published>2026-06-06T15:19:00Z</published>
    <category term="event:end" label="2026-06-06T15:23:00Z"/>
    <updated>2026-06-06T20:57:50Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/377622"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June  6, 2026 · 20:54 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mtu1xp environment, its resolved now&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started     20:49 UTC  &lt;br /&gt;
Usage recovery 20:53 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox Operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/377404</id>
    <published>2026-06-05T19:55:57Z</published>
    <category term="event:end" label="2026-06-06T14:23:00Z"/>
    <updated>2026-06-05T19:55:57Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/377404"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mt1p Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June  5, 2026 · 19:52 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDos affected signalling services on mt1p environment, it’s resolved now.&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started     19:47 UTC  &lt;br /&gt;
Usage recovery   19:53 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox Operations.  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/377401</id>
    <published>2026-06-05T19:39:16Z</published>
    <category term="event:end" label="2026-06-06T14:08:00Z"/>
    <updated>2026-06-05T19:39:16Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/377401"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mt1p Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June  5, 2026 · 19:33 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDos affected signalling services on mt1p environment, it’s resolved now.&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started     19:32 UTC  &lt;br /&gt;
Usage recovery   19:38 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox Operations.  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/377400</id>
    <published>2026-06-05T19:33:10Z</published>
    <category term="event:end" label="2026-06-06T14:00:00Z"/>
    <updated>2026-06-05T19:33:10Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/377400"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mt1p Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June  5, 2026 · 19:27 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDos affected signalling services on mt1p environment, it’s resolved now.&lt;/p&gt;
&lt;p&gt;
Impact window :&lt;/p&gt;
&lt;p&gt;
Drop started     19:24 UTC  &lt;br /&gt;
Usage recovery   19:30 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/377075</id>
    <published>2026-06-05T14:00:00Z</published>
    <category term="event:end" label="2026-06-05T14:30:00Z"/>
    <updated>2026-06-05T14:30:00Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/377075"/>
    <title>Scheduled Maintenance Update for MT1S</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - Comms and Safety, Vivox, mt1s Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June  4, 2026 · 13:43 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Hello team, &lt;/p&gt;
&lt;p&gt;
We will be performing a software upgrade to the platform mt1s.vivox.com on June 5th at 10AM EST, the impact to player usage would be for around 10 mins. We will notify when the upgrade is complete.&lt;/p&gt;
&lt;p&gt;
Regards  &lt;br /&gt;
Vivox Operations&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/377026</id>
    <published>2026-06-04T10:20:00Z</published>
    <category term="event:end" label="2026-06-04T10:23:00Z"/>
    <updated>2026-06-04T10:33:51Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/377026"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June  4, 2026 · 15:56 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mtu1xp environment, its resolved now&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started     10:20 UTC  &lt;br /&gt;
Usage recovery 10:23 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox Operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/376815</id>
    <published>2026-06-03T08:07:00Z</published>
    <category term="event:end" label="2026-06-03T08:12:00Z"/>
    <updated>2026-06-03T08:17:36Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/376815"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June  3, 2026 · 13:44 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mt1p environment, its resolved now&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started     08:07 UTC  &lt;br /&gt;
Usage recovery 08:12 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox Operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/376835</id>
    <published>2026-06-03T03:13:00Z</published>
    <category term="event:end" label="2026-06-03T03:19:00Z"/>
    <updated>2026-06-03T08:58:08Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/376835"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June  3, 2026 · 08:50 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mtu1xp environment, its resolved now.&lt;/p&gt;
&lt;p&gt;
Impact Window :&lt;/p&gt;
&lt;p&gt;
Drop started : 8:43  UTC&lt;/p&gt;
&lt;p&gt;
Usage recovery : 8:49 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/376387</id>
    <published>2026-06-02T16:00:00Z</published>
    <category term="event:end" label="2026-06-02T16:30:00Z"/>
    <updated>2026-06-02T16:30:00Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/376387"/>
    <title>Scheduled Maintenance Update for MT2P</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - Comms and Safety, Vivox, mt2p Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June  1, 2026 · 14:58 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Hello team, &lt;/p&gt;
&lt;p&gt;
We are planning to perform maintenance to your voice platform on Tuesday , 2nd June at 12:00 PM EST. Maintenance will last for around 10 minutes.  &lt;br /&gt;
Please let us know if you have any questions around this. &lt;/p&gt;
&lt;p&gt;
The platform is mt2p for all platforms.&lt;/p&gt;
&lt;p&gt;
Regards  &lt;br /&gt;
Vivox Operations&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/376466</id>
    <published>2026-06-01T23:44:00Z</published>
    <category term="event:end" label="2026-06-01T23:48:00Z"/>
    <updated>2026-06-02T05:49:42Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/376466"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;June  2, 2026 · 05:44 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mtu1xp environment, its resolved now.&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started - 05:14 UTC  &lt;br /&gt;
Usage recovery - 05:18 UTC&lt;/p&gt;
&lt;p&gt;
Vivox operations&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/375629</id>
    <published>2026-05-27T17:00:00Z</published>
    <category term="event:end" label="2026-05-27T18:00:00Z"/>
    <updated>2026-05-27T18:00:00Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/375629"/>
    <title>Scheduled Voice Maintenance on Vivox MT Env mtu1xp</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;May 26, 2026 · 19:49 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We will be performing a maintenance on your voice platform on May 27th at 13:00 EDT. This maintenance is expected to last approximately 60 minutes and will have intermittent impact to voice.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/375490</id>
    <published>2026-05-27T14:00:00Z</published>
    <category term="event:end" label="2026-05-27T15:00:00Z"/>
    <updated>2026-05-27T15:00:00Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/375490"/>
    <title>Scheduled Maintenance Update for MT1s</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - Comms and Safety, Vivox, mt1s Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;May 26, 2026 · 15:15 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Hello team, &lt;/p&gt;
&lt;p&gt;
A scheduled maintenance update will be performed on your voice platform (MT1S) on Wednesday, May 27th 10:00-10:30am EST.  &lt;br /&gt;
During this time any users in channel will be unaffected but new users may be unable to join a channel.&lt;/p&gt;
&lt;p&gt;
Sincerely,  &lt;br /&gt;
The Unity Vivox Team&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/375254</id>
    <published>2026-05-25T18:30:00Z</published>
    <category term="event:end" label="2026-05-25T22:03:12Z"/>
    <updated>2026-05-25T22:03:12Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/375254"/>
    <title>UBA: Some Mac builds in EU are not starting</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Major incident&lt;/strong&gt; - Collaboration / Unity DevOps, Unity Build Automation, Queue Performance - Mac Builders&lt;/p&gt;&lt;p&gt;&lt;small&gt;May 25, 2026 · 22:01 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This issue has been resolved. Build Automation Mac builds in the Europe region are now fully operational. Thank you for your patience.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;May 25, 2026 · 20:42 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are investigating an issue affecting Mac builders in Europe, which is preventing new builds from being accepted, leading to long queue times. &lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/375078</id>
    <published>2026-05-25T03:22:06Z</published>
    <category term="event:end" label="2026-05-25T03:37:06Z"/>
    <updated>2026-05-25T03:37:06Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/375078"/>
    <title>Service Queue Performance - Mac Builders seems to be down</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Major incident&lt;/strong&gt; - Collaboration / Unity DevOps, Unity Build Automation, Queue Performance - Mac Builders&lt;/p&gt;&lt;p&gt;&lt;small&gt;May 25, 2026 · 03:37 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Service is back up.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;May 25, 2026 · 03:22 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
According to our monitoring system this service has become unresponsive, we’re investigating.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/374113</id>
    <published>2026-05-20T23:15:00Z</published>
    <category term="event:end" label="2026-05-26T12:22:17Z"/>
    <updated>2026-05-26T12:22:17Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/374113"/>
    <title>Partial outage - Relay</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Multiplayer, Relay&lt;/p&gt;&lt;p&gt;&lt;small&gt;May 26, 2026 · 12:22 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The service has been fully restored and is operating normally.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;May 21, 2026 · 00:43 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The incident has been resolved and we are monitoring the situation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;May 21, 2026 · 00:15 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are currently investigating an issue with Relay. Our engineering team is actively triaging the situation, you may see issues allocating in some regions; southamerica-east.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/373564</id>
    <published>2026-05-20T17:00:00Z</published>
    <category term="event:end" label="2026-05-20T18:00:00Z"/>
    <updated>2026-05-20T18:00:00Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/373564"/>
    <title>Scheduled Voice Maintenance on Vivox MT Env mtu1xp</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - Comms and Safety, Vivox, mtu1xp Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;May 19, 2026 · 16:09 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We will be performing maintenance tomorrow May 20th at 1:00 PM EDT on your voice platform. The maintenance is expected to last approximately 1 hour with intermittent impact to voice.  &lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/373261</id>
    <published>2026-05-19T16:00:00Z</published>
    <category term="event:end" label="2026-05-19T17:00:00Z"/>
    <updated>2026-05-19T17:00:00Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/373261"/>
    <title>Scheduled Unity Pipeline Automation Maintenance</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - Collaboration / Unity DevOps, Unity Pipeline Automation, Backend Service, Event Processing, Job Status Reporting, Job Queueing, Cost &amp; Usage Reporting&lt;/p&gt;&lt;p&gt;&lt;small&gt;May 18, 2026 · 22:04 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Scheduled Unity Pipeline Automation infrastructure maintenance. Brief service disruptions possible. No action required.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/373382</id>
    <published>2026-05-19T06:00:14Z</published>
    <category term="event:end" label="2026-05-19T06:01:02Z"/>
    <updated>2026-05-19T06:01:02Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/373382"/>
    <title>Service Package Manager seems to be down</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Major incident&lt;/strong&gt; - Editor Services, Package Manager&lt;/p&gt;&lt;p&gt;&lt;small&gt;May 19, 2026 · 06:01 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Service is back up.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;May 19, 2026 · 06:00 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
According to our monitoring system this service has become unresponsive, we’re investigating.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/372233</id>
    <published>2026-05-14T15:42:14Z</published>
    <category term="event:end" label="2026-05-14T20:18:16Z"/>
    <updated>2026-05-14T20:18:16Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/372233"/>
    <title>Build Automation – Degraded Performance (Europe Region)</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Major incident&lt;/strong&gt; - Collaboration / Unity DevOps, Unity Build Automation, Queue Performance - Mac Builders&lt;/p&gt;&lt;p&gt;&lt;small&gt;May 14, 2026 · 20:17 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
This issue has been resolved. Build Automation Mac builds in the Europe region are now fully operational. Thank you for your patience.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;May 14, 2026 · 15:42 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are currently experiencing degraded performance affecting UBA Mac builds in the Europe region. Our team is actively investigating and working to restore service.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/371939</id>
    <published>2026-05-13T18:00:00Z</published>
    <category term="event:end" label="2026-05-13T19:12:57Z"/>
    <updated>2026-05-13T19:12:57Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/371939"/>
    <title>Elevated latencies and error responses with the leaderboard service</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - LiveOps, Leaderboards&lt;/p&gt;&lt;p&gt;&lt;small&gt;May 13, 2026 · 19:12 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The incident has been resolved and we are monitoring the situation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;May 13, 2026 · 19:12 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The incident has been resolved and we are monitoring the situation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;May 13, 2026 · 18:34 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are currently investigating an issue. Our engineering team is actively triaging the situation, and we will provide an update as soon as we have more information.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/371688</id>
    <published>2026-05-13T18:00:00Z</published>
    <category term="event:end" label="2026-05-13T19:00:00Z"/>
    <updated>2026-05-13T19:00:00Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/371688"/>
    <title>Scheduled Voice Maintenance on Vivox MT Environments</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - Comms and Safety, Vivox, mt1p Domain, mt2p Domain, mt1s Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;May 12, 2026 · 15:47 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We will be updating our SSL/TLS certificates on Wednesday May 13th at 2:00 PM EDT, maintenance is expected to last 1 hour. This update ensures the widest possible coverage of client devices. Please be aware that this update may affect older unpatched Windows 7 and Windows 8 clients, who will not be able to connect to our systems. These clients may be able to patch their systems to support these new certificates. Patch information can be found here (&lt;a target=&quot;_blank&quot; href=&quot;https://support.microsoft.com/en-us/topic/support-for-urgent-trusted-root-updates-for-w[%E2%80%A6]te-program-in-windows-a4ac4d6c-7c62-3b6e-dfd2-377982bf3ea5&quot;&gt;https://support.microsoft.com/en-us/topic/support-for-urgent-trusted-root-updates-for-w[…]te-program-in-windows-a4ac4d6c-7c62-3b6e-dfd2-377982bf3ea5&lt;/a&gt;). If you have any questions, please reach out to your Technical Account Manager or Vivox Support here (&lt;a target=&quot;_blank&quot; href=&quot;https://support.unity.com/hc/en-us/requests/new?ticket_form_id=360003199531).%22&quot;&gt;https://support.unity.com/hc/en-us/requests/new?ticket_form_id=360003199531).”&lt;/a&gt;&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/371763</id>
    <published>2026-05-12T17:22:00Z</published>
    <category term="event:end" label="2026-05-12T17:26:00Z"/>
    <updated>2026-05-12T17:28:28Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/371763"/>
    <title>Vivox DDOS service issues</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Comms and Safety, Vivox, mt1p Domain&lt;/p&gt;&lt;p&gt;&lt;small&gt;May 12, 2026 · 22:54 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Retroactive&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
DDOS affected signalling services on mt1p environment, its resolved now&lt;/p&gt;
&lt;p&gt;
Impact window :  &lt;br /&gt;
Drop started     17:22 UTC  &lt;br /&gt;
Usage recovery 17:26 UTC&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;
Vivox Operations  &lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/371350</id>
    <published>2026-05-09T08:37:00Z</published>
    <category term="event:end" label="2026-05-11T16:46:28Z"/>
    <updated>2026-05-11T16:46:28Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/371350"/>
    <title>Order fulfillment outage on Commerce platform</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Major incident&lt;/strong&gt; - Websites, Unity Dashboard, Unity Store&lt;/p&gt;&lt;p&gt;&lt;small&gt;May 11, 2026 · 16:46 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The incident has been resolved and we are monitoring the situation.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;May 11, 2026 · 16:41 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Update&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Root cause was found and fixed all pending events were reprocessed&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;May 11, 2026 · 09:37 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are currently investigating issues related to orders not being fulfilled that customers are placing for purchases and cancellation as one of partner systems is down. Our engineering team is actively triaging the situation, and we will provide an update as soon as we have more information.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/370959</id>
    <published>2026-05-08T10:02:00Z</published>
    <category term="event:end" label="2026-05-08T14:27:06Z"/>
    <updated>2026-05-08T14:27:06Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/370959"/>
    <title>[Build Automation] Project Statistics &amp; Build Target Errors</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Major incident&lt;/strong&gt; - Collaboration / Unity DevOps, Unity Build Automation, Backend Service, Queue Performance - Mac Builders, Queue Performance - Windows Builders, License Activations - Unity Editor, Cost &amp; Usage Reporting&lt;/p&gt;&lt;p&gt;&lt;small&gt;May  8, 2026 · 14:26 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The incident has been resolved. Apologies for the inconvenience. &lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;May  8, 2026 · 12:28 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Monitoring&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We have identified an issue that we believe is responsible for the Project Statistics &amp; Build Target errors on the Build Automation service. A fix has been deployed, and pages previously displaying errors are functioning as expected again. &lt;/p&gt;
&lt;p&gt;
Our engineering team is actively monitoring the service, and will post further updates. &lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;May  8, 2026 · 10:19 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are currently investigating an issue. Our engineering team is actively triaging the situation, and we will provide an update as soon as we have more information.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/370159</id>
    <published>2026-05-04T14:47:32Z</published>
    <category term="event:end" label="2026-05-04T17:26:22Z"/>
    <updated>2026-05-04T17:26:22Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/370159"/>
    <title>Automation Creation and Pipeline Triggering Unavailable</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Major incident&lt;/strong&gt; - Collaboration / Unity DevOps, Unity Pipeline Automation, Backend Service, Event Processing&lt;/p&gt;&lt;p&gt;&lt;small&gt;May  4, 2026 · 17:24 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
The issue affecting automation creation and pipeline triggering has been resolved. &lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;May  4, 2026 · 14:47 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Issue&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are currently experiencing an issue where automation creation and pipeline triggering is not working. Our team is aware and actively investigating.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/363921</id>
    <published>2026-05-02T21:00:00Z</published>
    <category term="event:end" label="2026-05-02T21:00:00Z"/>
    <updated>2026-04-04T21:00:15Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/363921"/>
    <title>Unity Build Automation Scheduled Maintenance</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Scheduled maintenance&lt;/strong&gt; - Collaboration / Unity DevOps, Unity Build Automation, Backend Service, Queue Performance - Mac Builders, Queue Performance - Windows Builders, License Activations - Unity Editor, Cost &amp; Usage Reporting&lt;/p&gt;&lt;p&gt;&lt;small&gt;April  4, 2026 · 21:00 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Scheduled&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Team Unity Build Automation will be performing scheduled maintenance on a recurring basis. Please expect minor disruptions to the services during these times. We appreciate your patience and understanding as we work to improve our services. We thank you for your cooperation.&lt;/p&gt;
</content>
  </entry>
  <entry>
    <id>tag:status.unity.com,2005:/Incident/369211</id>
    <published>2026-04-27T14:00:00Z</published>
    <category term="event:end" label="2026-04-30T10:29:39Z"/>
    <updated>2026-04-30T10:29:39Z</updated>
    <link rel="alternate" type="text/html" href="https://status.unity.com/incidents/369211"/>
    <title>Cost &amp; Usage dashboard reporting inaccuracies for Unity DevOps</title>
    <content type="html">&lt;p&gt;&lt;strong&gt;Minor incident&lt;/strong&gt; - Collaboration / Unity DevOps, Unity Build Automation, Cost &amp; Usage Reporting, Unity Pipeline Automation, Cost &amp; Usage Reporting, Unity Version Control, Cost &amp; Usage Reporting&lt;/p&gt;&lt;p&gt;&lt;small&gt;April 28, 2026 · 14:04 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
We are currently investigating an issue affecting Seats and Concurrency usage reporting for March, and April 2026. As a result, usage values may be displayed inaccurately in the dashboard.&lt;/p&gt;
&lt;p&gt;
Please note that March invoices remain accurate. April invoices will be corrected before charges are finalized.&lt;/p&gt;
&lt;hr&gt;&lt;p&gt;&lt;small&gt;April 24, 2026 · 18:27 UTC&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;
Usage values are back to normal. The march invoices were calculated with accurate information, guaranteeing that there were no overcharges.&lt;/p&gt;
&lt;p&gt;
The reporting charts are also showing accurate information, which reflect the actual storage usage of your DevOps subscriptions.&lt;/p&gt;
</content>
  </entry>
</feed>