in not eternal shocker! Ah well you pays your money......
Conversely, I've had less trouble connecting since the name change than I did before. That's probably around the time I stopped seeing your posts. And now I can again. Weird.
Bear in mind that ping only works if ICMP Echo hasn't been filtered out. It's far from the ideal litmus test. The news server was rejecting connections for a bit earlier due to high load average but it's been usable again for a while now.
Same here. I only found out the name was changing when someone posted it on here - email still hasn't arrived confirming it so I assume a lot of people are unaware of the change so they're not connecting anymore meaning more connectivity for the rest of us.
The name change roughly coincided with a couple of the big US ISPs pulling their usenet services. I wouldn't be surprised if ES are getting hit by several thousand new users a week at the moment.
You'd never be able to ping any webserver that I was responsible for either. Assuming I controlled the firewalls as well.. Phil
There's up and there's up. You couldn't ping it, I read your post saying you couldn't ping it and replied to that post, both via the server you couldn't ping. It was, however, under very high load, so intermittently refusing logins. Some issues, I fear, are beyond the server administrator's control.
I believe the issue was... "Maintenance on the router infrastructure in one of the provider's datacenters caused an outage of both the primary and secondary LDAP and database servers, although only one of the subnets was supposed to be offline for a couple of minutes. Both servers were unreachable for more than two hours." .... according to Ray.
