Status pages

Instability with status pages (free plan)

We are working on a fix for this incident.

We are working on a fix for this incident.

We resolved this issue. 
Currently monitoring the results and working on long term solutions for it.

We resolved this issue. 
Currently monitoring the results and working on long term solutions for it.

Dashboard

Issues affecting dashboard access and incident listings

We recently migrated the dashboard to <a href="https://dashboard.instatus.com" rel="noopener noreferrer" target="_blank">dashboard.instatus.com</a>
This introduced some issues with dashboard login, and the dashboard incidents list 
If you're affected, we advise you to please try clearing your browser cookies (ones that have .instatus.com domain)
We're currently working on resolving the issues, in order to make the dashboard experience seamless for everyone

We recently migrated the dashboard to [dashboard.instatus.com](https://dashboard.instatus.com)
This introduced some issues with dashboard login, and the dashboard incidents list 

If you're affected, we advise you to please try clearing your browser cookies (ones that have .instatus.com domain)

We're currently working on resolving the issues, in order to make the dashboard experience seamless for everyone

We implemented a fix, and monitoring to see if the issues are 100% over

We implemented a fix, and monitoring to see if the issues are 100% over

Issues affecting some status page subdomains on the free plan

We just fixed the issue for all pages!
If you're still facing it with your page, kindly contact <a href="mailto:support@instatus.com" rel="noopener noreferrer" target="_blank">support@instatus.com</a> or <a href="https://instatus.com/chat" rel="noopener noreferrer" target="_blank">chat with us on slack</a>

We just fixed the issue for all pages!

If you're still facing it with your page, kindly contact [support@instatus.com](mailto:support@instatus.com) or [chat with us on slack](https://instatus.com/chat)

No news is good news! Seems like it's resolved for everyone!
Behind the scenes:
Previously we moved free status pages from Vercel to AWS, due to high serverless function usage on Vercel.
Recently, Next.js <a href="https://nextjs.org/blog/next-12-1?utm_source=next-site&utm_medium=banner&utm_campaign=next-website" rel="noopener noreferrer" target="_blank">12.1</a> was released with on-demand ISR, which meant we could use less serverless functions. 
An opportunity to move everyone back to Vercel and provide a superior user experience for everyone. 
As we moved free status pages back to Vercel, some subdomains just didn't work as expected. It was around 10% of free status pages.
We contacted Vercel and they responded that there were remaining aliases from these subdomains that pointed to (now) deleted projects. So, we deleted these aliases, and everything is now up and running! 🚀

No news is good news! Seems like it's resolved for everyone!

**Behind the scenes:**

Previously we moved free status pages from Vercel to AWS, due to high serverless function usage on Vercel.

Recently, Next.js [12.1](https://nextjs.org/blog/next-12-1?utm_source=next-site&utm_medium=banner&utm_campaign=next-website) was released with on-demand ISR, which meant we could use less serverless functions. 

An opportunity to move everyone back to Vercel and provide a superior user experience for everyone. 

As we moved free status pages back to Vercel, some subdomains just didn't work as expected. It was around 10% of free status pages.

We contacted Vercel and they responded that there were remaining aliases from these subdomains that pointed to (now) deleted projects. So, we deleted these aliases, and everything is now up and running! 🚀

There's an issue where some status page subdomains don't resolve correctly to *.instatus.com. 
This is affecting some customers who use the free plan.
We're currently working on it and will update you once we fix it.
If you happen to be affected, you can get it back early by contacting <a href="mailto:support@instatus.com" rel="noopener noreferrer" target="_blank">support@instatus.com</a> or chat on slack at <a href="https://instatus.com/chat" rel="noopener noreferrer" target="_blank">instatus.com/chat</a>

There's an issue where some status page subdomains don't resolve correctly to *.instatus.com. 
This is affecting some customers who use the free plan.

We're currently working on it and will update you once we fix it.

If you happen to be affected, you can get it back early by contacting [support@instatus.com](mailto:support@instatus.com) or chat on slack at [instatus.com/chat](https://instatus.com/chat)

All systems operational

Recent notices