# Yesterday’s downtime

> Yesterday, Asana had a service interruption for approximately 90 minutes. We want to apologize because we know your team relies on Asana.

Source: https://asana.com/inside-asana/yesterdays-downtime

## Yesterday’s downtime

**Check our**[status page](https://trust.asana.com/)**and**[Twitter](https://twitter.com/asana)**for up-to-date information.**

Asana had a service interruption for approximately 90 minutes on Wednesday. We want to apologize, as we know your team relies on Asana and lengthy outages can majorly disrupt your workflow. It is our top priority to ensure Asana is up and running securely for you and your team, and we take these issues very seriously.

Whenever Asana is down or experiencing performance issues, we immediately dedicate engineers to fix the problem. We also aim to keep you as informed as possible–**you can always check our**[status page](https://trust.asana.com/)**and**[Twitter](https://twitter.com/asana)**for up-to-date information**. We also work to identify the root cause, so we can prevent the same issue from happening again.

We’re still investigating this outage, but we believe the root cause is related to transient connectivity issues between our app servers and database/cache servers. The most important complications we experienced yesterday have been resolved, so we don’t expect another serious interruption. However, the underlying network connectivity issue remains, and we are working closely with AWS to address the issue. This will be our top priority until it is fully resolved. Looking ahead, we do agree that offline access to Asana would be helpful, and this is on our long-term roadmap.

We apologize for the downtime yesterday. Thanks for your patience.

- [Improving Asana’s Pageload Performance](/inside-asana/improving-asanas-pageload-performance)

Engineering

#### Senior Engineering Manager

Asana serves 2.5 million pageloads a day, peaking at 3.5 million. Each one is a user's first impression of the product — the moment between intent and action — and for a tool team ...

- [How Asana Built A Resilient ID Allocation System](/inside-asana/how-asana-built-resilient-id-allocation)

Engineering

Every object in Asana—every task, project, comment, and attachment—needs a unique identifier. At Asana, these IDs are sequentially incrementing integers, allocated in blocks from ...

- [The Athletic Position](/inside-asana/the-athletic-position)

Engineering

I. Before the Ball Leaves their StringsThere is a moment from the 1988 French Open final that most people who talk about tennis haven’t had to think about carefully.Steffi Graf pl ...

- [How Asana leverages AWS Inspector for total visibility over infrastructure vulnerabilities](/inside-asana/asana-leverages-aws-inspector-visibility-infrastructure-vulnerabilities)

Engineering

#### Software Engineer

Scanning for vulnerabilities across multiple AWS accounts, eliminating noise, and turning vulnerability findings into actionable work is a challenging but important undertaking. A ...

- [Yesterday’s downtime](/inside-asana/yesterdays-downtime)

Engineering

Check our status page and Twitter for up-to-date information.Asana had a service interruption for approximately 90 minutes on Wednesday. We want to apologize, as we know your team ...

- [Engineering](/inside-asana/engineering-spotlight)