As seen from Cogent to XO.
http://i.imgur.com/aFyAw1p.png
On Tue, Mar 11, 2014 at 1:56 PM, Mikeal Clark mikeal.cl...@gmail.comwrote:
This problem seemed resolved for awhile and now its representing with about
7% packet loss.
Looks like someone adjusted the routing a bit at XO.
On Mon,
I saw the same effect after the Netflix peering started.
http://imgur.com/a/aVFAS
On Thu, Feb 27, 2014 at 10:22 PM, Jason Canady ja...@unlimitednet.uswrote:
I'm already seeing a huge improvement to Comcast after Netflix moved a lot
of traffic off of the ports.
On Feb 27, 2014, at 22:21,
Curious if anyone else thinks filtering out NTP packets above a certain
packet size is a good or terrible idea.
From my brief testing it seems 90 bytes for IPv4 and 110 bytes for IPv6 are
typical for a client to successfully synchronize to an NTP server.
If I query a server for it's list of
I also see major congestion from Cogent to VZ. Amongst other major
networks.
http://i.imgur.com/1z2ZGOr.png
On Tue, Feb 4, 2014 at 6:44 PM, Robert Glover robe...@garlic.com wrote:
Hello,
For the last several months, we have been tracking a congestion issue
between Cogent - Verizon
Cogent support uses the same response when inquiring about Comcast,
CenturyLink, Tata, ATT etc.
If the Tier 1s are really keeping each other congested, are they not
creating an environment where you have to buy from each of them to have a
chance at congestion free paths? Or peer around them.
Roughly between State College and Harrisburg.
On Fri, Nov 8, 2013 at 1:21 PM, Charles Mills w3y...@gmail.com wrote:
It's a big state. Which part? Pittsburgh, Philadelphia or some point in
between?
On Thu, Nov 7, 2013 at 9:41 PM, Edward Roels edwardro...@gmail.comwrote:
I'm looking
6 matches
Mail list logo
