Recent activity
Subscribe to this feed
crystal replied on September 16, 2008 23:33 to the problem ""Something is technically wrong" everywhere" in Twitter:
matthew replied on September 04, 2008 03:42 to the problem ""Something is technically wrong" everywhere" in Twitter:
A comment on the problem ""Something is technically wrong" everywhere" in Twitter:
thanks a lot - this solved the problem for me :) – satismoe, on September 03, 2008 18:59
A comment on the problem ""Something is technically wrong" everywhere" in Twitter:
Yep, I think that fixed the problem for my cousin's account (I logged into his acct to fix it for him. I commented in Trucklebed's post that you link to letting everyone know that I believe I have success with this) – srizvi1, on September 03, 2008 17:12
A comment on the problem ""Something is technically wrong" everywhere" in Twitter:
Can you sort mine out too please Mark? My Username is CraftyFella – CraftyFella, on September 03, 2008 16:53
mdy replied on September 03, 2008 16:53 to the problem ""Something is technically wrong" everywhere" in Twitter:
I don't know if it will make any difference, but figured I'd share the info...
Someone in another thread said that they just added additional info to their Twitter profile and the 'something is technically wrong' problem on their home page disappeared.
For details, kindly see click this link.
CraftyFella replied on September 03, 2008 16:50 to the problem ""Something is technically wrong" everywhere" in Twitter:
chanibutt replied on September 03, 2008 16:19 to the problem ""Something is technically wrong" everywhere" in Twitter:
satismoe replied on September 03, 2008 16:07 to the problem ""Something is technically wrong" everywhere" in Twitter:
mdy replied on September 03, 2008 09:12 to the problem ""Something is technically wrong" everywhere" in Twitter:
Hi all. In case you haven't done so yet, please send an email to support AT twitter DOT com.
In that email (not here please), it will be helpful if you could provide:
(1) a description of your problem,
(2) your username,
(3) the email address that you used to register your account (if you remember it)
(4) an indication of when you first encountered this problem and how long the problem has existed.
When Twitter's support system receives your email, it will automatically create a support ticket for you, and it will send back to you a confirmation email that contains the ticket number assigned to your issue. I usually receive the confirmation email within minutes of sending my own email to the support system. The confirmation email will also have a link that you can click to view your support ticket online.
Based on activity in other threads, it seems that Twitter Support is currently dealing with a backlog of support requests, so it may take a while (5 to 8 working days) before you get an actual reply. But at least your support issue will already be in their queue.
Leenie replied on September 03, 2008 07:57 to the problem ""Something is technically wrong" everywhere" in Twitter:
thejohnoram replied on September 03, 2008 07:43 to the problem ""Something is technically wrong" everywhere" in Twitter:
manela replied on September 03, 2008 05:43 to the problem ""Something is technically wrong" everywhere" in Twitter:
manela replied on September 03, 2008 05:42 to the problem ""Something is technically wrong" everywhere" in Twitter:
matthew replied on September 03, 2008 02:50 to the problem ""Something is technically wrong" everywhere" in Twitter:
satismoe replied on September 01, 2008 11:59 to the problem ""Something is technically wrong" everywhere" in Twitter:
mayowa replied on August 31, 2008 22:34 to the problem ""Something is technically wrong" everywhere" in Twitter:
mayowa replied on August 31, 2008 17:28 to the problem ""Something is technically wrong" everywhere" in Twitter:
digitallpro replied on August 30, 2008 15:52 to the problem ""Something is technically wrong" everywhere" in Twitter:
mdy replied on July 31, 2008 12:02 to the problem ""Something is technically wrong" everywhere" in Twitter:
Hi Nicola. I was getting the 'access key not on file' error a couple of weeks ago also -- apparently, the access key was invalidated because they migrated to a new support system.
But they've since stabilized the system and the access keys for new tickets are valid again. I was able to log a new ticket earlier today with a valid access key, so it's a bit disturbing to hear that your ticket is giving you that error.
| next » « previous |
Loading Profile...


