Koyeb - Notice history

All systems operational

Control Panel - Operational

99.98% uptime
Jun 2025 · 99.95%Jul · 100.0%Aug · 100.0%

Previous page

Next page

Jun 2025
Jul 2025
Aug 2025

API - Operational

100.0% uptime
Jun 2025 · 100.0%Jul · 100.0%Aug · 100.0%

Previous page

Next page

Jun 2025
Jul 2025
Aug 2025

Build / Provisioning - Operational

99.99% uptime
Jun 2025 · 100.0%Jul · 99.97%Aug · 100.0%

Previous page

Next page

Jun 2025
Jul 2025
Aug 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

View current status

Aug 2025

AUG26
Network maintenance in SFO
ResolvedMaintenance1 hour 39 minutes
  • ResolvedUTC
    This incident has been resolved.
  • IdentifiedUTC
    Our provider is currently performing some network maintenance in the region, and we're noticing some network disruption.
Network disruption causing 503
ResolvedMajor outage10 minutes
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC

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

    Traffic should be back to normal.

  • InvestigatingUTC
    We are currently investigating this incident.
Long allocation times in Washington
ResolvedDegraded performance30 minutes
  • ResolvedUTC
    The issue has been addressed.
  • MonitoringUTC
    The machine is out of the pool and we are monitoring the status of the cluster.
  • IdentifiedUTC
    We identified a problematic machine.
  • InvestigatingUTC
    We are investigating issues with longer-than-usual allocation times in our Washington datacenter

Jul 2025

503 when reaching a small portion of services
ResolvedDegraded performance5 minutes
  • ResolvedUTC
    This incident has been resolved.
  • IdentifiedUTC

    (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
ResolvedPartial outage4 minutes
  • ResolvedUTC
    This incident has been resolved.
  • IdentifiedUTC
    We are continuing to work on a fix for this incident.
Network issues in Tokyo region
ResolvedMajor outage35 minutes
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC
    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
ResolvedDegraded performance15 minutes
  • ResolvedUTC
    This incident has been resolved.
  • InvestigatingUTC
    We are currently investigating this incident.
HTTP requests failing with 503
ResolvedPartial outage1 hour
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC
    We implemented a fix and are currently monitoring the result.
  • IdentifiedUTC
    We are continuing to work on a fix for this incident.
  • InvestigatingUTC

Jun 2025

HTTP requests failing with 503
ResolvedPartial outage3 hours 23 minutes
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC
    We implemented a fix and are currently monitoring the result.
  • IdentifiedUTC
    We are continuing to work on a fix for this incident.
  • MonitoringUTC
    We implemented a fix and are currently monitoring the result.
  • IdentifiedUTC
    We are continuing to work on a fix for this incident.
  • InvestigatingUTC
    We are aware of an issue where requests are failing with 503.
Provisioning delays and wake up failures
ResolvedDegraded performance33 minutes
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC
    We implemented a fix and are currently monitoring the result.
  • InvestigatingUTC
    We are aware of an issue builds are delayed globally. New deployments in Frankfurt and Paris are delayed too.
503 and 404 on rare cases
ResolvedDegraded performance1 hour 30 minutes
  • ResolvedUTC
    This incident has been resolved.
  • InvestigatingUTC

    We are aware of an issue where a very low percentage of requests may end up in 404 or 503.

Elevated rate of 503s on apps deployed on Koyeb
ResolvedPartial outage1 hour 15 minutes
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC
    We implemented a fix and are currently monitoring the result.
  • IdentifiedUTC

    We've identified that the root cause was that we promoted some deployment automatically that were not fully propagated in our system.

    This incident should only be impacting new deployments.

    We're actively working on a fix.

  • InvestigatingUTC

    We are aware of an issue where apps on Koyeb return 503.

500 errors on Service page
ResolvedPartial outage1 hour 9 minutes
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC
    We implemented a fix and are currently monitoring the result.
  • InvestigatingUTC
    We are aware of an issue where the control panel returns Internal Server Errors in some cases

Previous

Jun 2025 to Aug 2025

Next