[QUOTE=Uncwilly;347028]Seems that the server is down....
[url]http://www.downforeveryoneorjustme.com/http://www.gpu72.com/[/url][/QUOTE]

It's just you...

Uptime shows 160 days.

[url]http://gpu72.com[/url] works for me too. It seems the site checker isn't 100% reliable as it often mistakenly thinks Google is down.

[QUOTE=chalsall;347040]It's just you...

Uptime shows 160 days.[/QUOTE]

@UNC- you might add isup.me to your lineup of "on/off check" sites.

[QUOTE=Uncwilly;347028]Seems that the server is down....[/QUOTE]
[QUOTE=chalsall;347040]It's just you...

Uptime shows 160 days.[/QUOTE]
I tried several times over the course of an hour. Then I checked dfeojm it agreed. Next time I checked, about 1/4-1/2 hour after posting it was ok.

[QUOTE=Uncwilly;347044]I tried several times over the course of an hour. Then I checked dfeojm it agreed. Next time I checked, about 1/4-1/2 hour after posting it was ok.[/QUOTE]

OK... All I can tell you is this:

[CODE][22/Jul/2013:18:23:12 -0400] www.gpu72.com 50.97.161.229 - - "HEAD / HTTP/1.1" 200 - "-" "SiteCheck - http://downforeveryoneorjustme.com"
[22/Jul/2013:18:23:13 -0400] www.gpu72.com 50.97.161.229 - - "HEAD / HTTP/1.1" 200 - "-" "SiteCheck - http://downforeveryoneorjustme.com"
[22/Jul/2013:18:23:13 -0400] www.gpu72.com 50.97.161.229 - - "HEAD / HTTP/1.1" 200 - "-" "SiteCheck - http://downforeveryoneorjustme.com"
[22/Jul/2013:18:30:24 -0400] www.gpu72.com 50.97.161.229 - - "HEAD / HTTP/1.1" 200 - "-" "SiteCheck - http://downforeveryoneorjustme.com"
[22/Jul/2013:18:30:26 -0400] www.gpu72.com 50.97.161.229 - - "HEAD / HTTP/1.1" 200 - "-" "SiteCheck - http://downforeveryoneorjustme.com"
[22/Jul/2013:18:32:57 -0400] www.gpu72.com 50.97.161.229 - - "HEAD / HTTP/1.1" 200 - "-" "SiteCheck - http://downforeveryoneorjustme.com"
[22/Jul/2013:18:32:57 -0400] www.gpu72.com 50.97.161.229 - - "HEAD / HTTP/1.1" 200 - "-" "SiteCheck - http://downforeveryoneorjustme.com"
[22/Jul/2013:18:36:36 -0400] www.gpu72.com 50.97.161.229 - - "HEAD / HTTP/1.1" 200 - "-" "SiteCheck - http://downforeveryoneorjustme.com"
[22/Jul/2013:18:36:37 -0400] www.gpu72.com 50.97.161.229 - - "HEAD / HTTP/1.1" 200 - "-" "SiteCheck - http://downforeveryoneorjustme.com"
[22/Jul/2013:18:45:45 -0400] gpu72.com 50.97.161.229 - - "HEAD / HTTP/1.1" 301 - "-" "SiteCheck - http://downforeveryoneorjustme.com"
[22/Jul/2013:18:58:32 -0400] www.gpu72.com 50.97.161.229 - - "HEAD / HTTP/1.1" 200 - "-" "SiteCheck - http://downforeveryoneorjustme.com"
[22/Jul/2013:18:58:32 -0400] www.gpu72.com 50.97.161.229 - - "HEAD / HTTP/1.1" 200 - "-" "SiteCheck - http://downforeveryoneorjustme.com"
[/CODE]

[QUOTE=Uncwilly;347044]I tried several times over the course of an hour. Then I checked dfeojm it agreed. Next time I checked, about 1/4-1/2 hour after posting it was ok.[/QUOTE]

I have to second Unc's opinion, though I just waited and did not seek a second opinion. Perhaps he and I are on the same plugged tube in the interwebs? Both View Assignments and Individual Overall Statistics were giving me this:

[QUOTE][B]Internal Server Error[/B]

The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, [EMAIL="chalsall@ideas4lease.com"]chalsall@ideas4lease.com[/EMAIL] and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Apache/2.2.3 (CentOS) Server at [URL="http://www.gpu72.com"]www.gpu72.com[/URL] Port 80[/QUOTE]

I got that same message a while ago as well, seems to be fine now.

Straight after he posted I checked his link and it said down.

[QUOTE=henryzz;347108]Straight after he posted I checked his link and it said down.[/QUOTE]

Sucks to be me, huh?

[QUOTE=chalsall;347133]Sucks to be me, huh?[/QUOTE]

Actually, doesn't it suck to have users with bad DNS, behind plugged up routers? I am quite happy to go with the "clogged tubes in the interwebs" theory.

Is there a reason that the 62M LL range at 73 bit never gets assigned? :max:

If one goes to the request page and leave everything with the default values, we get exponent in the 63M range to factor from 73 to 74. We need to specify the optional range min and max value to get exponent in the 62M range. :cry: