No downtime for the Akismet API that I’m aware of (I’m on the Akismet team). Status of our API is available at http://status.automattic.com/9931/136079/Akismet-API
Could be a router/firewall/proxy server between your host and akismet.com that is refusing connections. Your hosting provider is usually in the best position to determine if that is what is causing the problems.
Thanks. Have been checking with them. It does seem to be an issue with the hosting as my sites are very slow today as well. And my sites can’t pull outside RSS feeds, etc. like the WordPress news in the dashboard.
Thanks for the info.
I had my guy run a traceroute (I’m not that technical on server stuff). My host said that it appeared to leave their network without issue.
This was the result:
root@225937 [~]# traceroute wordpress.org
traceroute to wordpress.org(188.8.131.52), 30 hops max, 40 byte packets
1 vserver3021.laca01.hostnoc.net(184.108.40.206) 0.039 ms 0.039 ms 0.026 ms
2 ec0-64.gwy02.laca02.hostnoc.net(220.127.116.11) 0.350 ms 0.355 ms 0.346 ms
3 tenge11-1.br01.lax05.pccwbtn.net(18.104.22.168) 0.707 ms 0.754 ms 0.802 ms
4 TenGigabitEthernet8-1.1200.ar4.LAX1.gblx.net(22.214.171.124) 10.342 ms 10.458 ms 10.424 ms
5 te-4-4.car4.LosAngeles1.Level3.net(126.96.36.199) 0.526 ms 0.523 ms 0.511 ms
6 vlan90.csw4.LosAngeles1.Level3.net(188.8.131.52) 0.390 ms 0.359 ms 0.324 ms
7 ae-92-92.ebr2.LosAngeles1.Level3.net(184.108.40.206) 0.383 ms 0.358 ms 0.341 ms
8 ae-3-3.ebr3.Dallas1.Level3.net (220.127.116.11) 47.386 ms 47.522 ms 47.263 ms
9 ae-83-83.csw3.Dallas1.Level3.net (18.104.22.168) 47.116 ms ae-63-63.csw1.Dallas1.Level3.net (22.214.171.124) 47.792 ms ae-83-83.csw3.Dallas1.Level3.net (126.96.36.199) 47.170 ms
10 ae-12-60.car2.Dallas1.Level3.net (188.8.131.52) 50.533 ms ae-22-70.car2.Dallas1.Level3.net (184.108.40.206) 50.695 ms ae-12-60.car2.Dallas1.Level3.net (220.127.116.11) 50.607 ms
11 DATABANK-HO.car2.Dallas1.Level3.net(18.104.22.168) 48.088 ms 47.868 ms 48.257 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
I’ll check with the systems team for Akismet, see if they’ve heard anything about an issue with Level3.
So I’m just kind a restating what my guy who helps me with my server said. But we asked the host what the resolver IP’s should be set to then set them. That didn’t help anything. My guy then changed 1 (or all?) to Google’s and everything works perfectly! However something keeps causing them to revert back to the host’s which makes everything go wrong again. The host claims their resolvers are working fine and they haven’t had any issues. Even my guy who manages my VPS, who also has hosting through this same company is not experiencing any issues.
I’m just stating this incase this additional info helps identify the problem in any way. Thanks.
I started to use sitebrains plugin instead of akismet on a few sites, looks promising, anyone use it as a drop in replacement ?
If DNS is a problem then that can definitely do strange things. The traceroute you listed above goes to wordpress.org, have you tried one for akismet.com?
I haven’t tried the Sitebrains plugin, but it looks like you are affiliated with the author of the plugin, so I’m assuming you are already familiar with it.
So my guy called the hosting company (some guy he knows that works in the data center), he finally told us what support wouldn’t: they were actually having issues with their resolver IP’s/DNS. So we’re just using Google’s until they get things straightened out. They were also able to set my VPS to Google’s at some higher level so that they didn’t keep reverting to the host’s. Then once they get stuff worked out, we’ll switch back.
Thanks for you help.
Same issue now with accessing wordpress.org from admin panel of WP installations:
After some “hanging”, there is an error in wp admin panel:
“An Unexpected HTTP Error occurred during the API request.”
This happens when admin is trying to either update plugins, search for new plugins and perhaps doing anything else that requires connection to wordpress.org.
However, this does not seem to be a wordpress.org issue, but rather that of some networks on the “way” to it. Thus, depending on what particular server is used to trace route, connections are dropped from some servers, but not others. For example as of the time of this post, WHO.IS shows problem:
traceroute to wordpress.org (22.214.171.124), 25 hops max, 40 byte packets 1 126.96.36.199-static.reverse.softlayer.com (188.8.131.52) 0.402 ms 0.451 ms 0.550 ms 2 ae11.dar01.sr01.wdc01.networklayer.com (184.108.40.206) 0.218 ms 0.397 ms 0.496 ms 3 ae8.bbr02.eq01.wdc02.networklayer.com (220.127.116.11) 31.691 ms 0.532 ms 0.676 ms 4 xe-8-2-0.edge1.Washington4.Level3.net (18.104.22.168) 0.838 ms 0.944 ms 1.044 ms 5 vlan80.csw3.Washington1.Level3.net (22.214.171.124) 1.045 ms 1.149 ms vlan60.csw1.Washington1.Level3.net (126.96.36.199) 1.110 ms 6 ae-61-61.ebr1.Washington1.Level3.net (188.8.131.52) 1.231 ms 1.068 ms ae-71-71.ebr1.Washington1.Level3.net (184.108.40.206) 1.059 ms 7 ae-2-2.ebr3.Atlanta2.Level3.net (220.127.116.11) 14.498 ms 14.680 ms 14.777 ms 8 ae-7-7.ebr3.Dallas1.Level3.net (18.104.22.168) 34.351 ms 33.368 ms 34.158 ms 9 ae-63-63.csw1.Dallas1.Level3.net (22.214.171.124) 33.861 ms 33.542 ms ae-73-73.csw2.Dallas1.Level3.net (126.96.36.199) 33.438 ms 10 ae-32-80.car2.Dallas1.Level3.net (188.8.131.52) 33.677 ms ae-42-90.car2.Dallas1.Level3.net (184.108.40.206) 34.333 ms ae-22-70.car2.Dallas1.Level3.net (220.127.116.11) 34.555 ms 11 DATABANK-HO.car2.Dallas1.Level3.net (18.104.22.168) 33.812 ms 34.251 ms 34.013 ms 12 * * * 13 * * * 14 * * * 15 * * * .....
While this one does not:
traceroute to wordpress.org (22.214.171.124), 25 hops max, 40 byte packets 1 static-ip-188-138-112-3.inaddr.ip-pool.com (126.96.36.199) 9.066 ms 2 188.8.131.52 (184.108.40.206) 0.338 ms 3 220.127.116.11 (18.104.22.168) 3.447 ms 4 22.214.171.124 (126.96.36.199) 3.653 ms 5 ve498.bbr1.fra3.inetbone.net (188.8.131.52) 3.903 ms 6 xe-11-2-0.400.edge5.Frankfurt1.Level3.net (184.108.40.206) 3.938 ms 7 vlan90.csw4.Frankfurt1.Level3.net (220.127.116.11) 3.796 ms 8 ae-91-91.ebr1.Frankfurt1.Level3.net (18.104.22.168) 3.758 ms 9 ae-48-48.ebr2.Paris1.Level3.net (22.214.171.124) 12.854 ms 10 ae-43-43.ebr2.Washington1.Level3.net (126.96.36.199) 91.855 ms 11 ae-62-62.csw1.Washington1.Level3.net (188.8.131.52) 91.860 ms 12 ae-61-61.ebr1.Washington1.Level3.net (184.108.40.206) 92.050 ms 13 ae-2-2.ebr3.Atlanta2.Level3.net (220.127.116.11) 105.343 ms 14 ae-7-7.ebr3.Dallas1.Level3.net (18.104.22.168) 124.920 ms 15 ae-83-83.csw3.Dallas1.Level3.net (22.214.171.124) 125.011 ms 16 ae-32-80.car2.Dallas1.Level3.net (126.96.36.199) 300.480 ms 17 DATABANK-HO.car2.Dallas1.Level3.net (188.8.131.52) 125.447 ms 18 10.0.0.14 (10.0.0.14) 126.539 ms 19 wordpress.org (184.108.40.206) 125.112 ms
Of note, Akismet.com connections were also dropped earlier today for some time (comments went to “approval” instead of “spam”), but things got normal on their own now.
Now, as we are hosting not only WP clients, we have other needs to connect to external servers (server side) and we see that at the moment at least some connections, to some services we are using are dropped as well. This again is pointing to the issue being related to specific segments of the network, not blog installations, or wordpress.org, or Akismet.com.
We are still trying to ping pong the issue, but it really seems like a “sit and wait” type of solution this far.
P.S. I also read somewhere else a recommendation to increase time out value. I would not do that, unless this is temporary and unless the issue persists and such adjustment helps.
I’m also having similar issues this morning, so I’ve had to deactivate the plugin for now.
Just curious, would this be related to the new Cloudflare feature from MediaTemple? I started using this service on my DV account, and that’s really when I started to notice this Akismet problem. Cloudflare does take control of the DNS records for the domain and may be acting as a firewall preventing Akismet access. Just a thought…
Update: I don’t think it’s cloudflare, as all of my domains are affected (not just the one I chose to use cloudflare with).
On the akismet config page, all the “Server Connectivity” boxes are green, but the above section “Akismet API Key” has the following message in a tan box:
“The key below was previously validated but a connection to akismet.com can not be established at this time. Please check your server configuration.”
So I’m kinda lost. It had worked for a really long time before just recently (and my site’s been on MT (dv) for over 6 months), but I do remember there being a wordpress update in the recent past. So maybe that messed it up somehow?
- The topic ‘Are Akismet servers down?’ is closed to new replies.