Monthly Fail #5, Overall Fail #29

That previous fail came on Sunday. This fail came Monday. I received a text and responded accordingly, then left the text app on my phone as I often do. But no, I need to oversee the whole process as though I'm some evil warehouse micromanager overseeing some poor commoner on an assembly line. I received a second text from the same person and noticed the red '!' symbol denoting my text did not go through. I resent.

Monthly Fail #4, Overall Fail #28

Had just started a phone call to discuss an exciting matter with a friend when the call was dropped. I called him back and told him I would try him the next day if I was dropped again, but the drop never happened. So that's it... I have to threaten my phone and it will cooperate.

Month Fail #3 - Overall Fail #27

Tried four times in a row to send a text message Monday night and it finally went out on the fifth try.

Monthly Fail #2 - Overall Fail #26

Received a voicemail with no phone call Monday night.

Monthly Fail #1 - Overall Fail #25

Saturday ended the first month of fail documentation on this blog and we had a total of 24 fails. I will be in contact with AT&T before I pay my next bill and I will post what happens.

With a new month in mind, I will start classifying fails as they happen monthly while still keeping track of overall fails.

Since I averaged almost one fail per day during the first month of documentation, it was only fitting that I got a fail on the first day of the new billing cycle. It came yesterday in the form of a voicemail despite no missed call. Also a website I visited failed to load when I was at a friend's house after the big game. (I won't use the trademark.) However, I can't confirm that the website wasn't overloaded so no room to judge the 3G network based on circumstantial evidence.

Fail #24

Failed to send a text message on Saturday. Tried to send again and failed again. Held up to the window like it was the year 2000 and it went through. I finally figured it out... my service is trapped in the year 2000.

Fail #23?

Plenty of fails on Monday, but none since. The last fail may not have failed at all. I sent a text message to two recipients. I am able to tell as each message goes through and it appeared that it went to the first recipient and not the second. The failed text message signal appeared. I decided I didn't need to try to resend. But then the second recipient texted me back. So not sure what happened on this one...

Fail #22

Had another drop on Monday. This was an important, business-like call. I called the person back on a land line a few minutes later. She said she called me back twice and neither call came through. She also left a voicemail on one of the calls and it did not show up on my phone for about a half hour.

Fail #21

Was talking to a buddy on Monday while I was at home. The call was dropped, but we were not sure if it was him or me. Doesn't really matter though since we are both iPhone users.

Fail #20

Disclaimer: Don't judge me for going to Panera more than the average male. I get some good work done there.

Was at Panera last Thursday and dropped another call. But this wasn't any dropped call. Do you ever get one of those drops that it feels like an atomic bomb detonated. They happen rarely, but these are the types of dropped calls I look forward to. There is a loud static-like sound that dimly fades to silence, as opposed to the 'ole AT&T triple beep.

Anyway, that's what happened last week. Seems my buddy was blown up by this bomb. Poor guy.