sprint outage

Paul Miner wrote:

>> Bad flooding in Reno caused Sprint to re-route voice and data traffic to
>> Phoenix, so Phoenix had heavy traffic to begin with. Then we ended up with
>> the fiber cut...
>
> Yes, I know about the outage and its cause.

I figured you and some others might, but not everyone did.

I was commenting on and
> laughing at ynaught13's claim that the outage was causing Sprint's
> stock to plummet.

Yeah. Li'l ole me, Mr. Now-in-my-17th-year-on-Usenet, should have known
better than to followup. I should have started a new thread.

--
Steve Sobol, Professional Geek 888-480-4638 PGP: 0xE3AE35ED
Company website: http://JustThe.net/
Personal blog, resume, portfolio: http://SteveSobol.com/
E: [email protected] Snail: 22674 Motnocab Road, Apple Valley, CA 92307

---

› See More: sprint outage

JMann101 wrote:
> Sprint together with Nextel is currently being upgraded to provide you
> with a better customer experience. We apologize for the inconvenience.
>
> Our technical experts are working overtime to complete the upgrade
> process.
>
> In order to enhance our customer's wireless experience, we are making
> modifications to our servers at this time. I sincerely apologize for
> the
> inconvenience this has caused you. There are some technical discrepancy

No mention of a "cable cut" somewhere "between Phoenix and Palm
Springs" HA!
A classic crash after a weekend software update. People got back from
lunch at
1 PM PST and started making tons of phone calls, crashing the "servers"
at 1:30 PM.

If it was truely a cable cut, thats one sorry *ss network design. 2
down cables and the
entire West Coast crashes.

> for some time due to regular maintenance and constant updates which
> might have slowed down our servers. We assure you that this technical
> issue will be resolved very soon as our technical experts (INDIA) are working
> very hard to provide you the best wireless service.

Hmm, a software version that was rush tested over xmas holidays and
shipped
to the customer without load testing. The customers provided the final
"load test"
on Monday. Test failed

JG

Where did you obtain your information that lead you to this conclusion?
State only facts and hard evidence please.

<[email protected]> wrote in message
news:[email protected]...
>
> JMann101 wrote:
>> Sprint together with Nextel is currently being upgraded to provide you
>> with a better customer experience. We apologize for the inconvenience.
>>
>> Our technical experts are working overtime to complete the upgrade
>> process.
>>
>> In order to enhance our customer's wireless experience, we are making
>> modifications to our servers at this time. I sincerely apologize for
>> the
>> inconvenience this has caused you. There are some technical discrepancy
>
> No mention of a "cable cut" somewhere "between Phoenix and Palm
> Springs" HA!
> A classic crash after a weekend software update. People got back from
> lunch at
> 1 PM PST and started making tons of phone calls, crashing the "servers"
> at 1:30 PM.
>
> If it was truely a cable cut, thats one sorry *ss network design. 2
> down cables and the
> entire West Coast crashes.
>
>> for some time due to regular maintenance and constant updates which
>> might have slowed down our servers. We assure you that this technical
>> issue will be resolved very soon as our technical experts (INDIA) are
>> working
>> very hard to provide you the best wireless service.
>
> Hmm, a software version that was rush tested over xmas holidays and
> shipped
> to the customer without load testing. The customers provided the final
> "load test"
> on Monday. Test failed
>
> JG
>

Mij Adyaw wrote:
> Where did you obtain your information that lead you to this
> conclusion? State only facts and hard evidence please.
>

C'mon, Mij, he doesn't have any. My guess is that he was reminded of a
job he once botched. Ergo, he now assumes everyone is just as inept.
Facts be dammed, AP be damned, he just "knows" it was a software upgrade
gone bad. (The email from Sprint, that prompted his nonsense, was in no
way referring to the cable incident--it was a canned/semi-canned
response based on upgrades that have been going on for months.)


--
Mike

Mij Adyaw wrote:
> Where did you obtain your information that lead you to this conclusion?
> State only facts and hard evidence please.

The statement from E-care mentions nothing about "cables", only
"constant updates which might have slowed down our servers. We assure
you"

No mention of the cause of the "cable cut" in Buckeye, AZ.
Ergo, they tried a public excuse of "cable cuts". Blaming outside
"evil-doers"
and mud slides for the major WEST COAST service crash.
Baboo software at your service.
JG

>
> <[email protected]> wrote in message
> news:[email protected]...
> >
> > JMann101 wrote:
> >> Sprint together with Nextel is currently being upgraded to provide you
> >> with a better customer experience. We apologize for the inconvenience.
> >>
> >> Our technical experts are working overtime to complete the upgrade
> >> process.
> >>
> >> In order to enhance our customer's wireless experience, we are making
> >> modifications to our servers at this time. I sincerely apologize for
> >> the
> >> inconvenience this has caused you. There are some technical discrepancy
> >
> > No mention of a "cable cut" somewhere "between Phoenix and Palm
> > Springs" HA!
> > A classic crash after a weekend software update. People got back from
> > lunch at
> > 1 PM PST and started making tons of phone calls, crashing the "servers"
> > at 1:30 PM.
> >
> > If it was truely a cable cut, thats one sorry *ss network design. 2
> > down cables and the
> > entire West Coast crashes.
> >
> >> for some time due to regular maintenance and constant updates which
> >> might have slowed down our servers. We assure you that this technical
> >> issue will be resolved very soon as our technical experts (INDIA) are
> >> working
> >> very hard to provide you the best wireless service.
> >
> > Hmm, a software version that was rush tested over xmas holidays and
> > shipped
> > to the customer without load testing. The customers provided the final
> > "load test"
> > on Monday. Test failed
> >
> > JG
> >

[email protected] wrote:
> Mij Adyaw wrote:
> > Where did you obtain your information that lead you to this conclusion?
> > State only facts and hard evidence please.
>
> The statement from E-care mentions nothing about "cables", only
> "constant updates which might have slowed down our servers. We assure
> you"
>
> No mention of the cause of the "cable cut" in Buckeye, AZ.
> Ergo, they tried a public excuse of "cable cuts". Blaming outside
> "evil-doers"
> and mud slides for the major WEST COAST service crash.
> Baboo software at your service.

>From the stock charts on Monday and Tuesday, looks like a combo of
Nortel
and Alcatel equipment failure.

> JG
>
> >
> > <[email protected]> wrote in message
> > news:[email protected]...
> > >
> > > JMann101 wrote:
> > >> Sprint together with Nextel is currently being upgraded to provide you
> > >> with a better customer experience. We apologize for the inconvenience.
> > >>
> > >> Our technical experts are working overtime to complete the upgrade
> > >> process.
> > >>
> > >> In order to enhance our customer's wireless experience, we are making
> > >> modifications to our servers at this time. I sincerely apologize for
> > >> the
> > >> inconvenience this has caused you. There are some technical discrepancy
> > >
> > > No mention of a "cable cut" somewhere "between Phoenix and Palm
> > > Springs" HA!
> > > A classic crash after a weekend software update. People got back from
> > > lunch at
> > > 1 PM PST and started making tons of phone calls, crashing the "servers"
> > > at 1:30 PM.
> > >
> > > If it was truely a cable cut, thats one sorry *ss network design. 2
> > > down cables and the
> > > entire West Coast crashes.
> > >
> > >> for some time due to regular maintenance and constant updates which
> > >> might have slowed down our servers. We assure you that this technical
> > >> issue will be resolved very soon as our technical experts (INDIA) are
> > >> working
> > >> very hard to provide you the best wireless service.
> > >
> > > Hmm, a software version that was rush tested over xmas holidays and
> > > shipped
> > > to the customer without load testing. The customers provided the final
> > > "load test"
> > > on Monday. Test failed
> > >
> > > JG
> > >

[email protected] wrote:
> Mij Adyaw wrote:
>> Where did you obtain your information that lead you to this
>> conclusion? State only facts and hard evidence please.
>
> The statement from E-care mentions nothing about "cables", only
> "constant updates which might have slowed down our servers. We assure
> you"
>

What part of "facts and hard evidence" didn't you understand?

Your tirade over losing a job is stale. Get help.


--
Mike

[email protected] wrote:
> Mij Adyaw wrote:
>> Where did you obtain your information that lead you to this conclusion?
>> State only facts and hard evidence please.
>
> The statement from E-care mentions nothing about "cables", only
> "constant updates which might have slowed down our servers. We assure
> you"


So you're relying on a canned response from Sprint e-care, which has
been known for years as being unable to "resolve" itself out of a wet
paper bag, and treating that canned response as gospel? What's wrong
with this picture?

--
E-mail fudged to thwart spammers.
Transpose the c's and a's in my e-mail address to reply.

Isaiah Beard wrote:
> [email protected] wrote:
> > Mij Adyaw wrote:
> >> Where did you obtain your information that lead you to this conclusion?
> >> State only facts and hard evidence please.
> >
> > The statement from E-care mentions nothing about "cables", only
> > "constant updates which might have slowed down our servers. We assure
> > you"
>
>
> So you're relying on a canned response from Sprint e-care, which has
> been known for years as being unable to "resolve" itself out of a wet
> paper bag, and treating that canned response as gospel? What's wrong
> with this picture?

The second "cable cut", reportedly in Buckeye Arizona, has not been
explained.
Who or what caused it? Bin Laden? UFOs? Chip Monks?

If in fact "cut cables" are the reason, the fact remains that Sprint's
Wireless and Long Distance network design is weak. 2 cut cables and
bye-bye West Coast.

JG
>
> --
> E-mail fudged to thwart spammers.
> Transpose the c's and a's in my e-mail address to reply.

>> Isaiah Beard wrote:
>> So you're relying on a canned response from Sprint e-care, which has
>> been known for years as being unable to "resolve" itself out of a wet
>> paper bag, and treating that canned response as gospel? What's wrong
>> with this picture?
>
<[email protected]> wrote in message
news:[email protected]...
>
> The second "cable cut", reportedly in Buckeye Arizona, has not been
> explained.
> Who or what caused it? Bin Laden? UFOs? Chip Monks?
>
> If in fact "cut cables" are the reason, the fact remains that Sprint's
> Wireless and Long Distance network design is weak. 2 cut cables and
> bye-bye West Coast.
>
> JG
>>
>> --
>> E-mail fudged to thwart spammers.
>> Transpose the c's and a's in my e-mail address to reply.
>
A cut cable may contain 100 fiber strands. Cut enough of those and bu-bye
service.
Cut TWO -using my 100 fibers/cable-all the way through and kiss major pop
centers
goodbye until a repair is made.

--
Andrew D. Sisson
LG VX8100
VZW<BAM<FRONTIER CELLULAR<ROCHESTER TEL. MOBILE
SID 154 EV-DO PRL 50463
SINCE APRIL 1993

Sounds like he is also a disgruntled ex-Sprint Customer.

<[email protected]> wrote in message
news:[email protected]...
>
> Isaiah Beard wrote:
>> [email protected] wrote:
>> > Mij Adyaw wrote:
>> >> Where did you obtain your information that lead you to this
>> >> conclusion?
>> >> State only facts and hard evidence please.
>> >
>> > The statement from E-care mentions nothing about "cables", only
>> > "constant updates which might have slowed down our servers. We assure
>> > you"
>>
>>
>> So you're relying on a canned response from Sprint e-care, which has
>> been known for years as being unable to "resolve" itself out of a wet
>> paper bag, and treating that canned response as gospel? What's wrong
>> with this picture?
>
> The second "cable cut", reportedly in Buckeye Arizona, has not been
> explained.
> Who or what caused it? Bin Laden? UFOs? Chip Monks?
>
> If in fact "cut cables" are the reason, the fact remains that Sprint's
> Wireless and Long Distance network design is weak. 2 cut cables and
> bye-bye West Coast.
>
> JG
>>
>> --
>> E-mail fudged to thwart spammers.
>> Transpose the c's and a's in my e-mail address to reply.
>

Mij Adyaw wrote:
> Sounds like he is also a disgruntled ex-Sprint Customer.

Actually a brand new VM'er. Not relying on them for critical things
like some people whose livelyhood depends on reliable service. A decent
"star" network would handle multiple cut cables. This "dual-self
healing-ring" is a disaster waiting to happen.
And not truly "self healing".

Still waiting for an explanation on the "Buckeye Cut", JG

>
> <[email protected]> wrote in message
> news:[email protected]...
> >
> > Isaiah Beard wrote:
> >> [email protected] wrote:
> >> > Mij Adyaw wrote:
> >> >> Where did you obtain your information that lead you to this
> >> >> conclusion?
> >> >> State only facts and hard evidence please.
> >> >
> >> > The statement from E-care mentions nothing about "cables", only
> >> > "constant updates which might have slowed down our servers. We assure
> >> > you"
> >>
> >>
> >> So you're relying on a canned response from Sprint e-care, which has
> >> been known for years as being unable to "resolve" itself out of a wet
> >> paper bag, and treating that canned response as gospel? What's wrong
> >> with this picture?
> >
> > The second "cable cut", reportedly in Buckeye Arizona, has not been
> > explained.
> > Who or what caused it? Bin Laden? UFOs? Chip Monks?
> >
> > If in fact "cut cables" are the reason, the fact remains that Sprint's
> > Wireless and Long Distance network design is weak. 2 cut cables and
> > bye-bye West Coast.
> >
> > JG
> >>
> >> --
> >> E-mail fudged to thwart spammers.
> >> Transpose the c's and a's in my e-mail address to reply.
> >

What is a "VM'er?

<[email protected]> wrote in message
news:[email protected]...
>
> Mij Adyaw wrote:
>> Sounds like he is also a disgruntled ex-Sprint Customer.
>
> Actually a brand new VM'er. Not relying on them for critical things
> like some people whose livelyhood depends on reliable service. A decent
> "star" network would handle multiple cut cables. This "dual-self
> healing-ring" is a disaster waiting to happen.
> And not truly "self healing".
>
> Still waiting for an explanation on the "Buckeye Cut", JG
>
>>
>> <[email protected]> wrote in message
>> news:[email protected]...
>> >
>> > Isaiah Beard wrote:
>> >> [email protected] wrote:
>> >> > Mij Adyaw wrote:
>> >> >> Where did you obtain your information that lead you to this
>> >> >> conclusion?
>> >> >> State only facts and hard evidence please.
>> >> >
>> >> > The statement from E-care mentions nothing about "cables", only
>> >> > "constant updates which might have slowed down our servers. We
>> >> > assure
>> >> > you"
>> >>
>> >>
>> >> So you're relying on a canned response from Sprint e-care, which has
>> >> been known for years as being unable to "resolve" itself out of a wet
>> >> paper bag, and treating that canned response as gospel? What's wrong
>> >> with this picture?
>> >
>> > The second "cable cut", reportedly in Buckeye Arizona, has not been
>> > explained.
>> > Who or what caused it? Bin Laden? UFOs? Chip Monks?
>> >
>> > If in fact "cut cables" are the reason, the fact remains that Sprint's
>> > Wireless and Long Distance network design is weak. 2 cut cables and
>> > bye-bye West Coast.
>> >
>> > JG
>> >>
>> >> --
>> >> E-mail fudged to thwart spammers.
>> >> Transpose the c's and a's in my e-mail address to reply.
>> >
>

[email protected] wrote:

> No mention of the cause of the "cable cut" in Buckeye, AZ.
> Ergo, they tried a public excuse of "cable cuts". Blaming outside
> "evil-doers"
> and mud slides for the major WEST COAST service crash.
> Baboo software at your service.

That WAS what happened, Trollboi.

--
Steve Sobol, Professional Geek 888-480-4638 PGP: 0xE3AE35ED
Company website: http://JustThe.net/
Personal blog, resume, portfolio: http://SteveSobol.com/
E: [email protected] Snail: 22674 Motnocab Road, Apple Valley, CA 92307

[email protected] wrote:

>>From the stock charts on Monday and Tuesday, looks like a combo of
> Nortel
> and Alcatel equipment failure.

Ah, the "I hate Lucent/Nortel" moron shows his true colors again.

Is there anyone left that doesn't realize you have an obvious agenda? Don't
you have anything better to do with your time?

--
Steve Sobol, Professional Geek 888-480-4638 PGP: 0xE3AE35ED
Company website: http://JustThe.net/
Personal blog, resume, portfolio: http://SteveSobol.com/
E: [email protected] Snail: 22674 Motnocab Road, Apple Valley, CA 92307