Koyeb - Notice history

All systems operational

Control Panel - Operational

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

Previous page

Next page

Aug 2023
Sep 2023
Oct 2023

API - Operational

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

Previous page

Next page

Aug 2023
Sep 2023
Oct 2023

Build / Provisioning - Operational

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

Previous page

Next page

Aug 2023
Sep 2023
Oct 2023

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 2023

Database update
  • Completed
    October 17, 2023 at 10:00 AM
    Completed
    October 17, 2023 at 10:00 AM

    Maintenance has completed successfully

  • In progress
    October 17, 2023 at 8:00 AM
    In progress
    October 17, 2023 at 8:00 AM

    Maintenance is now in progress

  • Planned
    October 17, 2023 at 8:00 AM
    Planned
    October 17, 2023 at 8:00 AM

    We are planning a database update at 8:00 UTC.

    We might experience an increased rate of API call failure, the control panel might be unresponsive for a few minutes. Provisioning may be delayed for a few minutes.

    No impact on running services.

Runtime and build logs maintenance
  • Completed
    October 06, 2023 at 3:16 PM
    Completed
    October 06, 2023 at 3:16 PM

    Maintenance has completed successfully.

  • Planned
    October 06, 2023 at 2:50 PM
    Planned
    October 06, 2023 at 2:50 PM

    We will operate a maintenance of our logs backends.

    As a result, recent logs will not be delivered for the duration of the maintenance. No data loss is expected: those logs will be accessible after the maintenance is completed.

Sep 2023

Critical host failure in FRA
  • Resolved
    Resolved

    This incident has been resolved.

  • Monitoring
    Monitoring

    We successfully recovered the impacted servers.

    Some workload are still being recovered automatically.

  • Identified
    Identified

    We identified the root cause of the issue, some of the physical servers are lost because of high load, it seems that some reschedule of the impacted workload triggered a cascaded failure on other nodes.

    We are actively trying to recover access to the impacted servers.

    Some workload are still impacted and will soon recover.
    New build and container start are also impacted.

  • Investigating
    Investigating

    We are seing a high increase of container restart and container boot failure in FRA.

    We are currently investigating this incident.

Aug 2023

No notices reported this month

Aug 2023 to Oct 2023

Next