Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

May 15, 2026

  1. JamfJamf School: Degraded Performance (EU-Central)

    The interruption with Jamf School has been resolved. This issue effected read speed with our database. We apologize for any inconvenience. Customer Impact: General slowness of Jamf School application in the European cluster.

    Resolved

  2. New RelicUI and Data Irregularities - US Region

    Between 22:30 UTC on May 14th and 01:00 UTC on May 15th, 2026, some customers in the US region may have experienced issues loading different pages in the New Relic UI. Some customers may have also experienced delayed data in queries, charts, and dashboards. Data ingest and alerts were not impacted. We resolved this issue and the above services have returned to normal operation.

    Resolved

May 14, 2026

  1. DigitalOceanDNS service, Certificates and Managed MongoDB

    As of 19:50 UTC, the issue affecting the DNS service has been fully resolved, and all related services, including Let's Encrypt certificate issuance and Managed MongoDB provisioning, are now operating normally. The backlog of delayed requests has been successfully processed, and all DNS record updates, pending certificate, and MongoDB operations should now be complete. We apologize for the disruption this caused and appreciate your patience while our team worked to restore full functionality. However, if you continue to experience any issues, please don't hesitate to raise a support ticket for further investigation. We'll be happy to assist you.

    Resolved

  2. JiraThe Work Item view experience of Jira is restored

    ### SUMMARY ### Between May 1, 2026 at 23:34 UTC and May 2, 2026 at 02:53 UTC Atlassian customers using Jira and Jira Service Management (JSM) across all Cloud tenants received an error page when attempting to open a work item due to a schema incompatibility, and editing work item fields was degraded for both products. Navigating to and interacting with boards were degraded for Jira specifically. On Jira mobile, users were unable to view work items and work item search was degraded. This was caused by a deployment of a schema configuration change that had only been validated against some production environments. The issue also affected Atlassian's customer support operations and temporarily impacted Atlassian’s ability to respond to incoming support requests. Customers were able to raise tickets as usual. Atlassian’s automated monitoring systems detected the issue on May 1, 2026 at 23:41 UTC, and engineering teams promptly began investigating. The issue was reported on Statuspage on May 2, 2026 at 00:55 UTC. The issue was resolved after 3 hours and 19 minutes on May 2, 2026 at 02:53 UTC when the previous version of the schema configuration was successfully redeployed to all regions. ### IMPACT ### - **Duration**: 3 hours 19 minutes (May 1, 2026 at 23:34 UTC – May 2, 2026 at 02:53 UTC) - **Affected regions**: All regions. - **Affected products**: Jira, JSM, Jira Mobile - **Customer experience**: - Users were unable to view work items using the work item view; consequently updating and creating work items from the work item view was affected. - Editing work items was degraded. - Boards did not show under Spaces in the Jira navigation. - Certain board interactions were affected. - Other areas of Jira not dependent on the broken schema configuration continued to operate normally. ### ### ROOT CAUSE ### The root cause was a deployment sequencing issue. A schema configuration change was deployed to the API gateway layer before the corresponding application-level change had been deployed across all production environments. This created a mismatch between the schema expected by the gateway and the schema served by the application servers. ### ### MITIGATIONS ### The engineering team identified the problematic schema change and initiated a rollback of the deployment. A deployment blocker was put in place to prevent further changes while the rollback was executed. The previous version of the schema configuration was redeployed, and service was restored across all regions. ### ### REMEDIAL ACTION PLAN & NEXT STEPS ### We understand that service disruptions impact your productivity. In addition to our existing testing and preventative processes, Atlassian is prioritizing the following actions to help reduce the likelihood and impact of similar incidents in the future and to speed up recovery when issues occur: - We are adding automated pre-deployment checks to verify that schema configurations are compatible across all production environments before changes are deployed. - We will streamline our incident communication processes, incident response training and tooling to reduce the time between incident detection and customer notification. - We are working to improve resilience of critical customer-facing support services to ensure SLA continuity during outages. We apologize to customers whose services were impacted during this incident. We are taking immediate steps to reduce the risk and impact of similar issues in future. Thanks, Atlassian

    Resolved

  3. CircleCIElevated 429 errors pulling from maven central

    Customers running jobs that pulled dependencies from Maven Central experienced elevated 429 (rate limit) errors. We have worked with Sonatype to allow list CircleCI's dedicated IP ranges. Customers using our IP ranges feature should no longer see Maven Central rate limits affect their jobs while we continue work to fully address the issue for all customers. Customers whose jobs failed during this window may rerun affected jobs. We thank you for your patience while our team worked on implementing a fix.

    Resolved

  4. Epic GamesEAS Auth Access Token with additional claims

    We have rolled back a change to our backend that included additional claims in the EAS Auth Access token. This change could break the login flow in some games that allocated a fixed-size buffer to the access token.

    Resolved

  5. UpstashUpstash Redis – intermittent connection issues in some regions

    Earlier today, unexpected load on our proxies caused intermittent connection issues for Upstash Redis in the following regions: us-east-1, us-west-1, ap-southeast-2, and ap-south-1. During this period, some clients may have seen connection timeouts or elevated error rates when reaching their databases. Our team identified the issue quickly and applied workarounds to relieve pressure on the affected proxies. Connection health has since been restored and we've been monitoring the regions to confirm everything is stable. All systems are now operating normally. We appreciate your patience and apologize for any disruption this may have caused.

    Resolved

  6. Epic GamesV-Bucks Delivery Delayed

    Players who saw a delay in receiving V-Bucks should now have them available. As part of this fix, players who qualify for the Showdown Umbrella styles introduced in today's update may see them granted at a later date.

    Resolved

  7. LinearDegraded Slack integration performance

    This incident has been resolved. Linear Asks, Slack, and Slack agent functionality should now be operating normally after the upstream provider issue was fixed.

    Resolved

  8. SlackIssues affecting file uploads, message edits, channel renames, and channel creations

    The issue affecting multiple features, including file uploads, message edits, and channel management, has been resolved. A fix has been fully deployed, and all systems are functioning normally. If you are still experiencing any trouble, please perform a hard reload of Slack by pressing Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). Mobile users should fully close and relaunch the app. We sincerely apologize for the disruption to your day and appreciate your patience while we worked to sort this out.

    Resolved

  9. LinodeConnectivity Issue - AP-West (Mumbai) and IN-MAA (Chennai)

    On May 12, 2026, at approximately 14:50 UTC, Akamai began experiencing congestion and packet loss affecting traffic between India and Europe over Internet Service Provider network paths servicing our Mumbai and Chennai data centers. Customers may have seen intermittent connection timeouts and errors in the affected regions. The issue was due to congestion on transit paths between India and Europe. Akamai worked with the involved Internet Service Providers and their upstream providers to identify the cause. To mitigate the impact, Akamai redirected traffic away from the affected paths, stabilizing service while the investigation continued. Service was restored at the Mumbai data center at 19:23 UTC on May 12, 2026, and at the Chennai data center at 00:25 UTC on May 13, 2026. Akamai will continue working with the involved Internet Service Providers to address the underlying congestion and help prevent recurrence. This summary reflects our current understanding of the incident based on available information. Our investigation is ongoing, and details may change as we learn more.

    Resolved

  10. SnowflakeINC0157155

    <b>Current status:</b> After investigating, we've determined this to be a false positive. There were no customer replication refresh operations impacted. We've confirmed replication services are functioning normally. If you experience issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight.

    Resolved

May 13, 2026

Older incidents