SharePoint Online outage on
March 6, 2026

Read more >

Improved SSO setup and
logging

Read more >

StatusGator logo
Schedule a Demo
StatusGator logo
Use cases

IT Teams

Stay informed of outages and reduce tickets

DevOps

One status page for all your providers

Education

Features designed specifically for K12

Enterprise

Advanced features designed for enterprise

Managed service providers

Impress clients with proactive monitoring

Competitive intelligence

Analyze and compare peer performance

Monitor dependencies to prevent revenue loss

Create and manage custom status pages for your product

Features

Status page

A status page with service, website, and custom monitors built-in

Status aggregation

Aggregate the status of all vendors to a single page

Cloud monitoring

Monitor all your cloud services from a single dashboard

Website monitoring

Monitor your website with uptime monitoring built-in

Monitor network connectivity

Control the status of custom monitors manually with incidents

Get notified of disruptions before they become public

Pricing

Business

From startup to enterprise and everything in between

Education

Special plans and discounts for K12 and higher ed

Integrations

Incident Management

Better Uptime
FireHydrant
Opsgenie
PagerDuty

Notifications

Private Status

AT&T status
AWS status
Azure status
Microsoft 365 status
Zendesk status

Status Pages

Atlassian Statuspage
StatusHub

Advanced

Sign In Sign Up

How Often Do You Deploy?

There is simply no substitute for a well-tested project that deploys early and often. GitHub famously boasted about 175 deployments in one day, and that was 3 years ago. Even Facebook ships new code every single day. There are now entire products dedicated to shipping code and continuous deployment. As a team leader for nearly 15 years, I’ve often found myself striving for more frequent deploys. And not just hoping for it, but measuring it, tracking it, and improving it over time.

So how often do you deploy? If you use Heroku, we can find out easily.

I recently released the Heroku Average Deploy Plugin, a simple little plugin for the Heroku CLI that calculates how many times per day your project is deployed. Using Heroku’s release history, we can calculate the average time between deploys and then the number of deploys per day. Heroku stores the last 50 releases, so we base our calculation on that.

$ heroku plugins:install https://github.com/cbartlett/heroku-average-deploy.git
$ heroku average:deploy -a your-app-name
Average time between deploys:
57643 seconds
aka 960 minutes
aka 16.01 hours
aka 0.67 days
You deploy an average of 1.5 times per day

The plugin is extremely simple, but “Mean Time Between Deploys” is an important metric for teams to track and improve. Consider including it in your weekly team meeting or sprint retrospective. Perhaps CI providers can calculate this and allow it to be queried from an API or displayed in graphs. (Our beloved

Try it out and send me your feedback, issues, and pull requests!

Share this

Photo of author

Colin Bartlett

Colin Bartlett is co-founder of StatusGator and Nimble Industries, a seasoned Ruby engineer and entrepreneur who launched StatusGator in 2015 and later grew it into a full-fledged company.