Koyeb - Notice history

All systems operational

Control Panel - Operational

100% - uptime
Aug 2024 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2024
Sep 2024
Oct 2024

API - Operational

100% - uptime
Aug 2024 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2024
Sep 2024
Oct 2024

Build / Provisioning - Operational

100% - uptime
Aug 2024 · 100.0%Sep · 100.0%Oct · 99.96%

Previous page

Next page

Aug 2024
Sep 2024
Oct 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 - Operational

Third Party: Quay → Registry - Operational

Notice history

Oct 2024

Provisioning latency
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    UTC
    Investigating

    We're experiencing an issue where new deployments are stuck in the build phase

Sporadic failure of requests with code 503
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    UTC
    Investigating

    We have identified transient network failures on one of our providers in Frankfurt. Apps are transiently responding with code 503.

Environment variable expansion broken at build time
  • Resolved
    UTC
    Resolved

    This incident has been resolved.

  • Monitoring
    UTC
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Identified
    UTC
    Identified

    We identified a regression in the component that builds images and are actively tackling the issue.

Migration to new network stack
  • Completed
    October 07, 2024 at 2:14 PMUTC
    Completed
    October 07, 2024 at 2:14 PMUTC
    Maintenance has completed successfully.
  • In progress
    October 07, 2024 at 10:35 AMUTC
    In progress
    October 07, 2024 at 10:35 AMUTC
    Maintenance is now in progress
  • Planned
    October 07, 2024 at 10:35 AMUTC
    Planned
    October 07, 2024 at 10:35 AMUTC

    We will migrate apps and services to our new network stack in Frankfurt. If this migration affects you, you should have received an email on September 25th.

    The migration might automatically trigger a redeployment of your services with 60 seconds of connectivity loss at most.

Migration to new network stack
  • Completed
    October 07, 2024 at 12:47 PMUTC
    Completed
    October 07, 2024 at 12:47 PMUTC
    Maintenance has completed successfully.
  • In progress
    October 07, 2024 at 8:53 AMUTC
    In progress
    October 07, 2024 at 8:53 AMUTC
    Maintenance is now in progress
  • Planned
    October 07, 2024 at 8:53 AMUTC
    Planned
    October 07, 2024 at 8:53 AMUTC

    We will migrate apps and services to our new network stack in Washington. If this migration affects you, you should have received an email on September 25th.

    The migration might automatically trigger a redeployment of your services with 60 seconds of connectivity loss at most.

Sep 2024

Hypervisor network issue on FRA
  • Resolved
    UTC
    Resolved

    Machine was rebooted and we are conducting investigation with our provider.

  • Identified
    UTC
    Identified

    We have 2 hypervisor that just had network failure in the FRA region, we are currently investigating this incident.

Networking issues in tyo region
  • Resolved
    UTC
    Resolved
    The issue is resolved.
  • Monitoring
    UTC
    Monitoring
    We deployed a fix and are actively monitoring the system.
  • Identified
    UTC
    Identified
    We are aware of networking issues in the tyo region that are impacting all workloads there.
Network load balancing, high rate of 502 errors
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    UTC
    Investigating
    We are currently investigating this incident.
Migration to network stack v2
  • Completed
    September 26, 2024 at 5:00 PMUTC
    Completed
    September 26, 2024 at 5:00 PMUTC
    Maintenance has completed successfully.
  • In progress
    September 26, 2024 at 2:47 PMUTC
    In progress
    September 26, 2024 at 2:47 PMUTC
    Maintenance is now in progress.
  • Planned
    September 26, 2024 at 2:45 PMUTC
    Planned
    September 26, 2024 at 2:45 PMUTC

    We will migrate apps and services to our new network stack in Washington. If this migration affects you, you should have received an email on September 25th.

    The migration might automatically trigger a redeployment of your services with 60 seconds of connectivity loss at most.

Migration to network stack v2
  • Completed
    September 13, 2024 at 8:25 PMUTC
    Completed
    September 13, 2024 at 8:25 PMUTC
    Maintenance has completed successfully.
  • In progress
    September 13, 2024 at 5:14 PMUTC
    In progress
    September 13, 2024 at 5:14 PMUTC
    Maintenance is now in progress.
  • Planned
    September 13, 2024 at 5:14 PMUTC
    Planned
    September 13, 2024 at 5:14 PMUTC

    The migration will automatically trigger a redeployment of your services running in Tokyo with 60 seconds of connectivity loss at most.

Aug 2024

503 on newly deployed services
  • Resolved
    UTC
    Resolved
    This incident has been resolved.
  • Monitoring
    UTC
    Monitoring

    A fix has been applied.

  • Identified
    UTC
    Identified

    We identified an issue where some services are not accessible, ending up in 503s.

Workloads stuck in provisioning
  • Resolved
    UTC
    Resolved

    The issue has been tackled.

  • Monitoring
    UTC
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Identified
    UTC
    Identified
    We identified a problem with our build infrastructure and are acting to rectify the issue.
Elevated rate of 50X errors
  • Resolved
    UTC
    Resolved

    This incident has been resolved, it was caused by a network component that became unresponsive due to memory shortage.

    We will continue the investigation.

  • Investigating
    UTC
    Investigating
    We are currently investigating this incident.

Aug 2024 to Oct 2024

Next