Koyeb

First posted only after it was over

0% 0 of the 25 incidents we have in full detailbetterworse

The first update already said resolved. Typical vendor: 6%.

Koyeb: lower than most vendors.

Time to resolve

1 h 33 min median; 9 in 10 within 5 h 53 minbetterworse

From the vendor’s own start and resolve times, over the 162 days of history we have. Typical vendor: 2 h.

Koyeb: around the middle.

Major or critical incidents

0.0 a month 0 in the 162 days of history we havebetterworse

Impact as the vendor labels it. Typical vendor: 1.2 a month.

Koyeb: lower than most vendors.

Rewrites caught

None so far

Counts, not a rate: 10-minute tracking began Oct 17, so there are too few events to compare yet.

Outage events: Microsoft Azure west us, Jul 23 (timing), AWS, Jul 16 (timing).

Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.

No notable changes yet. We compare every snapshot of Koyeb’s status page (taken every 10 minutes) and its 0 tracked pages.

Full Koyeb change history

No pricing, trust or legal pages tracked for Koyeb.

Each change links to its diff: the changed passages with a few words of context, never a full copy of the page.

Koyeb incidents, last 90 daysJSONMarkdown