Incompetence is not becoming
Sep. 21st, 2005 14:55![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
torquillOne week ago, our DSL went out. It had stopped working briefly a week before that due to a corrupted file, so I called our ISP (Amerion) to sort out whatever was the matter this time.
After talking to them, then SBC, then Amerion again, I determined that a departing Amerion engineer had checked the database, not found us where we are supposed to be, and issued a cancel order -- not to Amerion internally, as is usually done, but to SBC directly. Then he left. Five days later, the cancel order went into effect at SBC, and our DSL went down.
Amerion told me that they had just issued a reistatement order (while on the phone with me), and we could expect to wait 3-5 business days for it to come back up. We waited, patiently for the most part. Friday passed, and we sat out the weekend. It still wasn't up by today, Wednesday, so Nick finally called SBC.
After dealing with far more jerkish people than I did, and handing the thing off to my dad eventually, we have an explanation: Amerion says that of course they issued the reinstatement order (why would we think otherwise) but SBC lost it. They've issued another one, which is due to come about on the 28th, a week from today.
Mind you, I find the situation annoying, but bearable... we moved the server (foogod.com) to my brother's place, and we have a 56K dialup connection shared across the house, so I have somewhat laggy access to my mail, Lily, and the web. Neither of my parents, however, can get their mail -- my mom muttered about trying webmail for hers, but my dad has explained, in detail, the laundry list of why nothing works for him. Nick has access to his main account, and foogod.com is thankfully a secondary address for him, so if he has trouble with IMAP on that it's no big deal.
My dad is looking into getting an account with meer.net, which uses Covad rather than SBC -- I think this is a good thing. However, I don't know how long it'll take to get that running, particularly if we have to tangle with SBC about getting the hum on the main line fixed (it's a bad pair), so we might not even have a replacement by the time the current order supposedly comes due with SBC.
So we're on the modem for another week. Through no fault of our own, at any point. Whom did we piss off, and how do we make amends?
After talking to them, then SBC, then Amerion again, I determined that a departing Amerion engineer had checked the database, not found us where we are supposed to be, and issued a cancel order -- not to Amerion internally, as is usually done, but to SBC directly. Then he left. Five days later, the cancel order went into effect at SBC, and our DSL went down.
Amerion told me that they had just issued a reistatement order (while on the phone with me), and we could expect to wait 3-5 business days for it to come back up. We waited, patiently for the most part. Friday passed, and we sat out the weekend. It still wasn't up by today, Wednesday, so Nick finally called SBC.
After dealing with far more jerkish people than I did, and handing the thing off to my dad eventually, we have an explanation: Amerion says that of course they issued the reinstatement order (why would we think otherwise) but SBC lost it. They've issued another one, which is due to come about on the 28th, a week from today.
Mind you, I find the situation annoying, but bearable... we moved the server (foogod.com) to my brother's place, and we have a 56K dialup connection shared across the house, so I have somewhat laggy access to my mail, Lily, and the web. Neither of my parents, however, can get their mail -- my mom muttered about trying webmail for hers, but my dad has explained, in detail, the laundry list of why nothing works for him. Nick has access to his main account, and foogod.com is thankfully a secondary address for him, so if he has trouble with IMAP on that it's no big deal.
My dad is looking into getting an account with meer.net, which uses Covad rather than SBC -- I think this is a good thing. However, I don't know how long it'll take to get that running, particularly if we have to tangle with SBC about getting the hum on the main line fixed (it's a bad pair), so we might not even have a replacement by the time the current order supposedly comes due with SBC.
So we're on the modem for another week. Through no fault of our own, at any point. Whom did we piss off, and how do we make amends?
