Hi. I'm Ted, the tech guy who runs everything in the background.
I just opened a few messages just 20 minutes ago that the site was down.
It turns out that a change I was working on late last night impacted the access to the database. It was supposed to be setup on a non-production network port, so as to not cause this very scenario. But I made an error in the number of the port I typed in.
And then I had one of those days at the day-job where it was meeting after meeting plus a few emergencies. So I didn't read the notifications in my email until several hours after I cooled off from the work day.
So. It's completely my fault. Just a typo in my work. It took me a mere few moments to correct it once I was aware.
I apologize. And hope the outage didn't cause too much havoc.
Thanks for understanding.
I just opened a few messages just 20 minutes ago that the site was down.
It turns out that a change I was working on late last night impacted the access to the database. It was supposed to be setup on a non-production network port, so as to not cause this very scenario. But I made an error in the number of the port I typed in.
And then I had one of those days at the day-job where it was meeting after meeting plus a few emergencies. So I didn't read the notifications in my email until several hours after I cooled off from the work day.
So. It's completely my fault. Just a typo in my work. It took me a mere few moments to correct it once I was aware.
I apologize. And hope the outage didn't cause too much havoc.
Thanks for understanding.
Comment