Skip to main content
Koyeb

Network upgrade on one A100 hypervisor in NA

Maintenance Lasted 0m · started · Koyeb's page

Level
confirmed
Worst impact
Maintenance
Regions
us

What to do

  • Check whether you use Koyeb in us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Check that everything you run on Koyeb came back after the window closed 2025-10-07 19:00 UTC.

  • Subscribe to Koyeb's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=koyeb works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Koyeb 1

  1. resolved

    Type: Maintenance Duration: 30 minutes Affected Components: San Francisco - SFO, Washington, D.C. - WAS, North America → Oct 7, 19:30:00 GMT+0 - Completed - Maintenance is now in progress Oct 7, 19:00:01 GMT+0 - Identified - Maintenance is now in progress Oct 7, 19:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. We will be performing some network operations.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-bffc58e3ec

Is this Koyeb maintenance still going on?

No, it ended 2025-10-07 19:00 UTC.

How long did it last?

0m, from 2025-10-07 19:00 UTC to 2025-10-07 19:00 UTC, by the times Koyeb posted.

What was affected?

Koyeb named in us.

What caused it?

Koyeb hasn't published a root cause. If it does, it shows here.

Where does this come from?

Koyeb's official status page, https://status.koyeb.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.