st is reporting that Tata is having problems in Montreal
affecting 'many routers'...maybe this is related?
Chris
--
Chris Stone
AxisInternet, Inc.
www.axint.net
ion of Nagios and Observium
--
Chris Stone
AxisInternet, Inc.
www.axint.net
> On Apr 18, 2012 5:43 PM, "Deric Kwok" wrote:
>> Any websites can provide about network issue
http://www.outages.org/index.php/Dashboard
--
Chris Stone
AxisInternet, Inc.
www.axint.net
st all of our
server like:
Mar 5 07:49:13 server kernel: Shorewall:logflags:DROP:IN=eth2 OUT=
MAC=00:07:e9:0f:39:f1:00:03:31:a5:74:00:08:00 SRC=178.18.16.101
DST=x.x.x.x LEN=56 TOS=0x00 PREC=0x00 TTL=204 ID=49665 DF PROTO=TCP
SPT=0 DPT=0 WINDOW=37009 RES=0x14 URG ACK RST SYN FIN URGP=37422
Brian,
> wanting to know what other people were seeing with traceroutes and "show ip
> bgp". The networks in question at the following 4 /24's
>
> 68.68.176.0/24
> 68.68.177.0/24
> 68.68.178.0/24
> 68.68.179.0/24
Here's what I'm seeing on our L3 connection here in Denver, CO::
route1:~$ show ip
>> Can someone please point me in the direction of an rwhoisd solution to
>> be run on a CentOS Linux platform? ARIN is now punting rwhois queries
>> to us and frankly i've been unable to find an easy to install/use
>> solution to answer these queries. I've seen the rwhoisd at
>> projects.arin.net
tage?
> Been that way for a while this morning.
I get that also with http://www.amazon.com, but do get the site using
http://www.amazon.com/tag/unavailable and then all links on the page though
click to the error - although the images on the page are all fine.
Chris
- --
Chris Stone,
y, and had no problems
their either.
The only real issue was the couple of times the peering between L3 and Cogent
was stopped - which was really, IMNTBHO, the fault of both parties. I was
able to route around this when it occurred, so was not a significant issue at
the time.
- --
Chris St
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 30 May 2008 9:10:50 am Mike Tancsa wrote:
> At 10:58 AM 5/30/2008, Frank Bulk wrote:
> >Required:
> >- temperature sensor
> >- 110 VAC power monitoring (on/off, not necessarily current)
> >- Ethernet interface (at least SNMP, Web GUI and
>
>
his is a deluge.)
>>
>> All I know is "amazonaws.com" is "Amazon Web Services", not sure if
>> these particular systems should be sending email at all, the hostnames
>> look like:
>>
Send to [EMAIL PROTECTED] - amazonaws.com has no MX:
[EMA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Bjørn Mork wrote:
> Not only that. They are actually redirecting to a 404 not found page
> based on User-Agent. Compare these two requests:
>
> The site is designed specifically NOT to work except if you've got an
> approved browser. I guess they
11 matches
Mail list logo