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
From pair to peer programmer: Our vision for agentic workflows in GitHub Copilot
AI agents in GitHub Copilot don’t just assist developers but actively solve problems through multi-step reasoning and execution. Here’s what that means.
GitHub Availability Report: May 2025
In May, we experienced three incidents that resulted in degraded performance across GitHub services.
GitHub Universe 2025: Here’s what’s in store at this year’s developer wonderland
Sharpen your skills, test out new tools, and connect with people who build like you.