[ADBjester]

Hi Scarr,

Well, we do have a pretty good idea.....

9 --- [ 144.232.9.95], Pings=3 , Quality=20 , Lost=2 , Min=16 , Max=16 , Avg=16
History: 16, -1, -1, 16, 16,
10 --- [ 144.232.20.16], Pings=5 , Quality=100 , Lost=0 , Min=16 , Max=141 , Avg=47
History: 31, 16, 31, 16, 141,
11 --- [ 144.232.20.17], Pings=4 , Quality=60 , Lost=1 , Min=15 , Max=125 , Avg=42
History: 16, -1, 125, 15, 15,
12 --- [ 144.232.20.16], Pings=5 , Quality=100 , Lost=0 , Min=15 , Max=31 , Avg=18
History: 15, 15, 31, 15, 16,
13 --- [ 144.232.20.17], Pings=3 , Quality=50 , Lost=1 , Min=15 , Max=32 , Avg=21
History: 32, -1, 16, 15,
14 --- [ 144.232.20.16], Pings=5 , Quality=100 , Lost=0 , Min=15 , Max=31 , Avg=21
History: 31, 31, 16, 15, 16,
15 --- [ 144.232.20.17], Pings=3 , Quality=50 , Lost=1 , Min=15 , Max=31 , Avg=20
History: 15, -1, 31, 16,

Ad infinitum until packets dropped.

These two routers, apparently in Ft. Worth on Sprintlink, had a circular route, and packets just ping-ponged until TTL was exceeded and the data dropped.

This is likely why SBC had no idea what was happening. It was not on their network. We got this data just about as you were all reconnecting, so I'm sure that Sprint knew about this and was scrambling to fix it.

In any case, I'm quite glad everyone's back online.

Best Regards,

Jeff
PokerStars Support Supervisor