[Outages-discussion] [outages] Long latency in receiving email on this list/Other observations about today's Google Incident

[virendra rode]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bob -

Moving to 'outages-discussion'.

Puck.nether.net that host outages list has been competing cycles with
cisco-nsp (busy list) off the same server.

When non-member messages (moderated) are posted to the list, at times
getting to these messages are delayed and they appear to be time delayed
when in fact its human delay. Then again, we've had instances when
member postings have been delayed which I agree defeats the purpose of
getting outages update to the list in a timely manner.

Either way, we will look into this further and see what can be done.

Thanks for the feedback.


regards,
/virendra


Bob Roswell wrote:
> I am looking through the emails from the outages list from today's
> Google incident and many of the posts have original time stamps.  I
> received my copies of mailing lists posts over an hour after they were
> sent.  For example, I posted a message today at 12:11PM EDT, and I
> received my copy from the list at 1:20PM.  We were well into our
> troubleshooting with Verizon and Level 3 when I saw the first post on
> this list.  Is there anything we can do to speed the delivery of the
> emails from this list?   We have had a better incident response had we
> known sooner that this was a global issue.  And I was still receiving
> hour old trouble reports long after the problem was resolved.
> 
>  
> 
> I also called two out of three of our upstream providers (Level 3 and
> Verizon)  Neither had status messages on their web sites, nor for their
> dispatch folks.  We had all of the relevant information (account #,
> Circuit ID etc) but they insisted on going through a long ticket process
> (Have you verified power, what are your IPS, what IPs are you trying to
> reach, what are your contact hours, what type of equipment do you have
> etc) instead of just taking the call.  At Verizon, (50 Mbit circuit) I
> was on hold for about 15 minutes before I was even able to place a
> trouble ticket.
> 
>  
> 
> I also saw speculation on the list that it was a Level 3 problem, and in
> fact we could not reach Google with any reliability on our DS3 with
> Level3 (On level3 IP Space)  But our Comcast line uses Level 3 for
> transport and we had no issues reaching Google services from Comcast.
> 
>  
> 
> Bob Roswell
> 
> System Source
> 
> broswell at syssrc.com
> 
> (410) 771-5544 ext 4336
> 
>  
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> outages mailing list
> outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages







-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFKEKP8pbZvCIJx1bcRAjPoAKDTvM2WYeXDlD5zzCs2yVbjVw+tFwCgn2NX
BL24SS/ADaHGRxq2sJ2pIuE=
=Xwtt
-----END PGP SIGNATURE-----