Damn, is it down?

All services / Money

coveralls.io · Money

Is Coveralls down?

Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.

What's broken? (optional)
Is it just me?
No problems detected

Live diagnosis

Is it just me?

Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.

Your browser → coveralls.io—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—

Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.

Live outage map

No reports in the last 24 hours.

Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.

User reports

0

Near baseline. 0 in the last hour. Typical hour is about 0.

Our checks

Reaching it

Last check reached it in 1367 ms · 6 min ago.

Reports and checks

Reports compared with the typical volume, with check latency and failures overlaid101261 ms14:0020:0002:0007:4513:45
ReportsTypical baselineCheck latencyFailed checkTimes in UTC
Numbers behind the chart
Time (UTC)ReportsBaselineLatencyFailed checks
03:0000.0841 ms0
03:1500.0144 ms0
03:3000.0279 ms0
03:4500.0338 ms0
04:0000.0632 ms0
04:1500.0885 ms0
04:3000.0149 ms0
04:4500.0383 ms0
05:0000.0330 ms0
05:1500.0173 ms0
05:3000.0100 ms0
05:4500.0306 ms0
06:0000.0214 ms0
06:1500.0264 ms0
06:3000.0123 ms0
06:4500.0202 ms0
07:0000.0319 ms0
07:1500.0144 ms0
07:3000.0929 ms0
07:4500.0322 ms0
08:0000.0116 ms0
08:1500.0234 ms0
08:3000.0156 ms0
08:4500.0194 ms0
09:0000.0265 ms0
09:1500.0145 ms0
09:3000.0151 ms0
09:4500.0466 ms0
10:0000.0413 ms0
10:1500.0157 ms0
10:3000.0623 ms0
10:4500.0199 ms0
11:0000.01261 ms0
11:1500.0210 ms0
11:3000.0216 ms0
11:4500.0189 ms0
12:0000.0699 ms0
12:1500.0206 ms0
12:3000.01233 ms0
12:4500.0117 ms0
13:0000.0672 ms0
13:1500.0152 ms0
13:3000.0759 ms0

Reliability

Score 100/100 · grade A

100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage

90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.

Coveralls status badge Embed a live Coveralls status badge

Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server

Coveralls status and 30-day uptime badge

Past outages

No outages on record for Coveralls yet. Outages of 10 minutes or more get their own page here.

All Coveralls outages · Every recent outage

Having trouble with Coveralls?

One report per service every 10 minutes from this network. No account.

What's broken? (optional)

Notes are stored for rate-limit context and are not shown publicly.

Questions

Is Coveralls down right now?

Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.

Coveralls not working for me but the status is fine. What now?

If Coveralls is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Coveralls's side.

How does Damn is it down decide Coveralls's status?

Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.

How often is Coveralls checked?

About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.