-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Elijah,
Elijah Savage wrote: > Fergie, > > I am aware of this but this is what's so confusing as we run our own > nameservers in our own facilities for a very large number of customers > so we do not rely on any of Comcast services at all. I do not even have > Comcast for a provider at home :) I also know of other AS's that were > affected that do not rely on any of comcast services. - ------------------------- Maybe somehow BGP attribute such as MED may have caused hiccup somewhere. Thinking out loud. regards, /virendra > > Plus I would never bring a home broadband issue as such to NANOG I know > a lot better that that :) > > > ---------------------------------------------------------------------- > Elijah Savage | AOL IM:layer3rules > Senior Network Engineer | When it has to be switched or routed. > http://www.digitalrage.org | The Information Technology News Center > ----- http://www.digitalrage.org/?page_id=46 for pgp public key-------- > > > On Sep 28, 2006, at 12:25 AM, Fergie wrote: > >> >> Elijah: >> >> http://www.macworld.com/news/2006/09/27/comcast/index.php >> >> - ferg >> >> >> -- Elijah Savage <[EMAIL PROTECTED]> wrote: >> >> http://www.ipdemocracy.com/archives/2006/09/27/#001985 >> >> I have not seen this show up on the list yet neither have I seen any >> public statements released. >> >> It is being passed on as a comcast problem but I know of others with >> connectivity as well as myself hat has no connectivity at all with >> comcast. >> >> [snip] >> >> -- >> "Fergie", a.k.a. Paul Ferguson >> Engineering Architecture for the Internet >> fergdawg(at)netzero.net >> ferg's tech blog: http://fergdawg.blogspot.com/ >> > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFG05ipbZvCIJx1bcRAr+VAKDoumKaxGhVS+uRkA0g5NhSBUr7lwCgwtI7 iA2AylhZO46v0jd22aaMPM0= =wtH4 -----END PGP SIGNATURE-----