Instatus - Berichtgeschiedenis

Alle systemen operationeel

Openbare statuspagina's - Operationeel

100% - uptime
feb. 2022 · 100.0%mrt. · 100.0%apr. · 100.0%

Previous page

Next page

feb. 2022100.0% uptime
mrt. 2022100.0% uptime
apr. 2022100.0% uptime

Private status pages - Operationeel

100% - uptime
feb. 2022 · 100.0%mrt. · 100.0%apr. · 100.0%

Previous page

Next page

feb. 2022100.0% uptime
mrt. 2022100.0% uptime
apr. 2022100.0% uptime

Dashboard - Operationeel

99% - uptime
feb. 2022 · 100.0%mrt. · 100.0%apr. · 98.50%

Previous page

Next page

feb. 2022100.0% uptime
mrt. 2022100.0% uptime
apr. 202298.50% uptime

API - Operationeel

100% - uptime
feb. 2022 · 100.0%mrt. · 100.0%apr. · 100.0%

Previous page

Next page

feb. 2022100.0% uptime
mrt. 2022100.0% uptime
apr. 2022100.0% uptime

Maintenance Automations - Operationeel

100% - uptime
feb. 2022 · 100.0%mrt. · 100.0%apr. · 100.0%

Previous page

Next page

feb. 2022100.0% uptime
mrt. 2022100.0% uptime
apr. 2022100.0% uptime

Integrations - Operationeel

100% - uptime
feb. 2022 · 100.0%mrt. · 100.0%apr. · 100.0%

Previous page

Next page

feb. 2022100.0% uptime
mrt. 2022100.0% uptime
apr. 2022100.0% uptime

Berichtgeschiedenis

apr. 2022

Issues affecting dashboard access and incident listings
  • Opgelost
    Opgelost

    The issue is now resolved!

  • Monitoring
    Monitoring

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

  • Geïdentificeerd
    Geïdentificeerd

    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

mrt. 2022

Geen mededelingen deze maand

feb. 2022

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

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

  • Monitoring
    Monitoring

    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

  • Geïdentificeerd
    Geïdentificeerd

    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

feb. 2022 naar apr. 2022

Volgende