Unleash - Notice history

All systems operational

www.getunleash.io - Operational

100% - uptime
Oct 2022 · 100.0%Nov · 100.0%Dec · 100.0%

Previous page

Next page

Oct 2022
Nov 2022
Dec 2022

docs.getunleash.io - Operational

100% - uptime
Oct 2022 · 100.0%Nov · 100.0%Dec · 100.0%

Previous page

Next page

Oct 2022
Nov 2022
Dec 2022

app.unleash-hosted.com [EU region] - Operational

100% - uptime
Oct 2022 · 99.97%Nov · 100.0%Dec · 100.0%

Previous page

Next page

Oct 2022
Nov 2022
Dec 2022

us.app.unleash-hosted.com [US region] - Operational

100% - uptime
Oct 2022 · 100.0%Nov · 100.0%Dec · 100.0%

Previous page

Next page

Oct 2022
Nov 2022
Dec 2022

Notice history

Dec 2022

Urgent maintenance needed in kubernetes clusters.
  • Completed
    December 16, 2022 at 9:35 AM
    Completed
    December 16, 2022 at 9:35 AM

    Maintenance has completed successfully

  • In progress
    December 16, 2022 at 9:20 AM
    In progress
    December 16, 2022 at 9:20 AM

    Maintenance is now in progress

  • Planned
    December 16, 2022 at 9:20 AM
    Planned
    December 16, 2022 at 9:20 AM

    We are going to roll out a patch to increase the stability of our Kubernetes clusters. This may lead to a few 502 responses during the upgrade.

    The Unleash clients are designed to mitigate this, and will catch up within the next poll cycle.

Nov 2022

RDS cluster upgrade
  • Completed
    November 10, 2022 at 6:30 AM
    Completed
    November 10, 2022 at 6:30 AM

    Maintenance has completed successfully

  • In progress
    November 10, 2022 at 6:00 AM
    In progress
    November 10, 2022 at 6:00 AM

    Maintenance is now in progress

  • Planned
    November 10, 2022 at 6:00 AM
    Planned
    November 10, 2022 at 6:00 AM

    We are planning for a scheduled maintenance.

    The service will be unstable for about 2 minutes during fail over for about 20% of our customers in eu region.

Oct 2022

EU region down due to miss-configure load-balancer
  • Resolved
    Resolved

    We just resolved the issue!

  • Monitoring
    Monitoring

    We implemented a fix and currently monitoring the result.

  • Identified
    Identified

    We are continuing to work on a fix for this incident.

  • Investigating
    Investigating

    We are currently investigating this incident.

One customer instance experience high 502 rates
  • Resolved
    Resolved

    We are continuing to work on a fix for this incident. Our data shows it only impacted a single customer in the EU region.

    We will do a post-mortem to understand why this happened and how we can improve our alerting system to catch this earlier.

Oct 2022 to Dec 2022

Next