Koyeb - Notice history

All systems operational

Control Panel - Operational

100% - uptime
May 2024 · 100.0%Jun · 99.82%Jul · 100.0%

Previous page

Next page

May 2024
Jun 2024
Jul 2024

API - Operational

100% - uptime
May 2024 · 100.0%Jun · 100.0%Jul · 100.0%

Previous page

Next page

May 2024
Jun 2024
Jul 2024

Build / Provisioning - Operational

100% - uptime
May 2024 · 100.0%Jun · 100.0%Jul · 99.80%

Previous page

Next page

May 2024
Jun 2024
Jul 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

Jul 2024

Provisioning delay
  • Resolved
    Resolved
    This incident has been resolved.
  • Investigating
    Investigating
    We are currently investigating this incident.
Databases creation delayed
  • Resolved
    Resolved
    The issue has been addresses.
  • Monitoring
    Monitoring
    We have deployed a fix and are monitoring the resolution. We will soon close the incident as the key metrics are back to green.
  • Identified
    Identified
    We are aware of an issue with a partner that is currently preventing new databases from being created. We are working to resolve the issue
Long queue times for image build
  • Resolved
    Resolved
    The build system is back to normal also for hobby users.
  • Monitoring
    Monitoring
    We deployed an hotfix and are monitoring the outcome.
  • Identified
    Identified

    We identified an issue with our build system, that determines long queue times, and are acting to mitigate it.

    This issue is only impacting hobby accounts.

Frankfurt - Apps stuck in allocating
  • Resolved
    Resolved
    The issue was a consequence of the incident of earlier today.
  • Investigating
    Investigating
    We are investigating some reports of apps stuck in allocating in Frankfurt.
Issue with image build
  • Resolved
    Resolved
    Our build system is back to normal operations.
  • Monitoring
    Update
    The fix is working, we are waiting for the build system to catch up.
  • Monitoring
    Monitoring
    We applied a mitigation and are actively monitoring its application.
  • Identified
    Identified
    We identified the cause of the issue: an incident with an external provider is affecting our build system. We are preparing a fix to mitigate the impact.
  • Investigating
    Investigating

    We identified an issue with our build infrastructure. Currently many apps are enqueued for building and in pending state. We are investigating the cause.

    This issue is only impacting Hobby users.

Jun 2024

Dashboard is crashing with 500 error code
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    We implemented a fix and are currently monitoring the result.

    This was caused by an API update from one of our third party.

  • Investigating
    Investigating

    Some pages on the dashboard are currently unavailable.
    Accessing these pages returns a 500 error,

    We will soon release a fix.

    We are currently investigating this incident.

May 2024

Elevated rate of 404 and 502 on healthy services
  • Resolved
    Resolved

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

  • Monitoring
    Monitoring

    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.

  • Identified
    Identified

    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.

  • Investigating
    Investigating

    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
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

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

  • Identified
    Update

    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.

  • Identified
    Identified

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

    The issue only affects services deployed in Frankfurt.

  • Investigating
    Investigating

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

Provisioning delay
  • 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.
New services reported healthy but not accessible
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring
    We implemented a fix and are currently monitoring the result.
  • Identified
    Identified

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

May 2024 to Jul 2024

Next