.
@NotionHQ
's issue is a good reminder that
It's a best practice to use a separate domain for your status page 🤯
Why? When you face DNS issues, your status page will remain up & running 😼
Hope they're able to recover soon 💪
Your status page should be on a different domain
Your status page should be on a different domain
Your status page should be on a different domain
Your status page should be on a different domain
Your status page should be on a different domain
Great UX is not a nice-to-have, it's a must-have!
It can make or break your brand and determine the success of your product.
Build things that people love!
Just when I thought I had all the time in the world to finish my work, a wild Windows update appears and reminds me that nothing is guaranteed in life.
There are currently issues if you're creating a new status page (+ some other scenarios)
Currently working to fix it!
For more info and updates, please check our status page
Will upgrade our backend tech to
@Prisma
2 on 11:00 PM GMT+0. It'll take ~30 mins.
Your status pages will continue to work fine, but you won't be able to update them during that time.
👉
We've been experiencing outages across Twitter and TweetDeck. You might have had trouble Tweeting, getting notifications, or viewing DMs. We're currently working on a fix, and should be back to normal soon.
@PlausibleHQ
@theEagleStatus
Hi
@PlausibleHQ
You may do this by editing the component status, as well as the main status.
Since that's an automated incident, would you please DM me the monitoring integration you're using so that I can make sure this doesn't happen again?
Identified: There are currently issues with reaching Vercel deployments from China. Since our status pages are hosted on Vercel, we're facing the same issue