Instatus - Historial de avisos

Todos los sistemas operativos

Public status pages - Operativo

100% - disponible
Dec 2021 · 100.0%Jan 2022 · 100.0%Feb · 100.0%
Dec 2021
Jan 2022
Feb 2022

Private status pages - Operativo

100% - disponible
Dec 2021 · 100.0%Jan 2022 · 100.0%Feb · 100.0%
Dec 2021
Jan 2022
Feb 2022

Uptime monitoring - Operativo

100% - disponible
Dec 2021 · 100.0%Jan 2022 · 100.0%Feb · 100.0%
Dec 2021
Jan 2022
Feb 2022

Incident response - Operativo

100% - disponible
Dec 2021 · 100.0%Jan 2022 · 100.0%Feb · 100.0%
Dec 2021
Jan 2022
Feb 2022

On-call - Operativo

100% - disponible
Dec 2021 · 100.0%Jan 2022 · 100.0%Feb · 100.0%
Dec 2021
Jan 2022
Feb 2022

Slack app - Operativo

100% - disponible
Dec 2021 · 100.0%Jan 2022 · 100.0%Feb · 100.0%
Dec 2021
Jan 2022
Feb 2022

Dashboard - Operativo

100% - disponible
Dec 2021 · 100.0%Jan 2022 · 99.86%Feb · 100.0%
Dec 2021
Jan 2022
Feb 2022

API - Operativo

100% - disponible
Dec 2021 · 100.0%Jan 2022 · 100.0%Feb · 100.0%
Dec 2021
Jan 2022
Feb 2022

Maintenance Automations - Operativo

100% - disponible
Dec 2021 · 100.0%Jan 2022 · 100.0%Feb · 100.0%
Dec 2021
Jan 2022
Feb 2022

Historial de avisos

Feb 2022

Issues affecting some status page subdomains on the free plan
  • Resuelto
    Resuelto

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

  • Supervisando
    Supervisando

    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

  • Identificado
    Identificado

    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

Dec 2021

No se reportaron avisos este mes

Dec 2021 a Feb 2022

Siguiente