Serious routing problems

[VolkerSchulz]

As of yesterday I can't connect to some of the servers located in my computer center in Germany anymore. It was working before and it still works for some but not for other servers. When attempting to connect to those, which are not working, a specific router (within the SBC network) seems to be involved.

Here are the trace routes:

For 81.209.144.3 (not working) it's:

Tracing route to pop.fn2.de [81.209.144.3]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  home [192.168.1.254]
  2    18 ms    17 ms    16 ms  bras14-l0.lsanca.sbcglobal.net [51.164.186.14]
  3    16 ms    15 ms    15 ms  dist4-vlan60.lsanca.sbcglobal.net [216.102.181.2]
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
[...]
 30     *        *        *     Request timed out.

Trace complete.

For 81.209.144.10 (working) it's:

Tracing route to capuzza.net [81.209.144.10]
over a maximum of 30 hops:

  1     3 ms     2 ms     3 ms  home [192.168.1.254]
  2    17 ms    15 ms    17 ms  bras14-l0.lsanca.sbcglobal.net [151.164.186.14]

  3    13 ms    15 ms    15 ms  dist3-vlan50.lsanca.sbcglobal.net [64.161.163.21
4]
  4    12 ms    16 ms    15 ms  bb1-g1-0-1.lsanca.sbcglobal.net [151.164.42.78]

  5    71 ms    70 ms    70 ms  151.164.40.53
  6    74 ms    72 ms    72 ms  Equinix-Ash.DC-1-eth020.us.lambdanet.net [206.22
3.115.97]
  7   147 ms   147 ms   149 ms  LON-2-pos210.uk.lambdanet.net [81.209.156.29]
  8   160 ms   157 ms   157 ms  DUS-1-pos700.de.lambdanet.net [82.197.136.17]
  9   159 ms   159 ms   159 ms  DUS-5-pos300.de.lambdanet.net [217.71.96.54]
 10   159 ms   159 ms   161 ms  atm011-gw.fn2.de [217.71.104.106]
 11   159 ms   159 ms   159 ms  s1web1.fn2.de [81.209.144.10]

Trace complete.

As you can see, they are within the same class-c net (and actually standing right next to each other), so I don't know why AT&T makes them to use different routes. I've tried to connect to some other European severs randomly, some were working, some were not. Everytime the dist4-vlan60.lsanca.sbcglobal.net [216.102.181.2] was involved, the connection timed out in the next hop. I'm also experiencing problems when talking to my German friends via IM. Every other message doesn't go through.

I've then tried to reset the modem. Weird enough I figured out that the non-working server was taking the working route now but the one that was previously working takes the broken route now and the connection times out on that one.

I guess one of their routers died, but the AT&T email support and even the second level tech phone support could not be of any help.

To proof that it is an SBC problem, I connected to the internet through dial-up and through my cell phone. Either option was working perfectly. It's not the solution tho, because it's damn slow and rediculously expensive!

So does anybody have an idea on how to solve that problem or does anybody actually know someone working for AT&T Yahoo! who has technical skills at all?

Any help will be greatly appreciated.

Volker