Jump to content

www.spamcop.net unavailable?


get-even

Recommended Posts

This morning, while the forums work just fine, www.spamcop.net is *almost* unreachable. It pings,

and once (of a dozen attempts) I got a partial page, but all other attempts to confim spam result in

the errors "Gateway Timeout The proxy server did not receive a timely response from the upstream server."

and a direct telnet gives (after about two minutes, the "connect" is immediate):

% telnet www.spamcop.net 80

Trying 209.247.88.168...

Connected to a369.g.akamai.net.

Escape character is '^]'.

HTTP/1.0 408 Request Time-out

Server: AkamaiGHost

Mime-Version: 1.0

Date: Sun, 26 Dec 2004 13:39:08 GMT

Content-Type: text/html

Content-Length: 163

Expires: Sun, 26 Dec 2004 13:39:08 GMT

<HTML><HEAD>

<TITLE>Request Timeout</TITLE>

</HEAD><BODY>

<H1>Request Timeout</H1>

The server timed out while waiting for the browser's request.<P>

</BODY></HTML>

Connection closed by foreign host.

Link to comment
Share on other sites

  • Replies 66
  • Created
  • Last Reply

I just checked from here and those pages came up just fine. So the problem may be from your location to your local akamai.net location (if I understand how akamai works).

For me, www.spamcop.net is resolving to a369.g.akamai.net [199.232.159.244]

All day today and normally, I use the http://mailsc.spamcop.net/ pages however because of my paid account which resolve to a different akamai server IP.

We may need to wait for the deputies to respond if it is a specific server in the akamai network. You can try emailing deputies<at>spamcop.net but we were informed that they were taking some much deserved time off for the holiday and response might be slower than normal.

The forums are on a specific server in JT's area (east coast with the mail servers) while the www and mailsc "servers" are distributed via the akamai network.

Link to comment
Share on other sites

Comparison: from here www.spamcop.net -> a369.g.akamai.net [64.86.101.39]

StevenUnderwood .... www.spamcop.net = a369.g.akamai.net [199.232.159.244]

get-even ................... www.spamcop.net = a369.g.akamai.net [209.247.88.168]

The top two appear to be working just fine.

Link to comment
Share on other sites

Comparison: from here  www.spamcop.net -> a369.g.akamai.net [64.86.101.39]

StevenUnderwood .... www.spamcop.net = a369.g.akamai.net [199.232.159.244]

get-even ................... www.spamcop.net = a369.g.akamai.net [209.247.88.168]

The top two appear to be working just fine.

21799[/snapback]

Recurring Problem. (it started working again after about 5 minutes).

% telnet www.spamcop.net 80

Trying 166.90.133.200...

Connected to a369.g.akamai.net.

Escape character is '^]'.

HTTP/1.0 408 Request Time-out

Server: AkamaiGHost

Mime-Version: 1.0

Date: Mon, 27 Dec 2004 12:40:38 GMT

Content-Type: text/html

Content-Length: 163

Expires: Mon, 27 Dec 2004 12:40:38 GMT

<HTML><HEAD>

<TITLE>Request Timeout</TITLE>

</HEAD><BODY>

<H1>Request Timeout</H1>

The server timed out while waiting for the browser's request.<P>

</BODY></HTML>

Connection closed by foreign host.

Fatal error in process.

Link to comment
Share on other sites

I'm having the exact same problem as get-even:

http://forum.spamcop.net works fine ...

BUT http://www.spamcop.net times out !

telnet www.spamcop.net 80
HTTP/1.0 408 Request Time-out
Server: AkamaiGHost
Mime-Version: 1.0
Date: Wed, 29 Dec 2004 16:33:30 GMT
Content-Type: text/html
Content-Length: 163
Expires: Wed, 29 Dec 2004 16:33:30 GMT

&lt;HTML&gt;&lt;HEAD&gt;
&lt;TITLE&gt;Request Timeout&lt;/TITLE&gt;
&lt;/HEAD&gt;&lt;BODY&gt;
&lt;H1&gt;Request Timeout&lt;/H1&gt;
The server timed out while waiting for the browser's request.&lt;P&gt;
&lt;/BODY&gt;&lt;/HTML&gt;
Connection to host lost.

Doing a nslookup www.spamcop.net I get:

Server:  a212-113-164-49.netcabo.pt
Address:  212.113.164.49

Non-authoritative answer:
Name:    a369.g.akamai.net
Addresses:  212.113.163.39, 212.113.163.51
Aliases:  www.spamcop.net, www.spamcop.net.edgesuite.net

Connecting to http://www.spamcop.net times out

Connecting to http://212.113.163.39 times out

Connecting to http://212.113.163.51 times out

Connecting to http://www.spamcop.net.edgesuite.net/ sometimes works, but usually it times out also.

Browsing the IP addresses supplied by Wazoo:

http://64.86.101.39

AND

http://199.232.159.244

returns:

Invalid URL
The requested URL "/", is invalid.

Any ideas / suggestions, please? :huh:

Link to comment
Share on other sites

Quick note for now ... the Forum is hosted on JT's system in Georgia (east coast US) and does not use the Akamai system .... www.spamcop.net is primarily based on IronPort systems in California (west coast US), but the Akamai servers are around the world. Thus the differences between those connections.

Somewhere in the way-back part of my head, there was once a tremendous issue between a New York hosting service that SpamCop once used and a major European bandwidth provider. Solutions included setting changes including MTU settings and even firewall settings that were blocking some of the handshaking signals that might have handled the MTU problem had these signals been allowed to pass .. I seem to recall it was as simple as the unblocking of an ICMP / Ping .. but, I'm going to have to go dig all that stuff up (actually remembering where all the traffic was would be a good start <g>)

Link to comment
Share on other sites

[snip]

Somewhere in the way-back part of my head, there was once a tremendous issue between a New York hosting service that SpamCop once used and a major European bandwidth provider.  Solutions included setting changes including MTU settings and even firewall settings that were blocking some of the handshaking signals that might have handled the MTU problem had these signals been allowed to pass .. I seem to recall it was as simple as the unblocking of an ICMP / Ping .. [snip]

21995[/snapback]

Thanks for the feedback Wazoo! :)

I have also done a traceroute to www.spamcop.net

It resolves to a369.g.akamai.net which, in turn, sometimes resolves to 212.113.163.51 and other times it resolves to 212.113.163.39

tracert www.spamcop.net

Tracing route to a369.g.akamai.net [212.113.163.51]
over a maximum of 30 hops:

  1    20 ms    10 ms    10 ms  10.19.79.254
  2    11 ms    10 ms    10 ms  a212-113-162-46.netcabo.pt [212.113.162.46]
  3   &lt;10 ms    30 ms    10 ms  ge-5-1.cr01pc01.netcabo.net [212.113.160.210]
  4    10 ms    21 ms    10 ms  a212-113-161-83.netcabo.pt [212.113.161.83]
  5   &lt;10 ms    10 ms    10 ms  vl-2.sr01pc01.netcabo.net [212.113.161.19]
  6     *        *        *     Request timed out.
[ all the following lines return  "*        *        *     Request timed out." ]

The traceroute to 212.113.163.39 is very similar (it also times out in the 6th hop and the other hops are the same).

An additional info: I am connected to the Internet by "NetCabo" - http://www.netcabo.pt - which is the largest "Cable Modem ISP" in Portugal (Europe). Specifically, I'm in the capital of Portugal: Lisbon.

Thanks again for your feedback. Any additional feedback (from you or anyone else) would be much appreciated.

Link to comment
Share on other sites

Then I think this is going to be a bit upsetting then;

12/29/04 21:00:53 Slow traceroute 212.113.163.51

Trace 212.113.163.51 ...

152.63.101.45 RTT: 63ms TTL: 80 (0.so-3-0-0.XR2.MIA4.ALTER.NET ok)

152.63.83.181 RTT: 62ms TTL: 80 (POS7-0.IG3.MIA4.ALTER.NET ok)

65.208.84.38 RTT: 141ms TTL: 80 (companhiaportuguesa-gw.customer.alter.net ok)

195.8.0.90 RTT: 145ms TTL: 80 (lisbon2-br1-p20.cprm.net ok)

195.8.10.198 RTT: 142ms TTL: 80 (netcabo1.cprm.net ok)

212.113.161.218 RTT: 142ms TTL: 80 (ge-4-1.cr01pc02.netcabo.net ok)

212.113.161.83 RTT: 141ms TTL: 80 (vl-40.sr01pc02.netcabo.net ok)

* 212.113.161.19 RTT: 141ms TTL: 80 (a212-113-161-19.netcabo.pt bogus rDNS: host not found [authoritative])

212.113.163.51 RTT: 155ms TTL: 46 (a212-113-163-51.deploy.akamaitechnologies.com ok)

12/29/04 21:01:20 Slow traceroute 212.113.163.39

Trace 212.113.163.39 ...

152.63.83.177 RTT: 62ms TTL: 80 (POS6-0.IG3.MIA4.ALTER.NET ok)

65.208.84.38 RTT: 142ms TTL: 80 (companhiaportuguesa-gw.customer.alter.net ok)

195.8.0.90 RTT: 143ms TTL: 80 (lisbon2-br1-p20.cprm.net ok)

195.8.10.198 RTT: 142ms TTL: 80 (netcabo1.cprm.net ok)

* 212.113.161.209 RTT: 143ms TTL: 80 (ge-4-1.cr01pc01.netcabo.net ok)

212.113.161.83 RTT: 143ms TTL: 80 (vl-40.sr01pc02.netcabo.net ok)

212.113.161.19 RTT: 141ms TTL: 80 (vl-2.sr01pc01.netcabo.net ok)

212.113.163.39 RTT: 145ms TTL: 46 (a212-113-163-39.deploy.akamaitechnologies.com ok)

The asterisks indicate a time-out, but the re-try seemed to fly. Noting that the paths aren't exactly the same, but still traveling through netcabo.net ... hard to believe that both Akamai servers were not availabe, but ..???

Link to comment
Share on other sites

From here:

18 80 ms 80 ms 90 ms POS6-0.IG3.MIA4.ALTER.NET [152.63.83.177]

19 150 ms 150 ms 160 ms companhiaportuguesa-gw.customer.alter.net [65.208.84.38]

20 151 ms 160 ms 150 ms lisbon2-br1-p20.cprm.net [195.8.0.90]

21 150 ms 160 ms 150 ms netcabo1.cprm.net [195.8.10.198]

22 150 ms 160 ms 160 ms ge-4-1.cr01pc01.netcabo.net [212.113.161.209]

23 150 ms 150 ms 150 ms vl-40.sr01pc02.netcabo.net [212.113.161.83]

24 150 ms 160 ms 151 ms vl-2.sr01pc01.netcabo.net [212.113.161.19]

25 * 150 ms 150 ms a212-113-163-51.deploy.akamaitechnologies.com [212.113.163.51]

18 90 ms 90 ms 90 ms POS7-0.IG3.MIA4.ALTER.NET [152.63.83.181]

19 160 ms 160 ms 151 ms companhiaportuguesa-gw.customer.alter.net [65.208.84.38]

20 150 ms 160 ms 161 ms lisbon2-br1-p20.cprm.net [195.8.0.90]

21 150 ms 150 ms * netcabo1.cprm.net [195.8.10.198]

22 160 ms 171 ms 160 ms ge-4-1.cr01pc02.netcabo.net [212.113.161.218]

23 160 ms 161 ms 150 ms vl-40.sr01pc02.netcabo.net [212.113.161.83]

24 150 ms 171 ms 160 ms vl-2.sr01pc01.netcabo.net [212.113.161.19]

25 160 ms * 150 ms a212-113-163-39.deploy.akamaitechnologies.com [212.113.163.39]

Link to comment
Share on other sites

Hi Jeff and Wazoo!

First of all, thanks a lot for your feedback.

From here:

18    80 ms    80 ms    90 ms  POS6-0.IG3.MIA4.ALTER.NET [152.63.83.177]

19 150 ms 150 ms 160 ms  companhiaportuguesa-gw.customer.alter.net [65.208.84.38]

20 151 ms 160 ms 150 ms  lisbon2-br1-p20.cprm.net [195.8.0.90]

21 150 ms 160 ms 150 ms  netcabo1.cprm.net [195.8.10.198]

22 150 ms 160 ms 160 ms  ge-4-1.cr01pc01.netcabo.net [212.113.161.209]

23 150 ms 150 ms 150 ms  vl-40.sr01pc02.netcabo.net [212.113.161.83]

24 150 ms 160 ms 151 ms  vl-2.sr01pc01.netcabo.net [212.113.161.19]

25  *      150 ms 150 ms  a212-113-163-51.deploy.akamaitechnologies.com [212.113.163.51]

[snipped similar successful traceroute to 212.113.163.39]

22020[/snapback]

That's REALLY interesting. I still have the same problem. I have discovered a workaround though: if I set up my Browser to use one of the Public Proxies that are available in the Internet, then I can *reach* and *Login* at the http://www.spamcop.net web page (I have a spamcop.net e-mail account).

Netcabo uses a Transparent Proxy. If I check my connection at:

http://www.lagado.com/proxy-test

... then I get:

Proxy Test

This request appears to have come via a proxy.

The proxy host has ip address 212.113.164.104

The proxy server has announced itself as 1.1 Application and Content Networking System Software 5.1.11

The proxy informs us that the client host ip address was 83.132.154.243

So, I'm starting to think that the problem resides in Netcabo and not in Spamcop.

Anyway, could you please tell me if there is some IP address / URL for http://www.spamcop.net/ that does NOT belong to the Akamai network, so that I can Login directly there?

Thanks!

Link to comment
Share on other sites

Hi Jeff,

[No IP address for http://www.spamcop.net which does NOT belong to Akamai] has been published, sorry.

22040[/snapback]

OK, thanks anyway!

Today (31 Dec 2004), I can get to http://www.spamcop.net/ and Login with no problems.

Sure enough, the traceroutes now are also reaching their destination:

tracert www.spamcop.net

Tracing route to a369.g.akamai.net [212.113.163.51]
over a maximum of 30 hops:

  1   &lt;10 ms    10 ms    10 ms  10.19.79.254
  2    10 ms    10 ms    10 ms  vl-91.cr01pc09.netcabo.net [212.113.162.46]
  3    10 ms    10 ms    10 ms  ge-5-1.cr01pc01.netcabo.net [212.113.160.210]
  4   &lt;10 ms    10 ms    10 ms  vl-40.sr01pc02.netcabo.net [212.113.161.83]
  5    10 ms    10 ms    10 ms  vl-2.sr01pc01.netcabo.net [212.113.161.19]
  6    10 ms    10 ms    10 ms  a212-113-163-51.deploy.akamaitechnologies.com [212.113.163.51]

All's well that ends well! :)

Happy New Year!

Ricardo

Link to comment
Share on other sites

That is interesting ... the same path allowed by "us" but dead / now fixed from your connection .. one could take the view that the blockage was intentional <g> That there was an e-mail or two to netcabo folks asking about your situation may or may not have anything to do with the "it works" condition today <g> Welcome back! <g>

Link to comment
Share on other sites

I've had more than one occasion where I was on the phone about a problem while the tech was saying there was no problem, he puts me on hold for a minute and the problem "resolves itself" before he returns on the line. Actually quite amazing the power of hold ;)

Link to comment
Share on other sites

Hi Wazoo,

That is interesting ... the same path allowed by "us" but dead / now fixed from your connection .. one could take the view that the blockage was intentional <g>  That there was an e-mail or two to netcabo folks asking about your situation may or may not have anything to do with the "it works" condition today <g>  Welcome back! <g>

22106[/snapback]

Hmm... Do you mean that you sent an e-mail to the Netcabo support people regarding this? (I didn't)

And thanks: it feels good to "be back"! :)

Link to comment
Share on other sites

  • 2 weeks later...

What I'm getting now might be the same phenomenon but I don't think so (I've started another topic but I'm adding more info here just in case). It started at some unknown point between 16:30 GMT (let's say 9 hours ago) and "now". I used to be able to report spam with no problems. But suddenly i get "Invalid URL" instead. Traceroutes go very fast -- to a369.g.akamai.net which resolves to 194.78.133.222 or 194.78.133.224 in 4 hops and no more than 18 ms from Brussels, Belgium in the Skynet.be ADSL range (currently I'm at 80.200.115.201).

Link to comment
Share on other sites

Are you having any problems reaching other Akamaized sites? This sounds like a problem with your local Akamai EdgePlatform and Akamai's Optimized Extranet Customers' origin infrastructures, or perhaps just SpamCop's origin infrastructure. If it's just SpamCop, that should be reported to SpamCop Admins via their email address service at admin.spamcop.net.

Link to comment
Share on other sites

Are you having any problems reaching other Akamaized sites?  This sounds like a problem with your local Akamai EdgePlatform and Akamai's Optimized Extranet Customers' origin infrastructures, or perhaps just SpamCop's origin infrastructure.  If it's just SpamCop, that should be reported to SpamCop Admins via their email address service at admin.spamcop.net.

22889[/snapback]

At the moment I can report spam perfectly with IE6 but I cannot reach SC at all with FF. The reason why is a mystery to me. Even if I tell FF to "spoof" IE by changing its user-agent string, it's still no-go. How can I tell if the error is with Firefox, Akamai or Spamcop? Or with my own ISP?

Link to comment
Share on other sites

Ok... something is definately screwy at Akamai. I'm sitting in Dallas, Texas on a machine that has access to Level3, UUnet, Time Warner Telecom, Sprint and Global Crossing. Look at the horrendous route that just occured to get my traffic back to http://spamcop.net hosted at Akamai from here in Dallas:

Tracing route to spamcop.net [61.120.150.17]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1

2 6 ms 7 ms 7 ms [removed]

3 74 ms 75 ms 74 ms at-0-0-0-46.aggr02.dllstx.grandecom.net [24.155.

121.195]

4 81 ms 86 ms 68 ms ge-0-0-2.core01.dllstx.grandecom.net [24.155.121

.133]

5 200 ms 135 ms 193 ms POS3-0.GW5.DFW9.ALTER.NET [157.130.135.5]

6 99 ms 48 ms 29 ms 130.at-6-0-0.XR1.DFW9.ALTER.NET [152.63.100.50]

7 25 ms 21 ms 22 ms 0.so-2-0-0.XL1.DFW9.ALTER.NET [152.63.101.253]

8 21 ms 23 ms 21 ms 0.so-7-1-0.BR6.DFW9.ALTER.NET [152.63.97.58]

9 32 ms 21 ms 23 ms 204.255.174.230

10 23 ms 38 ms 31 ms p16-1-0-0.r20.dllstx09.us.bb.verio.net [129.250.

3.20]

11 75 ms 76 ms 75 ms p16-1-1-3.r20.plalca01.us.bb.verio.net [129.250.

4.105]

12 76 ms 75 ms 76 ms xe-0-2-0.r21.plalca01.us.bb.verio.net [129.250.4

.231]

13 78 ms 77 ms 78 ms p64-0-0-0.r21.mlpsca01.us.bb.verio.net [129.250.

5.49]

14 85 ms 81 ms 81 ms p16-3-0-0.r80.mlpsca01.us.bb.verio.net [129.250.

5.253]

15 190 ms 190 ms 189 ms p16-0-2-1.r21.tokyjp01.jp.bb.verio.net [129.250.

4.130]

16 190 ms 189 ms 189 ms xe-1-0-0.a20.tokyjp01.jp.ra.verio.net [61.213.16

2.234]

17 190 ms 189 ms 190 ms ge-2-2-0.7.a01.tokyjp01.jp.ra.verio.net [61.200.

92.35]

18 190 ms 189 ms 190 ms a61-120-150-17.deploy.akamaitechnologies.com [61

.120.150.17]

I'd say this could possibly explain why some people are having problems getting DNS to resolve now that Spamcop is using Akamai for DNS.

- Davoice

Link to comment
Share on other sites

Interesting .. and a bit of a problem now .. conversations going in 2 different Topics about the same problem (though noting that the discussion over in http://forum.spamcop.net/forums/index.php?showtopic=3425 has taken a turn towards an issue with FireFox ..??) ... anyway, funny that you hit Tokyo whereas yestrday I ended up in France .. very odd.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...