ur Atlassian Cloud site has been failing on all REST API requests (Jira and Confluence both) continuously for
over 3 days now — first observed 2026-11-16, still failing as of 2026-11-19. The web UI works fine when logged in
via browser, so this looks scoped to the API/edge path specifically, not a full site outage — and it's not
reflected as an incident on status.atlassian.com, which currently shows "All Systems Operational."
We're on the Free plan, so we don't have access to a support ticket queue — posting here in case anyone from
Atlassian or the community has seen this before or can point us in the right direction.
Symptom: Every API request (bare GET to the site root, /wiki, /rest/api/3/myself, /rest/api/3/issue/...) returns:
HTTP/2 404
{"errorMessage": "Site temporarily unavailable", "errorCode": "OTHER"}
Diagnostics gathered:
- TLS/HTTP2 handshake succeeds normally with a valid *.atlassian.net certificate — not a network/DNS/TLS issue on our end.
- server: AtlassianEdge, x-cache: Error from cloudfront — the error is generated at the CDN edge, not forwarded from an origin/application error.
- atl-missing-tcs: true — suggests the edge cannot resolve tenant context for our site specifically.
- x-amz-cf-pop: MUC50-P3 — routed to the expected nearby (Munich) edge, so not a routing/geo anomaly.
- Example trace IDs from one failed request:
- atl-traceid: 870c88d012bb49d08bf13eae061c7997
- atl-request-id: 870c88d0-12bb-49d0-8bf1-3eae061c7997
- The failure is 100% consistent and reproducible — dozens of retries across 3+ days, same result every time, no intermittent success.
Has anyone else hit atl-missing-tcs before, or know whether this is something Atlassian staff can look into from a community post? Happy to provide more trace IDs if useful.