Instatus - История на известията

Всички системи работят

Public status pages - Работи

100% - достъпност
фев 2022 · 100.0%мар · 100.0%апр · 100.0%

Previous page

Next page

фев 2022
мар 2022
апр 2022

Private status pages - Работи

100% - достъпност
фев 2022 · 100.0%мар · 100.0%апр · 100.0%

Previous page

Next page

фев 2022
мар 2022
апр 2022

Uptime monitoring - Работи

100% - достъпност
фев 2022 · 100.0%мар · 100.0%апр · 100.0%

Previous page

Next page

фев 2022
мар 2022
апр 2022

Incident response - Работи

100% - достъпност
фев 2022 · 100.0%мар · 100.0%апр · 100.0%

Previous page

Next page

фев 2022
мар 2022
апр 2022

On-call - Работи

100% - достъпност
фев 2022 · 100.0%мар · 100.0%апр · 100.0%

Previous page

Next page

фев 2022
мар 2022
апр 2022

Slack app - Работи

100% - достъпност
фев 2022 · 100.0%мар · 100.0%апр · 100.0%

Previous page

Next page

фев 2022
мар 2022
апр 2022

Dashboard - Работи

99% - достъпност
фев 2022 · 100.0%мар · 100.0%апр · 98.50%

Previous page

Next page

фев 2022
мар 2022
апр 2022

API - Работи

100% - достъпност
фев 2022 · 100.0%мар · 100.0%апр · 100.0%

Previous page

Next page

фев 2022
мар 2022
апр 2022

Maintenance Automations - Работи

100% - достъпност
фев 2022 · 100.0%мар · 100.0%апр · 100.0%

Previous page

Next page

фев 2022
мар 2022
апр 2022

История на известията

апр 2022

Issues affecting dashboard access and incident listings
  • Решен
    Решен

    The issue is now resolved!

  • Наблюдаваме
    Наблюдаваме

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

  • Идентифициран
    Идентифициран

    We recently migrated the dashboard to 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

мар 2022

Този месец няма докладвани известия

фев 2022

Issues affecting some status page subdomains on the free plan
  • Решен
    Решен

    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 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! 🚀

  • Наблюдаваме
    Наблюдаваме

    We just fixed the issue for all pages!

    If you're still facing it with your page, kindly contact support@instatus.com or chat with us on slack

  • Идентифициран
    Идентифициран

    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 or chat on slack at instatus.com/chat

фев 2022 до апр 2022

Следващ