Koyeb - Notice history

All systems operational

Control Panel - Operational

100.0% uptime
Mar 2024 · 99.99%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2024
Apr 2024
May 2024

API - Operational

100.0% uptime
Mar 2024 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2024
Apr 2024
May 2024

Build / Provisioning - Operational

100.0% uptime
Mar 2024 · 100.0%Apr · 100.0%May · 100.0%

Previous page

Next page

Mar 2024
Apr 2024
May 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

View current status

May 2024

Elevated rate of 404 and 502 on healthy services
ResolvedPartial outage1 hour 51 minutes
  • ResolvedUTC

    The incident is now resolved, we are sorry about the impact, and we are available to discuss the details if needed.

  • MonitoringUTC

    We implemented a fix and have re-scheduled most of the impacted failing service.

    The initial incident triggering 404 was handled very shortly after it was detected, we noticed that some users were still experiencing some 503 due to an automatic garbage collection of some network resources.

    Then we implemented a fix to recover the data that were garbage collected.

  • IdentifiedUTC

    The recovery was done under 5m for most app, but a portion of user were still facing 503, we are currently trying to resolve this issue.

  • InvestigatingUTC

    We are currently investigating this incident, it seems it was caused by a configuration error from our side.

Elevated rate of 404 and 502 on healthy services
ResolvedPartial outage5 hours 33 minutes
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC

    We are still monitoring the state of services on the platform but the issue should be fixed.

  • UpdateUTC

    We are continuing to work on a fix for this incident. The 404 issue has been fixed.

    New services deployed in Frankfurt are however still not accessible. Accessing their public URL ends up in HTTP 502.

  • IdentifiedUTC

    We identified the root cause of the issue and are working on a fix.

    The issue only affects services deployed in Frankfurt.

  • InvestigatingUTC

    We are currently investigating the issue. A percentage of requests seem affected.

Provisioning delay
ResolvedDegraded performance39 minutes
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC
    We implemented a fix and are currently monitoring the result.
  • InvestigatingUTC
    We are currently investigating this incident.
New services reported healthy but not accessible
ResolvedPartial outage5 hours
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC
    We implemented a fix and are currently monitoring the result.
  • IdentifiedUTC

    Services deployed on the platform are returning a 404 page. This affects services created since the beginning of this incident only.

Apr 2024

New deployments erroring
ResolvedDegraded performance6 hours 8 minutes
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC
    We implemented a fix and are currently monitoring the result.
  • InvestigatingUTC

    We identified an issue where new deployments do not complete and end up in Error on the Frankfurt region.

WAS region partially unavailable
Resolved47 minutes
  • ResolvedUTC

    All services are confirmed to be back online.

  • MonitoringUTC

    All services are back online and we're monitoring to make sure everything is back to normal.

  • IdentifiedUTC

    The root cause was identified and we're actively restarting all services.

  • InvestigatingUTC
    We are currently investigating this incident.

Mar 2024

Provisioning delay
ResolvedDegraded performance36 minutes
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC

    Deployment time seems to be back to normal, we are currently monitoring the evolution.

  • InvestigatingUTC
    We are currently investigating this incident.
Provisioning delay in WAS
Resolved3 hours 1 minute
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC

    We experienced some issues with our orchestrator and one hypervisor was disconnected resulting in instances being re-allocated.

    This resulted in a few minutes of downtime for the service on this specific hypervisor, the service with 2 replicas was not impacted and traffic was re-routed to the other healthy instance.

Control panel inaccessible
ResolvedPartial outage1 hour 40 minutes
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC
    We implemented a fix and are currently monitoring the result.
  • IdentifiedUTC

    The control panel is inaccessible, we are seeing a high number of unusual requests and are trying to mitigate the issue.

Promotions delays
ResolvedDegraded performance4 hours 55 minutes
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC
    We implemented a fix and are currently monitoring the result.
  • InvestigatingUTC

    We noticed provisioning delays when rolling out new versions of existing Koyeb services, for at least region was. No downtime is expected.

503s on new deployments
Resolved44 minutes
  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC
    We implemented a fix and are currently monitoring the result.
  • InvestigatingUTC

    We are experiencing an issue which provokes 503s for new deployments on Frankfurt.

Previous

Mar 2024 to May 2024

Next