Instatus - Historique des incidents

Tous les systèmes sont opérationnels

Public status pages - Opérationnel

100% - disponibilité
janv. 2022 · 100.0%févr. · 100.0%mars · 100.0%

Previous page

Next page

janv. 2022100.0% disponibilité
févr. 2022100.0% disponibilité
mars 2022100.0% disponibilité

Private status pages - Opérationnel

100% - disponibilité
janv. 2022 · 100.0%févr. · 100.0%mars · 100.0%

Previous page

Next page

janv. 2022100.0% disponibilité
févr. 2022100.0% disponibilité
mars 2022100.0% disponibilité

Dashboard - Opérationnel

100% - disponibilité
janv. 2022 · 99.86%févr. · 100.0%mars · 100.0%

Previous page

Next page

janv. 202299.86% disponibilité
févr. 2022100.0% disponibilité
mars 2022100.0% disponibilité

API - Opérationnel

100% - disponibilité
janv. 2022 · 100.0%févr. · 100.0%mars · 100.0%

Previous page

Next page

janv. 2022100.0% disponibilité
févr. 2022100.0% disponibilité
mars 2022100.0% disponibilité

Maintenance Automations - Opérationnel

100% - disponibilité
janv. 2022 · 100.0%févr. · 100.0%mars · 100.0%

Previous page

Next page

janv. 2022100.0% disponibilité
févr. 2022100.0% disponibilité
mars 2022100.0% disponibilité

Historique des incidents

mars 2022

Aucun incident signalé ce mois-ci

févr. 2022

Issues affecting some status page subdomains on the free plan
  • Résolu
    Résolu

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

  • Surveillé
    Surveillé

    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

  • Identifié
    Identifié

    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

janv. 2022

Issues affecting stability of free status pages
  • Résolu
    Résolu

    Issue is resolved now!

  • Surveillé
    Surveillé

    Released a fix for this now, and it seems to be working. Currently monitoring the results to see if it's fixed for everyone.

    If you're currently affected by this, please email support@instatus.com

  • Identifié
    Identifié

    We are working on a fix for this incident.

Issues logging in to the dashboard
  • Résolu
    Résolu

    Just resolved the issue with logging into the dashboard.

  • Surveillé
    Surveillé

    We implemented a fix and currently monitoring the result.

janv. 2022 à mars 2022

Suivant