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
Why age assurance laws matter for developers
Youth safety requirements are moving down the tech stack to operating systems and app stores—raising new questions for open source developers.
How researchers are using GitHub Innovation Graph data to reveal the “digital complexity” of nations
Researchers share in an interview how they used GitHub data to predict GDP, inequality, and emissions in ways that traditional economic data misses, along with our Q4 2025 data release.
An update on GitHub availability
Here’s what we’ve done—and what we’re still doing—to improve our availability and reliability.