Koyeb - Notice history

All systems operational

Control Panel - Operational

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

Previous page

Next page

Jan 2016
Feb 2016
Mar 2016

API - Operational

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

Previous page

Next page

Jan 2016
Feb 2016
Mar 2016

Build / Provisioning - Operational

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

Previous page

Next page

Jan 2016
Feb 2016
Mar 2016

Third Party: Github → API Requests - Operational

Third Party: Github → Webhooks - Operational

Third Party: Cloudflare → Cloudflare Sites and Services → API - Degraded performance

Third Party: Docker → Registry - Operational

Third Party: Quay → Registry - Operational

Notice history

Sep 2025

All regions unavailable for some time
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    The configuration was rolled back; we're still seeing and monitoring a few unhealthy deployments for the free users.

    Some new deployments might be throttled due to the volume of new instance creation caused by the rescheduling.

  • Identified
    Identified
    We are continuing to work on a fix for this incident.
  • Investigating
    Investigating
    We are currently investigating this incident.

Aug 2025

Network maintenance in SFO
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified
    Our provider is currently performing some network maintenance in the region, and we're noticing some network disruption.
Network disruption causing 503
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    This was most likely caused by a DDOS, we've blocked the source, and are investigating the issue.

    Traffic should be back to normal.

  • Investigating
    Investigating
    We are currently investigating this incident.
Long allocation times in Washington
  • Resolved
    Resolved
    The issue has been addressed.
  • Monitoring
    Monitoring
    The machine is out of the pool and we are monitoring the status of the cluster.
  • Identified
    Identified
    We identified a problematic machine.
  • Investigating
    Investigating
    We are investigating issues with longer-than-usual allocation times in our Washington datacenter

Jul 2025

503 when reaching a small portion of services
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    (Optional - Several|X) services deployed in XXX are unavailable due to a failure of the underlying hypervisors. Hypervisors failures happen and services should be automatically migrated - in this case they didn’t automatically recover. Our engineering team is investigating.

Elevated rate of 503
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified
    We are continuing to work on a fix for this incident.
Network issues in Tokyo region
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We are aware of an issue where requests are failing for services in Tokyo region. We do not have any ETA to provider as the issue comes from an underlying provider. A workaround is to move services to any other region
HTTP requests failing with 502
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating
    We are currently investigating this incident.
HTTP requests failing with 503
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Identified
    Identified
    We are continuing to work on a fix for this incident.
  • Investigating
    Investigating

Jul 2025 to Sep 2025

Next