Anyone experiencing probs with uswest.net today?

Anyone experiencing probs with uswest.net today?

Post by Sam Evan » Sun, 11 Apr 1999 04:00:00



Seems like this started yesterday morning, but, for some reason or another,
I'm getting some seriously bad ping times, and download speeds through my
DSL Connection w/USWest.net ..  Here's a little of what I've found:

5  554.Hssi3-0-0.GW1.SLT1.ALTER.NET (157.130.161.101)  32.237 ms  34.430 ms
30.932 ms
6  124.ATM4-0-0.CR2.SFO1.Alter.Net (137.39.68.81)  48.779 ms  46.998 ms
54.830 ms
7  111.ATM2-0.XR1.SFO1.ALTER.NET (146.188.148.154)  48.779 ms  376.865 ms
351.559 ms
8  * 287.ATM1-0.TR1.SCL1.ALTER.NET (146.188.147.154)  611.514 ms  780.883 ms

As you can see, it looks like Alter.net is having some serious issues, but,
you'd think USWest.net might care, since they use Alternet/UUNet as a
backbone.  After talking to a tier 2 tech she mentioned it could wait until
Monday....

If anyone else is noticing that they are getting slow speeds w/their DSL and
Uswest.net since a couple days ago, please let me know, I'd like to know
it's not just me, contrary to their tech support's belief.

I also did one other test to http://www.uswest.net and here's it's results.

traceroute to www.uswest.net (204.147.80.81), 30 hops max, 40 byte packets

 6  sjc1-core2-fa10-0-0.atlas.digex.net (165.117.54.146)  44.841 ms  43.662
ms  43.555 ms
 7  oma1-core1-s8-0-0.atlas.digex.net (165.117.56.237)  75.923 ms  86.077 ms
oma1-core1-h8-0.atlas.digex.net (165.117.50.17)  83.970 ms
 8  oma1-core2-fa6-0-0.atlas.digex.net (165.117.53.18)  88.656 ms  111.903
ms  87.942 ms
 9  ord1-core2-s1-0-0.atlas.digex.net (165.117.50.13)  99.121 ms  102.619 ms
110.445 ms
10  msp1-core1-s4-0-0.atlas.digex.net (165.117.53.149)  113.051 ms  111.894
ms  105.141 ms
11  204.91.153.18 (204.91.153.18)  116.378 ms  112.646 ms  118.396 ms
12  207.225.159.252 (207.225.159.252)  117.025 ms  378.359 ms  401.903 ms
13  * www.uswest.net (204.147.80.81)  288.300 ms  594.076 ms

Would appear that 207.225.159.252 is where the problem starts.  And yes,
even going to www.uswest.net is sloooww.  Anyhow, I'd be curious to know if
it's just me, or if anyone else is having the same probs.

 
 
 

Anyone experiencing probs with uswest.net today?

Post by Sam Evan » Sun, 11 Apr 1999 04:00:00


Sorry..  Should have made my post clearer, but, I know it's not USWest
that's having the problem (atleast I don't believe it is) but more a
Backbone issue, anyone else having this problem?

Sorry for the confusion and false accusation.
-Sam


Quote:> Seems like this started yesterday morning, but, for some reason or
another,
> I'm getting some seriously bad ping times, and download speeds through my
> DSL Connection w/USWest.net ..  Here's a little of what I've found:

> 5  554.Hssi3-0-0.GW1.SLT1.ALTER.NET (157.130.161.101)  32.237 ms  34.430
ms
> 30.932 ms
> 6  124.ATM4-0-0.CR2.SFO1.Alter.Net (137.39.68.81)  48.779 ms  46.998 ms
> 54.830 ms
> 7  111.ATM2-0.XR1.SFO1.ALTER.NET (146.188.148.154)  48.779 ms  376.865 ms
> 351.559 ms
> 8  * 287.ATM1-0.TR1.SCL1.ALTER.NET (146.188.147.154)  611.514 ms  780.883
ms

> As you can see, it looks like Alter.net is having some serious issues,
but,
> you'd think USWest.net might care, since they use Alternet/UUNet as a
> backbone.  After talking to a tier 2 tech she mentioned it could wait
until
> Monday....

> If anyone else is noticing that they are getting slow speeds w/their DSL
and
> Uswest.net since a couple days ago, please let me know, I'd like to know
> it's not just me, contrary to their tech support's belief.

> I also did one other test to http://www.uswest.net and here's it's
results.

> traceroute to www.uswest.net (204.147.80.81), 30 hops max, 40 byte packets

>  6  sjc1-core2-fa10-0-0.atlas.digex.net (165.117.54.146)  44.841 ms
43.662
> ms  43.555 ms
>  7  oma1-core1-s8-0-0.atlas.digex.net (165.117.56.237)  75.923 ms  86.077
ms
> oma1-core1-h8-0.atlas.digex.net (165.117.50.17)  83.970 ms
>  8  oma1-core2-fa6-0-0.atlas.digex.net (165.117.53.18)  88.656 ms  111.903
> ms  87.942 ms
>  9  ord1-core2-s1-0-0.atlas.digex.net (165.117.50.13)  99.121 ms  102.619
ms
> 110.445 ms
> 10  msp1-core1-s4-0-0.atlas.digex.net (165.117.53.149)  113.051 ms
111.894
> ms  105.141 ms
> 11  204.91.153.18 (204.91.153.18)  116.378 ms  112.646 ms  118.396 ms
> 12  207.225.159.252 (207.225.159.252)  117.025 ms  378.359 ms  401.903 ms
> 13  * www.uswest.net (204.147.80.81)  288.300 ms  594.076 ms

> Would appear that 207.225.159.252 is where the problem starts.  And yes,
> even going to www.uswest.net is sloooww.  Anyhow, I'd be curious to know
if
> it's just me, or if anyone else is having the same probs.


 
 
 

Anyone experiencing probs with uswest.net today?

Post by Charlie &am » Tue, 13 Apr 1999 04:00:00




Quote:> UGH!!!!!!

> Tracing route to www.uswest.net [204.147.80.81]
> over a maximum of 30 hops:

How do you figure it's over 30 hops?  You got blackholed getting to
hop 12, the destination:

11  207.225.159.220 (207.225.159.220)  83.862 ms  81.305 ms  89.294 ms
12  www.uswest.net (204.147.80.81)  81.540 ms  84.565 ms  80.903 ms

Paul

Quote:>   1    28 ms    34 ms    33 ms  sense-sea-MegaBit-121-1.oz.net
> [216.39.144.1]
>   2    21 ms    20 ms    20 ms  sense-sea-core-e03.oz.net
> [216.39.150.17]
>   3    21 ms    20 ms    20 ms  sense-n-gw.semaphore.net
> [207.17.119.77]
>   4    20 ms    20 ms    22 ms  903.Hssi5-0.GW1.SEA1.ALTER.NET
> [137.39.136.21]
>   5    26 ms    27 ms    23 ms  103.ATM2-0.XR1.SEA1.ALTER.NET
> [146.188.200.34]
>   6    21 ms    32 ms    46 ms  195.ATM3-0.TR1.SEA1.ALTER.NET
> [146.188.200.102]

>   7    63 ms    63 ms    62 ms  110.ATM7-0.TR1.CHI4.ALTER.NET
> [146.188.136.165]

>   8    64 ms    74 ms    73 ms  199.ATM6-0.XR1.CHI6.ALTER.NET
> [146.188.208.241]

>   9    74 ms    77 ms    79 ms  191.ATM9-0-0.GW2.MSP1.ALTER.NET
> [146.188.209.121
> ]
>  10    76 ms    78 ms    86 ms  uswmsp-gw.customer.ALTER.NET
> [157.130.96.166]
>  11    79 ms    82 ms   101 ms  207.225.159.220
>  12     *        *        *     Request timed out.
>  13     *        *        *     Request timed out.
>  14     *        *        *     Request timed out.
>  15     *        *        *     Request timed out.
>  16     *        *        *     Request timed out.
>  17     *        *        *     Request timed out.

--
The lotto must be rigged, I should have won by now.
 
 
 

1. USWest.net and staying connected probs...

I have USWest as my internet provider and I always seem to lose my
connection everyonce and a while.  I have the 256 deluxe (always on) and
there are no timers set on the modem as far as i can tell.  It seems that I
lose connection for a sec or two and then am fine.  The light for the WAN
connection never goes off when I do.  When i am on ICQ after 20 mins or so
it will lose its connection to the internet and I will have to close it down
and restart it later for it to establish a connection again.  Could these
problems be cause by my dsl modem's NAT?  If I were to go ahead and get
static IP's, would this problem still happen?  Also, I am unable to view
streaming media because of the "firewall" that the modem provides.  I have
contacted USWest support and they keep telling me that they can't help
me...(typical phone company)...

Any suggestions...?
-JM

2. MFC 4550 Beep Codes

3. Verizon DSL - anyone experiencing a slowdown in NYC today?

4. Terminal Services Client

5. 256k upgraded to 512k+ saved $2 a month sitched to USWEST.NET

6. Problems with boot up of Win98SE on laptop

7. USWest.net, Cisco 675, And Bridging Mode.

8. Growing stack with djgpp

9. Uswest.net web cache server...other ISP's doing this too?

10. ICQ and USWest.net MegaPak

11. Fed up with USWEST.net going to TCI Cable

12. Help please: CUSeeMe through Cisco 675 using USWest.net

13. Uswest.net and MS Proxy Server