The Internet's broken

[Wade Chamberlain]

I'm in!  Thanks Scott!

[PINKY]

Scott it's back up in NVA now on cox.
Pinky

[Hector Rodriguez]

I'm in, and fast.
Thanks Scott,

[Eric Nelson]

I was unable to access from home since sometime last weekend, I think, and it didn't work from home this a.m. before leaving for work. 
From work today there is no problem.

[aspenbubba]

I'm back on tho I lost electricity sometime last night and it finally came back on around 8:50 AM . Thanks Scott

[Scott Brooke]

Ok, so the last couple of days have been an unfortunate mix of bad timing and misdiagnosis.  Around the middle of Monday we started having some ISP issues but after troubleshooting we believed it was limited in scope and my testing to CACC wasn't showing any problems.  What I didn't know was at that time I was one of the few, or rather ATT through my iPhone was one of the few, that could successfully reach the forum.

Some emails from some members yesterday and further testing showed that the ISP seems to have assigned our IP addresses to another location in the network.  For those of you in the know, our subnet was propagating up to two different peering routers from our location and the other "wrong" location.  Anyone ISP that was closer (BGP) to our peering router could still get to the forum.  Anyone closer to the other peering router was going into DC somewhere and basically falling into the bit bucket.

I finally got someone at the ISP on the line last night that was able to fix the problem.  That happened around 7:30pm.

At about 7:35pm we lost power.  Storms had been gone for hours but I guess some tree just couldn't hold on any longer.  Batteries lasted about an hour but power didn't come back until this morning.  When I was starting things up this morning I had a moment of concern with some issues with the server, but all seems to be well now.

So, the ISP thing sucked and was a simple oversight on their part.  It happens.  The power outage is a bummer though.  We'll be getting a generator soon and shouldn't have to worry about that problem.

After reading the other posts about Cumberland it looks like this couldn't have happened at a better time!   

If anyone's still having issues please let me know.  Everything should be ok at this point so if there's a problem, I'm not aware of it.

[Dan Deitz]

I'm in Scott!

Dan

[Scott Brooke]

The f'in clock is off an hour.  Probably fix that tonight.  Just can't win.

[Bob Lennon]

Since Al Gore "invented" the internet, let's ask him to fix the clock!

[Don Flanigin]

Thanks Scott,

You really do not know how much you appreciate something until it is is gone. 

Glad we are back up and Scott, thanks again for the time and effort that you put into this site to keep it running.

Don

[Gary Hughes]

Thanks for your efforts, Scott.  Much appreciated.  Regarding a generator, do we need to discuss how that would be financed?

[Scott Brooke]

Thanks for your efforts, Scott.  Much appreciated.  Regarding a generator, do we need to discuss how that would be financed?

Nope.  That's a personal expense that will benefit much more than the club.  Thanks for mentioning it though!

Speaking of...I've just been informed that we've lost power again.  The clock is ticking.

And no, the generator's not installed yet.   

[Joe Widmayer]

Ok, so the last couple of days have been an unfortunate mix of bad timing and misdiagnosis.  Around the middle of Monday we started having some ISP issues but after troubleshooting we believed it was limited in scope and my testing to CACC wasn't showing any problems.  What I didn't know was at that time I was one of the few, or rather ATT through my iPhone was one of the few, that could successfully reach the forum.

Some emails from some members yesterday and further testing showed that the ISP seems to have assigned our IP addresses to another location in the network.  For those of you in the know, our subnet was propagating up to two different peering routers from our location and the other "wrong" location.  Anyone ISP that was closer (BGP) to our peering router could still get to the forum.  Anyone closer to the other peering router was going into DC somewhere and basically falling into the bit bucket.

I finally got someone at the ISP on the line last night that was able to fix the problem.  That happened around 7:30pm.

At about 7:35pm we lost power.  Storms had been gone for hours but I guess some tree just couldn't hold on any longer.  Batteries lasted about an hour but power didn't come back until this morning.  When I was starting things up this morning I had a moment of concern with some issues with the server, but all seems to be well now.

So, the ISP thing sucked and was a simple oversight on their part.  It happens.  The power outage is a bummer though.  We'll be getting a generator soon and shouldn't have to worry about that problem.

After reading the other posts about Cumberland it looks like this couldn't have happened at a better time!  

If anyone's still having issues please let me know.  Everything should be ok at this point so if there's a problem, I'm not aware of it.

 

Does this explanation come with subtitles?

[Ben Lambiotte]

I think the title of the thread is the layman's version . . .

[Joe Widmayer]

"our subnet was propagating up to two different peering routers from our location and the other "wrong" location.  Anyone ISP that was closer (BGP) to our peering router could still get to the forum.  Anyone closer to the other peering router was going into DC somewhere and basically falling into the bit bucket."


My computer skill deficiencies exposed for all to see.......... 

I only meant to unclude the above portion in the quote.

The next time I'm asked to explain some screwup at work I'll just type in Scott's text.