Re: mysql.org down?
On 26/01/2012, at 10:51 AM, Ingo Flaschberger wrote: Hi, from my location / austria, mysql.org seems to be down: http://www.downforeveryoneorjustme.com/mysql.org It's not just you! http://mysql.org looks down from here. smime.p7s Description: S/MIME cryptographic signature
Re: Overall Netflix bandwidth usage numbers on a network?
On 12/12/2011, at 4:18 PM, Joel jaeggli wrote: also probably your relationships to akamai and level3 Probably want to add Limelight to that list as well (do Netflix even use Akamai these days?) -Shaun smime.p7s Description: S/MIME cryptographic signature
Re: Abuse@ contacts
From: Gavin Pearce gavin.pea...@3seven9.com How many of you (honestly) actively manage and respond to abuse@ contact details listed in WHOIS? Or have had any luck with abuse@ contacts in the past? Who's good and who isn't? We monitor our abuse queues, but when the email is just a stock standard incident (eg: spam or phishing) we don't actually reply to the emails unless more information is required. As mentioned previously, a lot of the traffic in abuse queues is automated and you might have anywhere up to 100 emails for a single incident. In these cases, we merge the messages into one ticket, handle the case and close it off. The nature of our business (hosting) means that we do get a decent amount of abuse traffic - ranging from compromised out of date CMSs used to send spam or host phishing sites right through to fraudulent accounts again used to send spam. Rather than hire additional staff to respond to the each abuse email individually we prefer to invest in systems to stop the abuse in the first place. For example, all outbound email from our shared hosting network is checked for spam/viruses and any unusual traffic (such as a spike from a customer who typically only sends a few messages a day) is flagged. -Shaun
Re: Google Over IPV6
On 27/03/09 11:59 PM, Daniel Verlouw dan...@bit.nl wrote: yes. We participate in the Google IPv6 trial program so our recursors get records for www.google.com and so far it's been great, no issues whatsoever. Same. We've been participating since January and haven't had any problems: # traceroute6 www.google.com traceroute to www.google.com (2001:4860:c003::68), 30 hops max, 40 byte packets 1 vl2-gw.cbr1.as24557.net.au (2405:5000:1:2::1) 0.492 ms 0.484 ms 0.501 ms 2 gi0-1-4.bdr1.syd1.as24557.net.au (2405:5000:1:4::21) 5.009 ms 5.048 ms 5.212 ms 3 AS15169.ipv6.sydney.pipenetworks.com (2001:7fa:b::14) 4.552 ms 4.538 ms 4.522 ms 4 2001:4860::29 (2001:4860::29) 157.930 ms 157.914 ms 149.638 ms 5 2001:4860:c003::68 (2001:4860:c003::68) 157.709 ms 156.651 ms 149.585 ms -Shaun
Re: Cable Colors
On 17/06/08 9:00 AM, Randy Bush [EMAIL PROTECTED] wrote: the colors make no difference as long as you are consistent. labeling, consistent port use (oob port == power port == switch port ==) are what will bail you out at three in the morning. randy And there you have it. Finding the group of backbone cables (as an example) out of a bundle of cables is much easier when they're a different colour. What colours we use depends on what area of the network we're in. For example (for the DC): - Access layer (ie: to servers): Blue - Management network (KVM, power, etc): Green - Private network (internal only): Black - Inter-rack links (don't touch): yellow - Network uplinks (really don't touch): red -Shaun
