Tucson gateway problems??

[PlugNickel]

Tucson Exede gateway went down at about 4:54 pm Mountain Time with modem unable to enter network and didn't come back until about 6:37 pm...

It's 8:40 pm and the speed is now about 400kbps...not exactly blistering speed.

Anybody working on this?

Maybe you are and maybe you aren't...

I have no way of knowing since nobody seems to think that using this forum to let their customers know what's actually going on is perhaps...just maybe a good idea?

You know...nothing complicated; perhaps just a little note that says " we are experiencing some problems on (insert gateway / beam / or what not) and that we are working to resolve the problem"?

Oh wait...it's 8:45 pm and it's disconnected again....

Oy

[Phainein]

Tucson Exede gateway went down

I think Phoenix Server has an issue....Phoenix AcceleNet Server: Issues?

Tracert works...but page timeouts happen mostly.

I wish Wildblue World had separate Section for this type of stuff.

[Seether]

I'm in the mountains about an hour west of Denver & think I'm on that gateway too. Nothing but trouble here since early evening.

I've had to revert to my back up Verizon MiFi. Not ideal but at least I can get a tiny bit of work done.

Does WildBlue not have any kind of network status page for customers to access?

[Phainein]

think I'm on that gateway too.

do a DOS Command:

tracert 24.25.224.142

And on the sixth hop, what city name is there?

[TexasRebel]

do a DOS Command:

tracert 24.25.224.142

And on the sixth hop, what city name is there?

Tracing route to ge3-1-0.oahuhimail-10k1.hawaii.rr.com [24.25.224.142]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms SCALAR [192.168.1.251]
2 * * * Request timed out.
3 601 ms 649 ms 628 ms 10.71.101.1
4 599 ms 651 ms 667 ms 10.71.10.2
5 629 ms 620 ms 671 ms 10.71.255.21
6 603 ms 639 ms 668 ms hlr-edge-09.inet.qwest.net [63.156.186.13]
7 634 ms 640 ms 637 ms dvr-brdr-02.inet.qwest.net [67.14.24.118]
8 665 ms 778 ms 661 ms 63.146.26.130

This is quite different than most times.. I'm seeing qwest.net in the hops rather than Level3.net.

and here's a whopping record breaker for me at just after midnight..



-TexasRebel

[Seether]

do a DOS Command:

tracert 24.25.224.142

And on the sixth hop, what city name is there?

Looks like Phoenix:


Tracing route to ge3-1-0.oahuhimail-10k1.hawaii.rr.com [24.25.224.142]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms THRILLKILLKULT [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 638 ms 639 ms 639 ms 10.74.10.2
5 627 ms 639 ms 638 ms 10.74.255.21
6 627 ms 631 ms 638 ms vlan263.car1.Phoenix1.Level3.net [4.53.104.177]

[Phainein]

6 ....hlr-edge-09.inet.qwest.net [63.156.186.13]

This is quite different than most times.. I'm seeing qwest.net in the hops rather than Level3.net.

I'm wonder if they dropped "Level...whoever?" Or just added an additional provider.

Cheyene has Gateways...but I don't know if they changed total network system for processing all requests (legacy/Exede) in Denver now. If so, Denver would have a large server setup there, requiring lots of bandwidth.

[PlugNickel]

It seems that service on the Tucson gateway went down at 6:44 am mountain time.

Anyone else in Colorado or on the Tucson gateway having problems?

[PlugNickel]

Service returned at about 10:30 am mountain time.

[PlugNickel]

Spoke too soon, down again.......