Deprecated: Function get_magic_quotes_gpc() is deprecated in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 99

Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 619

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1169

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176

Warning: Cannot modify header information - headers already sent by (output started at /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php:99) in /hermes/walnacweb04/walnacweb04ab/b2791/pow.jasaeld/htdocs/De1337/nothing/index.php on line 1176
Atlassian Support Status
Nothing Special   »   [go: up one dir, main page]

Update - The issue relating to the Atlassian Support portal displaying a message to customers to use our temporary support channel has now been resolved. The Atlassian Support portal is fully functional for any ongoing support issues.

With regards to other Atlassian products, we continue to see recovery continuing across all impacted products and our teams are continuing to monitor as the recovery continues.

We will provide further update on our recovery status within two hours.

Oct 21, 2025 - 03:24 UTC
Update - We continue to see recovery progressing across all impacted products as backlogged items continue to be processed.

The Atlassian Support portal is currently displaying a message directing customers to our temporary support channel. Please note that our support portal is currently fully functional for those attempting to raise requests. We are continuing to look into this alert to remove this message.

We will provide further update on our recovery status in two hours.

Oct 21, 2025 - 01:07 UTC
Update - Our team is now seeing recovery across all impacted Atlassian products. We are continuing to monitor for individual products that may still be processing backlogged items now that services are restored.

The Atlassian Support portal is currently still displaying a message directing customers to our temporary support channel. Please note that our support portal is currently fully functional for those attempting to raise requests. We are continuing to look into this alert to remove this message.

We will provide further update on our recovery status in one hour.

Oct 21, 2025 - 00:03 UTC
Update - Our teams are continuing to monitor the recovery of systems across Atlassian products. This update is to inform that the Atlassian Support portal is fully operational at this time for customers that wish to contact support.
Oct 20, 2025 - 22:58 UTC
Update - Monitoring - We've started seeing continued product experience improvement.

While we still have a backlog of event processing, we are seeing improvements in systems operational capabilities across all products. We estimate a significant improvement with the next few hours and will continue to monitor the health of AWS services and the effects on Atlassian customers. We appreciate your continued patience and remain committed to full resolution as we work through this situation. We will post our next update in two hours.

Oct 20, 2025 - 21:26 UTC
Monitoring - There have been no changes since our last update. We will provide our next updated by 9:00PM UTC or sooner as new information becomes available.

We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority and we are closely monitoring the health of AWS services. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation.

Oct 20, 2025 - 18:38 UTC
Update - We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority and we are closely monitoring the health of AWS services. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available.
Oct 20, 2025 - 17:43 UTC
Update - Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available.
Oct 20, 2025 - 17:27 UTC
Update - Update - Thank you for your continued patience. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is still actively working to mitigate this issue with urgency and while we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will be providing hourly updates on this issue.
Oct 20, 2025 - 16:36 UTC
Update - Update - Thank you for your continued patience. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is still actively working to mitigate this issue with urgency and while we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will be providing hourly updates on this issue.
Oct 20, 2025 - 16:35 UTC
Update - Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available.
Oct 20, 2025 - 15:21 UTC
Update - We understand your pain and mitigating or fixing this issue is of utmost importance. Our public cloud provider is actively working to mitigate this issue on priority. We have been seeing partial operational success. We appreciate your patience and will continue to provide updates every hour or sooner.
Oct 20, 2025 - 14:02 UTC
Update - Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.
Oct 20, 2025 - 13:58 UTC
Update - Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.
Oct 20, 2025 - 13:56 UTC
Update - Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.
Oct 20, 2025 - 13:07 UTC
Update - Atlassian team is actively engaged and continues to work with our public cloud provider to mitigate this issue at the earliest. We are starting to see partial operations succeed. We appreciate your patience. We shall continue to share updates every hour, if not sooner.
Oct 20, 2025 - 12:06 UTC
Update - We continue to work with our public cloud provider towards mitigating the issue at the earliest. We appreciate your patience. We shall continue to share updates every hour, if not sooner.
Oct 20, 2025 - 11:07 UTC
Identified - We understand that our public cloud provider has identified the cause of the issue. We are starting to see some recovery and is working towards mitigation. We appreciate your patience.
We shall continue to share updates every hour, if not sooner.

Oct 20, 2025 - 09:58 UTC
Update - We are experiencing an outage due to some issue at the end of our public cloud provider. We are working closely with them to get this resolved or mitigated as quickly as possible. ETA of the same is not know at the moment.
We shall continue to share updates every hour, if not sooner.

Oct 20, 2025 - 09:24 UTC
Update - We are experiencing an outage due to some issue at the end of our public cloud provider. We are working closely with them to get this resolved or mitigated as quickly as possible. ETA of the same is not know at the moment.
We shall continue to share updates every hour, if not sooner.

Oct 20, 2025 - 09:23 UTC
Update - Atlassian Cloud services are impacted and we are aware that our customers might not be able to create support tickets. Our teams are actively investigating the same.
We shall keep you informed of the progress every hour.

Oct 20, 2025 - 08:24 UTC
Investigating - We have noticed that Atlassian Cloud services are impacted and our teams are actively investigating the same.
We shall keep you informed of the progress every hour.

Oct 20, 2025 - 07:56 UTC

About This Site

Here we will post updates about Atlassian Support's service availability. For status information about other Atlassian products or services, please visit the Atlassian status page.

Support Portal Operational
90 days ago
99.72 % uptime
Today
Ticketing Operational
90 days ago
99.79 % uptime
Today
Knowledge Base Operational
90 days ago
99.79 % uptime
Today
Community Operational
90 days ago
99.79 % uptime
Today
API Docs Operational
90 days ago
99.79 % uptime
Today
Public Issues Tracker ? Operational
90 days ago
99.79 % uptime
Today
Training ? Operational
90 days ago
99.79 % uptime
Today
Blogs Operational
90 days ago
99.79 % uptime
Today
Careers Operational
90 days ago
99.79 % uptime
Today
Content Delivery Operational
90 days ago
99.79 % uptime
Today
Search Operational
90 days ago
99.79 % uptime
Today
Downloads Access Operational
90 days ago
99.56 % uptime
Today
Preferences Center ? Operational
90 days ago
99.79 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Oct 21, 2025

Unresolved incident: Atlassian Cloud Services impacted.

Oct 20, 2025
Oct 19, 2025

No incidents reported.

Oct 18, 2025

No incidents reported.

Oct 17, 2025

No incidents reported.

Oct 16, 2025

No incidents reported.

Oct 15, 2025

No incidents reported.

Oct 14, 2025

No incidents reported.

Oct 13, 2025

No incidents reported.

Oct 12, 2025

No incidents reported.

Oct 11, 2025

No incidents reported.

Oct 10, 2025

No incidents reported.

Oct 9, 2025
Resolved - We have resolved the incident. A new version of the Loom chrome extension has been approved and published to the Chrome Extension store. Update to the latest version(v5.5.142) of the extension.
Oct 9, 20:00 UTC
Identified - We have identified an issue starting at 17:00 UTC on Monday, October 6th, 2025 affecting all Loom users who record videos with the Chrome Extension, causing unexpected delays when saving videos. If the browser is closed before the video is playable, the recording may be lost.

To address this, we have developed an updated version of the extension, which is currently under review by Google. We anticipate the fix to be published by 20:00 UTC on October 15th, 2025, or sooner. In the meantime, users will see an in-browser message if their video has not yet been saved, advising them not to close the browser session.

We will provide an update again when the fix is available.

Oct 8, 22:20 UTC
Oct 8, 2025
Resolved - We are closing this incident on Statuspage as the Atlassian Support portal functionality has been restored.

We are aware that the ticket attachments panel remains unavailable and that some customers may be receiving a 'Something went wrong!' error message despite successfully uploading ticket attachments. We are working to resolve these UX issues. Atlassian Support is available for customers needing further assistance.

Oct 8, 02:18 UTC
Update - Our teams are continuing to make progress and are actively working on finalizing the deployment plan for fixes to address this issue.

Meanwhile, customers can upload attachments but may see an error message and cannot view the attachment list. Shortly after uploading, they will see a comment on their ticket confirming the attachment was added. Customers do not need to take extra steps; our Support team can access the attachments. The rest of the support portal is working normally. We appreciate your patience and will provide a further update by October 8th, 01:00 UTC, if not sooner.

Oct 7, 21:02 UTC
Identified - Our teams are continuing to make progress and are in the final stages of validating potential fixes to address this issue.

Meanwhile, customers can upload attachments but may see an error message and cannot view the attachment list. Shortly after uploading, they will see a comment on their ticket confirming the attachment was added. Customers do not need to take extra steps; our Support team can access the attachments. The rest of the support portal is working normally. We appreciate your patience and will provide a further update by October 7th, 21:00 UTC, if not sooner.

Oct 7, 18:04 UTC
Update - Atlassian teams have identified some likely root causes and are testing and simulating to confirm them. Once the root cause is confirmed, our teams will carefully conduct thorough checks before making any changes.

Meanwhile, customers can upload attachments but may see an error message and cannot view the attachment list. Shortly after uploading, they will see a comment on their ticket confirming the attachment was added. Customers do not need to take extra steps; our Support team can access the attachments.

The rest of the support portal is working normally. We appreciate your patience.
We will provide further update by October 7th 18:00 UTC, if not sooner.

Oct 7, 11:59 UTC
Update - We don't have any new update to share at this point. However, please be rest assured that out team is continuing to work to restore full attachment functionality.

Customers can upload attachments, but may receive an error message when doing so, and will not be able to view the attachment list at this time.
Soon after uploading, they will see a comment on their ticket that the attachment was added. Customers do not need to take additional upload steps, and our Support team will be able to access the attachment.
The rest of the support portal is working as expected. Thank you for your patience. We will provide further update by October 7th 12:00 UTC, if not sooner.

Oct 7, 08:28 UTC
Update - No change since our previous update. Our team is continuing to work to restore full attachment functionality.

Customers can upload attachments, but may receive an error message when doing so, and will not be able to view the attachment list at this time.
Soon after uploading, they will see a comment on their ticket that the attachment was added. Customers do not need to take additional upload steps, and our Support team will be able to access the attachment.

The rest of the support portal is working as expected. Thank you for your patience. We will provide further update by October 7th 08:00 UTC, if not sooner.

Oct 7, 04:01 UTC
Update - No change since our last update. We are continuing to work to restore full attachment functionality.

Customers can upload attachments, but may receive an error message when doing so, and will not be able to view the attachment list at this time. However, soon after uploading, they will see a comment on their ticket that the attachment was added. Customers do not need to take additional upload steps, and our Support team will be able to access the attachment.

The rest of the support portal is working as expected. Thank you for your patience. We will provide an update by October 7th 04:00 UTC, if not sooner.

Oct 6, 22:00 UTC
Update - No change since our last update. We are continuing to work to restore full attachment functionality.

Customers can upload attachments, but may receive an error message when doing so, and will not be able to view the attachment list at this time. However, soon after uploading, they will see a comment on their ticket that the attachment was added. Customers do not need to take additional upload steps, and our Support team will be able to access the attachment.

The rest of the support portal is working as expected. Thank you for your patience. We will provide an update by 22:00 UTC, if not sooner.

Oct 6, 18:58 UTC
Update - No change since our last update. We are continuing to work to restore full attachment functionality.

Customers can upload attachments, but may receive an error message when doing so, and will not be able to view the attachment list at this time. However, soon after uploading, they will see a comment on their ticket that the attachment was added. Customers do not need to take additional upload steps, and our Support team will be able to access the attachment.

The rest of the support portal is working as expected. Thank you for your patience. We will provide an update by 19:00 UTC, if not sooner.

Oct 6, 17:54 UTC
Update - We continue to investigate to identify root cause of the issue. We have made changes to contain the issue to listing attachments for tickets. As a result of some mitigation changes, rest of the support portal is working as expected.

New attachments are getting uploaded and a comment is added in the support ticket indicating successful upload of the attachment. From the comment, customers can view the attachment (if required). Customers don't need to upload the attachment again.
Currently, the table/list of attachments to the support ticket is not visible to our customers and we continue to work to restore this functionality.
We will provide more details within the next hour.

Oct 6, 16:15 UTC
Update - Atlassian team is investigating the issues with viewing existing attachments and uploading attachments. We will provide more details within the next hour.
Oct 6, 15:01 UTC
Investigating - We are again seeing issues with uploading new attachments and viewing existing attachments. We will provide more details within the 2 hours.
Oct 6, 14:02 UTC
Monitoring - We have identified the root cause of partially impacting Atlassian support portal that led to the issue of visibility of the Support tickets and customers being unable to upload attachments. We have mitigated the problem and continue to monitoring the services closely.

There will be no further updates here until the status is changed to 'Resolved' unless the issue recurs.

Oct 6, 13:13 UTC
Identified - We have identified the cause of the issue and expect recovery shortly.
Oct 6, 13:02 UTC
Update - Our team continues to investigate the issue on priority.

Please note that support ticket creation is still working as expected. You can continue to interact with us by replying to the email you received when your support ticket was created.

Oct 6, 12:01 UTC
Update - Atlassian team continues to investigate the issue with utmost importance.

Please note that support ticket creation is still working as expected. You can continue to interact with us by replying to the email you received when your support ticket was created.

Oct 6, 11:01 UTC
Update - Our team is actively engaged and continuing to investigate issues with our Customer Support portal.

Please note that support ticket creation is still working as expected. You can continue to interact with us by replying to the email you received when your support ticket was created.

Oct 6, 10:01 UTC
Update - We are continuing to investigate issues with our Customer Support portal.

Please note that support ticket creation is still working as expected. You can continue to interact with us by replying to the email you received when your support ticket was created.

Oct 6, 09:02 UTC
Update - We are investigating the issue of being unable to view Support tickets and uploading attachments in Atlassian support portal. We will provide more details within the next hour.
Oct 6, 08:21 UTC
Update - We are continuing to see issues with customers uploading new attachments and viewing existing attachments. We have identified the root cause and work is underway to resolve the issue.
Oct 6, 07:04 UTC
Investigating - We are continuing to investigate the regression issue and we will provide more details once we identify the root cause.
Oct 6, 06:08 UTC
Monitoring - We identified that there was a temporary regression in our backend service health and we have mitigated the problem. We will continue to monitor the issue.
Oct 6, 04:49 UTC
Investigating - On further monitoring, we see the issue resurfacing so our team is actively investigating with urgency and we will provide an update as soon as possible. We apologise for any inconvenience caused by this issue.
Oct 6, 04:32 UTC
Monitoring - We have identified the root cause of the performance degraded service and have mitigated the problem. We are now monitoring closely.
Oct 6, 01:37 UTC
Investigating - We are investigating cases of degraded performance for attachments in the Customer Support portal. We will provide more details within the next hour.
Oct 6, 01:10 UTC
Oct 7, 2025