Instatus - Notice history

All systems operational

Public status pages - Operational

100% - uptime
Jan 2022 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2022100.0% uptime
Feb 2022100.0% uptime
Mar 2022100.0% uptime

Private status pages - Operational

100% - uptime
Jan 2022 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2022100.0% uptime
Feb 2022100.0% uptime
Mar 2022100.0% uptime

Dashboard - Operational

100% - uptime
Jan 2022 · 99.86%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 202299.86% uptime
Feb 2022100.0% uptime
Mar 2022100.0% uptime

API - Operational

100% - uptime
Jan 2022 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2022100.0% uptime
Feb 2022100.0% uptime
Mar 2022100.0% uptime

Maintenance Automations - Operational

100% - uptime
Jan 2022 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2022100.0% uptime
Feb 2022100.0% uptime
Mar 2022100.0% uptime

Integrations - Operational

100% - uptime
Jan 2022 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2022100.0% uptime
Feb 2022100.0% uptime
Mar 2022100.0% uptime

Notice history

Mar 2022

No notices reported this month

Feb 2022

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

    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

  • Identified
    Identified

    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

Jan 2022

Issues affecting stability of free status pages
  • Resolved
    Resolved

    Issue is resolved now!

  • Monitoring
    Monitoring

    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

  • Identified
    Identified

    We are working on a fix for this incident.

Issues logging in to the dashboard
  • Resolved
    Resolved

    Just resolved the issue with logging into the dashboard.

  • Monitoring
    Monitoring

    We implemented a fix and currently monitoring the result.

Jan 2022 to Mar 2022

Next