Operational Loom status
loom.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
Loom looks fine itself, but Amazon Web Services, a provider it may run on (inferred), reports major outage. Watch for knock-on effects.
confidence: low Vendor: operational · users: normal · routing: no data · upstream providers: major.
- Vendor status page Operational · 10 open incidents
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) Amazon Web Services: Major outage
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Recording, Viewing, Authentication
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 585 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “Multiple Atlassian services are experiencing issues”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
- Amazon Web Services reports an issue. Loom may depend on it (inferred from public sources). Coincidence, not causation. evidence confidence: low
What we don't know: what is happening inside Loom's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.
Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data · upstream providers: major. Vendor status and outside signals roughly agree.
Who depends on whom
Loom may run on Amazon Web Services (inferred). We don't map other services that depend on Loom. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Loom or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Loom. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Multiple Atlassian services are experiencing issues
minor resolved · started · resolved
10 updates
- investigating
We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.
- identified
We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.
- identified
Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.
- identified
We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.
- identified
Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.
- identified
We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each product page.
- monitoring
The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.
- monitoring
We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.
- monitoring
Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team. We apologise for the disruption and thank you for your patience.
- resolved
On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.