We are keeping this issue open on reports of intermittent (but ongoing) failures to receive Github status updates. We have not identified a root cause but are addressing customer issues individually as we continue to monitor and investigate.
Re-opening this incident from yesterday, THU, APR 14, since we are receiving more reports this morning: > We are getting reports of Github status updates not arriving at Github for repos that have been fine in this regard for a long time. We are noticing an uptick in background job failures responsible for these status updates. In most cases, these failures resolve immediately by re-trying them. But some fail a few times before succeeding. We suspect there's an issue with the Github API (though not according to https://www.githubstatus.com/), or an isolated issue between coveralls.io and github.com, that's resulting in behavior like rate limiting. There is no known basis for actual rate limiting, but this is the effect. > > Please know that any failing status updates will be retried in exponential back-off fashion (so they should eventually succeed) and that we are monitoring closely and will take any action we can to improve things.
Never miss when your external dependencies are down. Instant notifications when there are outages.
"I spend 2 hours trying to solve an issue and then realize it's due to an [EXTERNAL SERVICE] outage"
Every engineer at some point in time
No more frantic searching for the source of the problem.
All of your service statuses in one place
Check the status of all your services in one place. No more going to each of the status pages and managing them individually.
Notifications of incidents in real time
We monitor 24 hours a day, 7 days a week and will notify you if there is an incident. No more wasting time trying to figure out why something isn't working.
Notifications in your favorite channel
Get instant notifications in your email, Slack, or Discord.
Keep track of scheduled maintenance
Never again be caught off guard by unexpected maintenance from your services. A feed of the next scheduled maintenances is available.
Set the notification level for each service
Configure which notifications you want to receive from each service. You can choose to receive notifications for all incidents, only critical incidents, or just display them on the dashboard.
Integrate with your current workflows
Using Zapier or Webhooks, you can easily integrate notifications into your processes.
Receive a Weekly Digest
Every Monday, you'll receive a weekly summary of what happened the previous week as well as the maintenance schedule for the following week.
Create one profile for each of your teams. One Dashboard and specific Notifications settings for each team.
Only receive notifications for specific components
Filter notifications by service components. You can opt to receive notifications only when a specific component is affected.
Add another dimension (external systems) to your monitoring data and complement it with the external factors. Monitor the services your company relies on for the development experience. Don't waste time looking elsewhere, when it's an external outage.
Know before your clients tell you. Anticipate possible issues and make the necessary arrangements. Understand if your business is being impacted by outages in external services.
One of your competitors is down? Maybe a good time to spread the word about your service.
all your essential services
Start with a trial account that will allow you to try and monitor up to 30 services for 14 days.
There are 1622 services to choose from, and we're adding more every week.
You can get notifications by email, Slack, and Discord. You can also use Zapier or Webhooks to build your workflows.
Increase the productivity and efficiency of your team. Enable monitoring for your services, and start receiving real-time alerts when your services have outages.Start today for FREE