Is Koyeb down?
Last checked 7m agoAffected component: Third Party: Docker → Registry
Koyeb is reporting a partial outage right now (last checked 7m ago). Some components are affected; others remain operational.
Real-time Koyeb status, recent outages, and incident history — pulled directly from Koyeb's official status page at https://status.koyeb.com every 5 minutes. Pingoru tracks 17 Koyeb services and has captured 38 incidents in the last 90 days (97.52% uptime). Get email, Slack, Discord, or webhook alerts the moment Koyeb reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Control PanelAPI
Timeline · 2 updates
- investigating · Jul 23, 2026, 03:16 PM UTC
We are investigating this issue. Existing deployments are working not affected.
- resolved · Jul 23, 2026, 03:17 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
-
Timeline · 1 update
- resolved · Jul 23, 2026, 03:16 PM UTC
Type: Incident Duration: 2 minutes Affected Components: API, Control Panel Jul 23, 15:16:00 GMT+0 - Investigating - We are investigating this issue. Existing deployments are working not affected. Jul 23, 15:17:51 GMT+0 - Resolved - This incident has been resolved.
Latest: Type: Incident Duration: 2 minutes Affected Components: API, Control Panel Jul 23, 15:16:00 GMT+0 - Investigating - We are investigating this issue. Existing deployments are workin…
-
-
Timeline · 1 update
- resolved · Jul 21, 2026, 09:30 AM UTC
Type: Incident Duration: 1 hour and 59 minutes Affected Components: Tokyo - TYO, San Francisco - SFO, Paris - PAR, Singapore - SIN, Frankfurt - FRA Jul 21, 09:30:00 GMT+0 - Investigating - We had an issue where new custom domains or refreshed custom domains would be stuck in Pending. Jul 21, 11:29:00 GMT+0 - Resolved - This incident has been resolved.
Latest: Type: Incident Duration: 1 hour and 59 minutes Affected Components: Tokyo - TYO, San Francisco - SFO, Paris - PAR, Singapore - SIN, Frankfurt - FRA Jul 21, 09:30:00 GMT+0 - Investi…
-
- Tokyo - TYOFrankfurt - FRASingapore - SINParis - PARSan Francisco - SFO
Timeline · 2 updates
- investigating · Jul 21, 2026, 09:30 AM UTC
We had an issue where redeploying a service using a custom domain would result in the domain returning 404\. Existing deployments were unaffected
- resolved · Jul 21, 2026, 11:29 AM UTC
This incident has been resolved. The root cause is still unclear, we are investigataing.
Latest: This incident has been resolved. The root cause is still unclear, we are investigataing.
-
-
Timeline · 1 update
- resolved · Jul 20, 2026, 10:30 PM UTC
Type: Incident Duration: 5 hours and 30 minutes Affected Components: Build / Provisioning Jul 20, 22:30:00 GMT+0 - Investigating - New deployments were throttled, causing them to take up to 20-30 minutes to reach a Healthy state. Existing deployments unaffected Jul 21, 04:00:00 GMT+0 - Resolved - This incident has been resolved.
Latest: Type: Incident Duration: 5 hours and 30 minutes Affected Components: Build / Provisioning Jul 20, 22:30:00 GMT+0 - Investigating - New deployments were throttled, causing them to t…
-
See the full Koyeb outage history
33 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Koyeb outage history →Or sign up free to get alerts when Koyeb breaks · 10 free monitors · No credit card
- 500s on APIs ResolvedStarted Jul 23, 2026, 03:16 PM UTC · Resolved Jul 23, 2026, 03:17 PM UTC · 1m
- 500s on APIs ResolvedStarted Jul 23, 2026, 03:16 PM UTC · Resolved Jul 23, 2026, 03:16 PM UTC · —
- Started Jul 21, 2026, 09:30 AM UTC · Resolved Jul 21, 2026, 09:30 AM UTC · —
- Started Jul 21, 2026, 09:30 AM UTC · Resolved Jul 21, 2026, 11:29 AM UTC · 1h 59m
- Provisioning delays ResolvedStarted Jul 20, 2026, 10:30 PM UTC · Resolved Jul 20, 2026, 10:30 PM UTC · —
- Provisioning delays ResolvedStarted Jul 20, 2026, 10:30 PM UTC · Resolved Jul 21, 2026, 04:00 AM UTC · 5h 30m
- Login failure ResolvedStarted Jul 16, 2026, 08:59 AM UTC · Resolved Jul 16, 2026, 10:32 AM UTC · 1h 33m
- Login failure ResolvedStarted Jul 16, 2026, 08:59 AM UTC · Resolved Jul 16, 2026, 08:59 AM UTC · —