Koyeb - Notice history

All systems operational

Control Panel - Operational

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

Previous page

Next page

Aug 2025
Sep 2025
Oct 2025

API - Operational

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

Previous page

Next page

Aug 2025
Sep 2025
Oct 2025

Build / Provisioning - Operational

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

Previous page

Next page

Aug 2025
Sep 2025
Oct 2025

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 2025

Network upgrade on one A100 hypervisor in NA
  • Completed
    October 07, 2025 at 7:30 PM
    Completed
    October 07, 2025 at 7:30 PM
    Maintenance is now in progress
  • In progress
    October 07, 2025 at 7:00 PM
    In progress
    October 07, 2025 at 7:00 PM
    Maintenance is now in progress
  • Planned
    October 07, 2025 at 7:00 PM
    Planned
    October 07, 2025 at 7:00 PM

    We are planning for a scheduled maintenance during that time. We will be performing some network operations.

Sep 2025

503s in Singapore, Tokyo and Washington
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Investigating
    Investigating
    We are currently investigating this incident.
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

Aug 2025 to Oct 2025

Next