Any 1&1 email users?

[Rik]

I'm getting a lot of timeouts to their servers. Anyone else?

[Glenn]

I use them for one of my email address's but not noticed anything today.

[Rik]

Thanks, Glenn. I'll go take a look at the site.

[scook94]

Yup Rik, I use them for my email and web hosting. Can't reach my site or 1and1. Tried a tracert and get nowhere after redbus-gw2-g0-1-331.idnet.net.

[Rik]

Both my control panel and their main site are timing out too.

[Glenn]

I sent myself a test email, it hasn't arrived so far

[Rik]

I've switched to OpenDNS but can't reach it that way either, so it's not an IDNet DNS issue, anyway. I must go and take a look on TB...

[scook94]

http://downforeveryoneorjustme.com/ is telling me my site is up....

[Rik]

Same here. It's not DNS as I've switched to OpenDNS at the moment, there's nothing I could see being reported on TB. I might just fire off an email to IDNet.

[scook94]

judging by my tracert it's either not getting off idnet or it's the first hop.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\cooks1>tracert www.1and1.co.uk

Tracing route to www.1and1.co.uk [212.227.126.68]
over a maximum of 30 hops:

  1    35 ms     4 ms     4 ms  192.168.1.1
  2   118 ms    32 ms    29 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    31 ms    31 ms    30 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    32 ms    30 ms    31 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
10     *        *        *     Request timed out.
11     *        *        *     Request timed out.
12     *        *        *     Request timed out.
13     *        *        *     Request timed out.
14     *        *        *     Request timed out.
15     *        *        *     Request timed out.
16     *        *        *     Request timed out.
17     *        *        *     Request timed out.
18     *        *        *     Request timed out.
19     *        *        *     Request timed out.
20     *        *        *     Request timed out.
21     *        *        *     Request timed out.
22     *        *        *     Request timed out.
23     *        *        *     Request timed out.
24     *        *        *     Request timed out.
25     *        *        *     Request timed out.
26     *        *        *     Request timed out.
27     *        *        *     Request timed out.
28     *        *        *     Request timed out.
29     *        *        *     Request timed out.
30     *        *        *     Request timed out.

Trace complete

[Inactive]

A clue may be that ISPReview is hosted there I think, that has been down for a while.

[madasahatter]

Try to get to it from www.hidemyass.com

Edit: Nope can't get to ispreview through there either

[scook94]

Can get to my site through hidemyass but not direct. Would that indicate an IDnet routing issue?

[Rik]

I suspect an IDNet routing issue, I can get to three sites through the proxy that are timing out with IDNet. Reported.

[madasahatter]

It would indicate that something is going on - not sure what though - ties in with issues on another couple of threads.

Are we acting as early warning again?  

Anyway, on the good side, at least you know that your site is up  

[madasahatter]

That's issues two weekends running isn't it Rik? 

[Inactive]

I am almost certain that ISPReview is hosted at 1&1, I seem to recall that they are located in Germany?

[scook94]

It would indicate that something is going on - not sure what though - ties in with issues on another couple of threads.

Are we acting as early warning again?  

Anyway, on the good side, at least you know that your site is up  

haha, as I'm the only one who ever visits it, it may as well be down!

[scook94]

Correct In, they are, 1and1 are German based.

[Rik]

That's issues two weekends running isn't it Rik? 

I've reported all three URLs that I know of, so hopefully someone will take a look shortly.

Yup, Saturday, then Sunday - but this week Simon is on holiday.

[kinmel]

I can reach 1&1 through the proxyserver at Proogly

[Inactive]

Yup, Saturday, then Sunday - but this week Simon is on holiday.

I don't recall any of us giving him permission.

[Inactive]

Correct In, they are, 1and1 are German based.

Thanks.

[Rik]

I can reach 1&1 through the proxyserver at Proogly

Thanks, Alan.

[scook94]

My site is back up, anyone else?

[Rik]

Same here.   All the affected sites I reported seem to have been sorted. 45 mins, not bad for a Sunday. 

[scook94]

The next hop after idnet's is on oneandone.net's router so it would be interesting to know which side had the problem...

[Rik]

Given the other sites involved, I'd say IDNet, but that may be prejudging.

[Sebby]

We all had email problems about an hour ago, but all seems fine now.

[Rik]

1&1 email, Sebby?

[Glenn]

I just received my test email

[Sebby]

Yep, 1&1.

[Rik]

I'm beginning to think maybe it was 1&1, Glenn, stuff seems to be moving through quite slowly.

Thanks for the confirmation, Seb.

[Inactive]

Confirm ISP Review working again.

[Rik]

It's either a routing problem at IDNet or a 1&1 issue. My instinct is swinging to the latter, now, In, simply because 1&1 mail appears to be moving slowly, and that wouldn't apply if it was merely routing from IDNet. I stand to be corrected, of course.

[madasahatter]

I would have thought that if it had been a 1&1 issue, your sites would not have been available even through another proxy, which I though they were?

[Rik]

Unless the site was caching, of course. I didn't try to login to the webmail interface.

[Sebby]

I couldn't get onto webmail, either.

[Rik]

Thanks, Sebby, that seems to confirm it was 1&1. I'm just surprised that I didn't come across any reports at TB.

[madasahatter]

I couldn't get onto webmail, either.

Was that through IDNet or another proxy Sebby?

[Sebby]

That was through IDNet, so again, it could have been a routing issue.

[madasahatter]

Is it possible to find out from IDNet if it was our end, and what the problem was? Just out of interest and to be sure on eway or the other.

[Rik]

The fault was reported, so I should get something back in due course. If not, I'll follow up tomorrow.

[madasahatter]

Cheers Rik - I'm a nosey son of a hoob ain't I? 

[Inactive]

Cheers Rik - I'm a nosey son of a hoob ain't I? 

I reckon your Father may well have been a Muppet Mad, get your DNA checked out.. 

[Rik]

Cheers Rik - I'm a nosey son of a hoob ain't I? 

No more than the rest of us.

[madasahatter]

I reckon your Father may well have been a Muppet Mad, get your DNA checked out.. 

[scook94]

Did you get any feedback on this Rik?

[madasahatter]

I was wondering that too

[Sebby]

IDNet are still looking into this.

It could have been a routing issue, but if it was, it sorted itself out, so it's a case of trying to work out if this was the case.

Does that make sense?

[madasahatter]

Cheers Sebby 

[Rik]

What Sebby said. Hopefully, I'll hear more today. They did confirm all the affected sites were 1&1 hosted, which would normally make me think the issue was a 1&1 one, but I couldn't find reports anywhere else so...

[Inactive]

I don't think it was 1&1 Rik, ISP Review is hosted there, I asked if anyone else had been unable to access the site, the answer was no.

[Rik]

Thanks, In.

[Rik]

The lovely Miriam has finished checking this:

From office (1 hop more to get to redbus so hop numbers differ)

5  redbus-gw2-g0-1-331.idnet.net (212.69.63.5)  6.394 ms  6.368 ms  6.435 ms
6  amsix.bb-c.nkf.ams.nl.oneandone.net (195.69.144.220)  14.792 ms  25.967 ms 
15.441 ms

This shows that either 1+1 had the problem, the link between Amsix and Redbus
had a problem or Amsix had a problem. Our router graphs seem to indicate no
abnormalities on our link to Amsix and that we were sending a usual amount of
traffic down the link which would seem it was 1+1's link to Amsix that was
the problem. (this would not likely show on 1+1's monitoring system as the
actual servers and their main hosting centre would have been completely up
with full traffic from the main internet - its just the routing from peers at
amsix would that may have had an issue)

[Inactive]

Thanks Rik, that has made it all as clear as mud.

[Rik]

I think I understand - just don't ask me to explain it.

[madasahatter]

Still doesn't really explain how we were able to get to their sites through another proxy though??? 

[Rik]

Different peering being used by the proxy, Mad.

[madasahatter]

get ya - we were just unucky to be using that route then 

[Rik]

Looks that way. How you ever prevent this kind of issue I don't know, short of built-in redundancy at every level.

[Danni]

I think I understand it. I've also has similar problems to my server (and other servers hosted in the same data centre) in the past.

I think that the route IDNet takes to 1and1 goes through Amsix, who were having a routing problem. Accessing through a proxy bypasses Amsix, so it worked fine.

[Rik]

That's how I understand it, Danni. From the IDNet end, the link to Amsix looked fine, from the 1&1 end it looked fine. Somewhere in the middle, things were disappearing into a black hole.

[Danni]

Yup You said you couldn't explain it, so I tried

[Rik]

And succeeded brilliantly. 

[Danni]

Thank you

[Sebby]

Yep, I understood it.

[madasahatter]

Even I understood it Danni - thanks 

[Sebby]

She must be good...

[madasahatter]