Atlassian Status · History · Incident #52
RESOLVEDIssues with 403 user authentication errors across Atlassian products
Minor · Started Mar 4, 2025 · 7:31 AM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Atlassian Status · History · Incident #52
RESOLVEDMinor · Started Mar 4, 2025 · 7:31 AM
Duration
< 1m
Severity
Minor
Detection lead
—
User reports
—
Summary
We are aware of an issue that was impacting user authentication to Atlassian services between 6:10AM Tuesday 4th March UTC and 6:35AM Tuesday 4th March UTC. Users that were already logged in would not have been impacted by this issue. A deployment suspected of causing this issue was rolled back and the problem was subsequently resolved.
Started
Mar 4, 2025 · 7:31 AM
Resolved
Mar 4, 2025 · 7:31 AM
Duration
< 1m
Severity
None
Event timeline
Resolved
Mar 4 · 7:31 AM AtlassianWe are aware of an issue that was impacting user authentication to Atlassian services between 6:10AM Tuesday 4th March UTC and 6:35AM Tuesday 4th March UTC. Users that were already logged in would not have been impacted by this issue. A deployment suspected of causing this issue was rolled back and the problem was subsequently resolved.
Pattern
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime. Try Free
Made by Designmodo
MONITORING
SERVICE
COMPARE
ACCOUNT