Vendor Status Watch

← all vendors

Atlassian Access status history

Current state: operational — “All Systems Operational” per https://access.status.atlassian.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

0incidents, last 30 days
0incidents, last 90 days
11incidents on record

How long do Atlassian Access incidents last?

2.8 hmedian incident duration11 measured
21.5 h90th percentile1 in 10 ran longer
104 minmedian, major/critical only5 incidents

From 11 incidents with a vendor-posted start and resolve time. Longest on record: 2FA, Password reset, OTP, and verification emails being quarantined — 3.2 days (2025-11-13 18:56 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (11)

StartedIncidentStatusImpactDuration
2026-05-14 05:11 UTCUsers experiencing issues accessing multiple Atlassian productspostmortemcritical1 h 37 min
2026-05-08 01:31 UTCMultiple Atlassian services are experiencing issuespostmortemminor18 h 13 min
2026-04-13 07:29 UTCUsers experiencing issues with login across Atlassian productspostmortemminor2 h 47 min
2026-04-08 06:01 UTCMultiple products impacted by search failurespostmortemcritical5 h 41 min
2026-02-18 11:28 UTCGroups are not clickable from Groups Page in Atlassian Administrationresolvedminor2 min
2025-12-27 04:42 UTCOutbound Email, Mobile Push Notifications, and Support Ticket Delivery Impacting All Cloud Productspostmortemcritical37 min
2025-12-15 20:23 UTCDisrupted Guard availability for US Prod Eastresolvedcritical1 h 44 min
2025-12-15 16:16 UTCDegraded performance of Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovoresolvedminor2 h 45 min
2025-11-13 18:56 UTC2FA, Password reset, OTP, and verification emails being quarantinedresolvednone3 d 5 h
2025-10-20 07:56 UTCAtlassian Cloud Services impactedpostmortemmajor21 h 28 min
2025-09-22 05:59 UTCDegraded performance to multiple Atlassian experiencespostmortemminor1 h 17 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Atlassian Access with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "atlassian-access"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}