Koyeb - Notice history

All systems operational

Control Panel - Operational

100% - uptime
Dec 2023 · 100.0%Jan 2024 · 100.0%Feb · 99.98%

Previous page

Next page

Dec 2023
Jan 2024
Feb 2024

API - Operational

100% - uptime
Dec 2023 · 100.0%Jan 2024 · 100.0%Feb · 99.98%

Previous page

Next page

Dec 2023
Jan 2024
Feb 2024

Build / Provisioning - Operational

100% - uptime
Dec 2023 · 99.71%Jan 2024 · 100.0%Feb · 99.98%

Previous page

Next page

Dec 2023
Jan 2024
Feb 2024

Third Party: Github → API Requests - Operational

Third Party: Github → Webhooks - Operational

Third Party: Cloudflare → Cloudflare Sites and Services → API - Operational

Third Party: Docker → Registry - Degraded performance

Third Party: Quay → Registry - Operational

Notice history

Feb 2024

Build and runtime logs are unavailable
  • Resolved
    Resolved

    Logs components is back online.
    Some logs might have been discarded during the outage (between 12:10 to 12:40 UTC).

Jan 2024

Control panel unavailable
  • Resolved
    Resolved

    This incident has been resolved.

  • Monitoring
    Monitoring

    We implemented a fix and are currently monitoring the result.

Delay in provisionning
  • Resolved
    Resolved

    This incident has been resolved.

    We had to perform an unplanned maintenance (involving a restart) on some LB components.

    Some services may have experience 502 errors during the maintenance.

  • Monitoring
    Monitoring

    We implemented a fix and are currently monitoring the result.

  • Identified
    Identified

    The root cause has been identified.

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

  • Investigating
    Investigating

    We noticed a delay when provisioning or re deploying services.
    We are currently investigating this incident.

Dec 2023

Some service are no longer reachable
  • Resolved
    Resolved

    This incident has been resolved.

  • Monitoring
    Monitoring

    We believe we found the root cause of the issue, more investigation is required, it seems to be related to one of the load-balancing components misbehaving under a certain load.

  • Investigating
    Investigating

    There is currently an elevated rate of 502 errors when requesting some services, we are currently investigating the root cause of the issue.

Provisioning delay
  • Resolved
    Resolved

    This incident has been resolved.

  • Monitoring
    Monitoring

    We implemented a fix and are currently monitoring the result.

    The cluster is now back online and the builds should be able to restart.

    We tried to re-route the builds to another region during the outage, but we were sadly not able.

    We are still trying to understand the root cause of the issue.
    And we will try to understand why the re-routing of the build was not possible during the outage.

  • Identified
    Identified

    We have identified some provisioning delay for builds and deployments in the Frankfurt region.

    Our engineering team is investigating.

Dec 2023 to Feb 2024

Next