●Incident

Codecov outage.

ResolvedDEGRADATION · HIGH

Oct 25, 2026, 01:48 PM · about 8 hours ago · Duration: 30min

Detected by Probecast

Incident Summary

Incident Summary

API Codecov is currently DOWN in europe.

Diagnostic Details

Error Type: http HTTP Status: 503 Error Message: API returned HTTP 503 Retry Attempts: 1 (all failed)

Validation Results

Validation Reason: DOWN only in europe - possible regional issue Consecutive DOWN Checks: 2 Time Between Checks: 286s

Regional Analysis

Status: DOWN only in europe (possible regional issue) Other Regions: asia: up, us-east: up, us-west: up

Severity Assessment

Level: MEDIUM Limited regional impact or recoverable error type.


Detected by Probecast Health Monitor - 2026-10-25T13:48:39.953Z

Timeline

●Started

Oct 25, 2026, 01:48 PM

about 8 hours ago

●Resolved

Oct 25, 2026, 02:18 PM

about 8 hours ago

●Duration

30min

Total downtime

Evidence Logs4 checks

TimeRegionStatusLatencyCode
Oct 25, 01:48 PMeuropedown107ms503
Oct 25, 01:43 PMeuropedown111ms503
Oct 25, 01:35 PMus-eastdown74ms503
For the projects you ship

How many of your clients depend on Codecov?

When Codecov slows down, every project that depends on it feels it at once — and the first call goes to whoever shipped it. Probecast watches the sites you ship and the providers underneath them, shows which clients an outage touches and turns each month into a report your client can trust.

One provider breaks. See every client it touches.

Ordered by how many clients it hits, so you message the right people first.

Each client's site and store, checked from four regions.

US West & East, Europe and Asia — a regional outage never hides.

A monthly report under your brand, reviewed by your team before it goes out.

Uptime, incidents, traffic, revenue and support — signed off by a person.

Your team scoped per client. Every change on the record.

Freelancers see only their clients; every change lands in an append-only audit log.

Start freeBook 15 minutes →View Codecov full status →

Alerts land on email, Slack, push or webhooks — with the client's name on them.

Related Incidents