Semaphore vs. Coveralls

Compare the status, incidents stats and history between Semaphore and Coveralls

Every service has different practices when updating its status page, so compare these stats with a grain of salt. E.g., one service can be more aggressive when updating its status page than other so that they will have more incidents, but it doesn't mean it is worse than the other.

Semaphore current official status is Operational

Statistics

1
Incidents in the last 7 days: 3
Incidents in the last 30 days: 5
Incidents in the last 90 days

Latest incidents

Resolved Delays in job processing on Semaphore 2.0

We are currently investigating this issue.

5 days ago Official incident report

Resolved Issues with GitHub Status checks on PR builds

We are currently investigating this issue.

9 days ago Official incident report

Resolved Elevated error rates on Semaphore

We are currently investigating this issue.

20 days ago Official incident report

Components

Semaphore 2.0

Semaphore Classic

Coveralls current official status is Operational

Statistics

0
Incidents in the last 7 days: 1
Incidents in the last 30 days: 2
Incidents in the last 90 days

Latest incidents

Resolved Unplanned outage - Working to resolve

We are currently investigating this issue.

14 days ago Official incident report

Resolved Outage for some users

We are currently investigating report of a partial outage for some users.

about 2 months ago Official incident report

Resolved Longer than normal build times reported

Several users have reported longer than average build times, either appearing as large number under a build's "BUILD TIME" or as builds staying in PENDING COMPLETION state for longer than expected....

3 months ago Official incident report

Components

Pusher Presence channels

Pusher WebSocket client API

Stripe API

Never again lose time looking in the wrong place

Start Monitoring in 5 minutes

14-day free trial · No credit card required · No code required