Double Billing Receipts
If you received two email receipts tonight it’s because we accidentally billed you twice. That said, the second charge has already been voided. In the craziness of migrating hosts we…
If you received two email receipts tonight it’s because we accidentally billed you twice. That said, the second charge has already been voided.
In the craziness of migrating hosts we forgot to turn off the cron jobs on our Engine Yard slices. One of those was our nightly billing job so it ran once on EY and again on Rackspace. Fortunately our payment processor, Braintree, has a great API that allowed me to grab all of the customers that were billed twice this morning and void the second charge in about 10 lines of ruby.
This is particularly embarrassing for me, because it could have been easily avoided, but I wanted to be totally honest about what happened and let you know that we took care of it.
Now let’s all get back and enjoy crazy-fast GitHub!!
Written by
Related posts
Let’s talk about GitHub Actions
A look at how we rebuilt GitHub Actions’ core architecture and shipped long-requested upgrades to improve performance, workflow flexibility, reliability, and everyday developer experience.
GitHub Availability Report: November 2025
In November, we experienced three incidents that resulted in degraded performance across GitHub services.
The new identity of a developer: What changes and what doesn’t in the AI era
Discover how advanced AI users are redefining software development—shifting from code producers to strategic orchestrators—through delegation, verification, and a new era of AI-fluent engineering.