-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you're with Experian contact please ping me off-list it would be
really great.
regards,
/virendra
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFH8pSppbZvC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
reported on outages mailing list.
John van Oppen wrote:
> Major media outlets have been reporting massive power outages in
> Florida. Given the scope it seems interesting nobody has commented.
>
>>From the news reports it sounds like everyone in Mi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
fyi -/
- Original Message
Subject: [Outages] FW: Level(3) Service Affecting Maintenance -
GCR#180226 -Scheduled
Date: Tue, 12 Feb 2008 13:22:18 -0700
From: Raman Sud <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://www.computerworld.com/action/article.do?command=viewArticleBasic&articleId=9036482&intsrc=hm_list
regards,
/virendra
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
FYI -/
- Original Message
Subject: [Outages] FW: SMC INITIAL OUTAGE NOTIFICATION: MULTIPLE
fBroadwing Markets
Date: Wed, 19 Sep 2007 12:50:58 -0500
From: W. Kevin Hunt <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
City/State: Mo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
Mills, Charles wrote:
> We're seeing packet loss and significant latency with Sprint in
> Pittsburgh. Anyone else know anything. Sprint has confirmed an issue
> but I'm not sure how widespread it is.
- ---
I'm not seeing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brad,
Brandon Galbraith wrote:
> Is anyone else seeing significant congestion between ATT and Broadwing in
> Dallas/Fort Worth?
>
> -brandon
- --
Not that I can tell. Not sure what others are seeing.
Level 3 (Dallas, TX) Pi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[pardon me if this off topic - thought I might be able to help from an
operational standpoint]
This is related to running a colo/pop/peering/etc., in a city (primarily
in southern california) where you have no personnel. Issues like remote
hands, shi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Coulson wrote:
>
> About 20mins ago my connection to Cogent in Cleveland just went totally
> nuts. I can't even get to www.cogentco.com over their circuit:
>
>Packets
> Pings
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
william(at)elan.net wrote:
>
> On Sun, 18 Mar 2007, virendra rode // wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> william(at)elan.net wrote:
>>>
>>>
>>> On Sun, 18 M
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
william(at)elan.net wrote:
>
>
> On Sun, 18 Mar 2007, Rubens Kuhl Jr. wrote:
>
>> What open-source or low-budget tools are operators using for SLA
>> monitoring when the reports (current state and historical) should be
>> available to customers ?
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ray Burkholder wrote:
>> What open-source or low-budget tools are operators using for
>> SLA monitoring when the reports (current state and
>> historical) should be available to customers ?
>>
>
> Here is one way to do it on the cheap.
>
> I have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
virendra rode // wrote:
> Frank Bulk wrote:
>>> http://www.phillyburbs.com/pb-dyn/articlePrint.cfm?id=1310151
>>>
>>> Is this a normal thing for Level 3 to do, cut off small, responsive
>>> providers?
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frank Bulk wrote:
> http://www.phillyburbs.com/pb-dyn/articlePrint.cfm?id=1310151
>
> Is this a normal thing for Level 3 to do, cut off small, responsive
> providers?
>
> Frank
-
Just curious, should "small responsive provid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rob Baxter wrote:
> I mean exactly what I said. I grabbed that info from
> http://status.cogentco.com/ after seeing a few complaints from users.
>
> Rob
-
Sorry I meant your subject?
regards,
/virendra
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rob Baxter wrote:
>
> ** Cogent Network Status Report Last Updated Wed Feb 21 16:35:00 2007 **
>
> Cogent Network Status/DNS Server Status Description:
> We currently have a possible fiber cut between Stamford, CT and New York
> City, NY. This may c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sean Donelan wrote:
>
> On Sat, 17 Feb 2007, Petri Helenius wrote:
>>> After all these years, I'm still surprised a consortium of ISP's
>>> haven't figured out a way to do something a-la Packet Fence for their
>>> clients where - whenever an infected
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Douglas Otis wrote:
>
>
> On Feb 7, 2007, at 6:27 AM, Jeff Kell wrote:
>
>>
>> Alexander Harrowell wrote:
>>>
>>> It was clear from the highly reliable index I call the "Nanogdex"
>>> that nothing was seriously amiss.
>>
>> Yes, but it got so much
Any insight will be appreciated.
regards,
/virendra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris L. Morrow wrote:
>
> On Tue, 7 Nov 2006, Wallace Keith wrote:
>
>> Working with 2 other carriers on a similar issue, response I rec'd was
>> congestion due to automated political dialers. Not sure if I believe
>> that or not...
>
> you'd thin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We ran into similar attacks (couple days back) coming from non-spoofed
address range (being initiated from valid prefixes).
In working (w/ a co-worker of mine) on a network attack situation (trace
process) for a 30,000 user location (serving 60 other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
William Allen Simpson wrote:
>
> Jeremy Chadwick wrote:
>> On Thu, Oct 19, 2006 at 02:40:01PM -0400, J. Oquendo wrote:
>>> Anyone else seeing issues with GBLX, DC area?
>>
>> Yes. There appears to be a fibre cut of some kind either around
>> Virgini
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scott Weeks wrote:
> - Original Message Follows -
> From: virendra rode // <[EMAIL PROTECTED]>
>> Scott Weeks wrote:
>>> - Original Message Follows -----
>>> From: virendra rode // <[EMAIL PROTECT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Scott Weeks wrote:
> - Original Message Follows -
> From: virendra rode // <[EMAIL PROTECTED]>
>
>> Ideally (if I have better luck) I would like to get
>> providers to direct outage notices to this list. All that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris L. Morrow wrote:
> On Fri, 29 Sep 2006, Randy Bush wrote:
>
>>> as reported on outages mailing list.
>> you will find the specifics as you catch up on your nanog reading
>>
>
> Maybe the point was that it's not being effective already?
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
as reported on outages mailing list.
regards,
/virendra
- Original Message
Subject: Re: [Outages] [SPAM] - Global Crossing Issues - Bayesian
Filter detected spam
Date: Fri, 29 Sep 2006 13:40:38 -0400
From: Steve Postma <[EMAI
nge what's supposed to be "on-topic" for the mailing list anyway
> 4) start a new mailing list in an attempt to take real content away from
> nanog
> 5) ???
> 6) profit!
>
> Don't fall for it, people.
>
>
> -- Niels.
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris L. Morrow wrote:
> On Thu, 28 Sep 2006, virendra rode // wrote:
>> Gadi Evron, Randy Vaughn and myself have initiated an "outages" mailing
>> list.
>>
>> The primary goal of this mailing list ("outages&
rtment of homeland
security) perceived needs. We look forward to your feedback and suggestions.
Outages mailing is now accepting members.
http://isotf.org/mailman/listinfo/outages
regards,
Gadi Evron
Randy Vaughn
Virendra Rode
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (GNU
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Kent wrote:
> virendra rode wrote:
>>> This is yet another reason one shouldn't rely on pings & traceroutes to
>>> perform reachability analysis.
>
> So, you're in the "traceroute is not importan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark Kent wrote:
> A smaller North American network provider, with a modest North
> American backbone, numbers their internal routers on public IP space
> that they do not announce to the world.
>
> One of the largest North American network providers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alain Hebert wrote:
>
>Hi,
>
>All our experiences consulting our clients about how to get their AS
> and Subnets have been pretty easy and fast.
>
>First get enought IP from 2 Peer to justify at least a /21;
>
>Now that you have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard A Steenbergen wrote:
> On Fri, Aug 18, 2006 at 09:09:59PM +, Christopher L. Morrow wrote:
>> On Fri, 18 Aug 2006, Geoffrey Pan wrote:
>>
>>> This space has been assigned to the same location, facility for years.
>>>
>> same location/facil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
in-line:
Jordan Medlen wrote:
> I'm sure most people on this list have heard of or use snort. There is an
> add-on package called snortsam. This package allows automation of blocking
> traffic deemed malicious via a null route statement or ACL statem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://www.networkworld.com/news/2006/072106-free-management.html?twht=072406thisweek2
regards,
/virendra
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEyS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://www.npr.org/templates/story/story.php?storyId=5538363
enjoy :-)
regards,
/virendra
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFExk/jpbZvCIJx1bcRAuC
37 matches
Mail list logo
