That said, there are no doubt folks on the other side of those down links with calls in to three or four NOCs, a couple of trouble tickets being escalated, and people driving out to non-nondescript buildings near railroad tracks and in industrial areas carrying weird looking devices which can measure the intensity of laser light and do time-domain reflectometry (TDR) measurements. We can only wait and see what they discover. If we were playing the Ops edition of the game Clue I'd guess "Colonel Mustard with a Backhoe in New Jersey" :-)
Available online along with all the other South Park episodes on their official website: http://www.southparkstudios.com/full-episodes/s12e06-over-lo...
Sometimes it's amazing how much one silly little issue can bork. Even more so when it usually winds up being completely innocent, and not actually a bug.
I was the senior UNIX systems manager at a business unit HQ of a Fortune 5 company then, and still remember all the people stopping me in the halls that day to ask what was wrong with the Internet.
Another place to check for good information is http://www.outages.org/
There have been a few incidents as of the past few days. Last night, there was a nationwide outage from Frontier that has since been resolved.
The day prior there was a triple failure in the Midwest as reported http://vielmetti.typepad.com/vacuum/2012/10/windstream-outag... that affected lots of services in a large area.
I could see a core router at UW being a major measure of the internet, but not some small consulting company in a small town..
Fortunately to date the affected services are all non essential, mainly entertainment/trivial stuff like blogs, instagram, dropbox etc etc, but when we start to see things like water supply and electrical power management systems, hospital records, aviation system etc affected the consequences could be severe.
If the very best IT minds at AWS and GAE can't keep their systems running, what hope have government departments got? Anyone that's ever been to a DMV, or USPS knows just how good the US Government’s IT departments are.
Now how to explain to your spouse that the TV is broken because ns-18.sbcglobal.net is not working.
I have no idea what those numbers should look like?
I remember years ago when a fast-spreading virus shot all those numbers up.
By far the best tool available.
Most of those zeroes have been zero for a long time. The ITR isn’t
well-maintained and I wouldn’t use the data as a primary source.
I am having some routing issues with my Frontier DSL service
(residential) and after speaking with technical support at Frontier, they
confirmed they are having a nationwide routing issue with no ETA
currently on the fix.
Packet loss is intermittent regardless of destination.
Of course, they couldn't possibly be that dumb as to make a massive DDoS in retaliation. snicker
The USA has been fighting a very dirty fight against Iranian science programs, including using the stuxnet worms. Iran was also recently fingered for attacking Saudi networks.
EDIT: The West also crashed Iran's currency, where it lost 40% value in one week.
FYI: most serious attacks come out of Chinese networks and are managed by Eastern Europeans where the attack software is written.
Other issue met this week,
Yahoo msger report TLS error sometime when login at 0900-1000 in the morning.
Doesn't look port 443 specific.
And China isn't some rogue state despite perceptions within the US. They aren't going to deliberately attack core routers out of spite.
Umm, weren't the Chinese fingered (by Google and the USGov) in a giant attempted incursion only a few months back?
The Ontario router seems to be dropping packets:
$ ping gw02.wlfdle.phub.net.cable.rogers.com
PING gw02.wlfdle.phub.net.cable.rogers.com (18.104.22.168) 56(84) bytes of data.
From <snip> icmp_seq=1 Packet filtered
From <snip> icmp_seq=2 Packet filtered
From <snip> icmp_seq=3 Packet filtered
--- gw02.wlfdle.phub.net.cable.rogers.com ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 10206ms
$ traceroute <snip>
traceroute to <snip> (<snip>), 30 hops max, 60 byte packets
1 <snip> (192.168.1.1) 1.489 ms 2.038 ms 2.669 ms
2 * * *
3 22.214.171.124 (126.96.36.199) 17.599 ms 17.584 ms 17.339 ms
4 so-4-0-0.gw02.wlfdle.phub.net.cable.rogers.com (188.8.131.52) 31.992 ms 31.972 ms 31.819 ms
5 184.108.40.206 (220.127.116.11) 33.198 ms 34.687 ms 34.596 ms
6 * * *
7 pos-3-15-0-0-cr01.ashburn.va.ibone.comcast.net (18.104.22.168) 35.557 ms 28.952 ms 28.818 ms
8 22.214.171.124 (126.96.36.199) 33.029 ms 42.176 ms 41.924 ms
9 he-0-4-0-0-cr01.350ecermak.il.ibone.comcast.net (188.8.131.52) 49.244 ms 45.218 ms 44.940 ms
10 pos-1-2-0-0-pe01.350ecermak.il.ibone.comcast.net (184.108.40.206) 37.146 ms 40.169 ms 40.372 ms
Akami reporting attacks 50% above normal: http://www.akamai.com/dv1
8,000 attacks reported for 10/24
17,000+ attacks reported so far today
HUGE scans yesterday. Something is going on.
Do you really think all traffic in/out of MD goes through a single (2 if you count DC) router?
Put it another way, imagine you're monitoring traffic for SF by monitoring average speeds on the Northbound 280. One pile-up that blocks the road completely brings the average speed at that point to 0mph. Doesn't mean that every road in SF is blocked. Traffic will bail off the 280 and use other routes to get to their destinations (albeit slower and causing average speeds on the surround[ing] road network to drop too), but the one thing you are measuring (average speed on the Northbound 280) has dropped to 0.
Perhaps I'm just lucky? Or there is issue with how this is reporting or there is more than one router that everyone else on my ISP uses.
There isn't just one router where all data flows in/out from.
I wonder how reliable this is.
Now I see the problem of private subnets is fixed at the L3 dns servers that were borked 2-days ago (220.127.116.11 18.104.22.168). The one the popped up today is still borked (22.214.171.124).
Pinging 126.96.36.199 with 32 bytes of data:
Reply from 188.8.131.52: bytes=32 time=14ms TTL=56
Reply from 184.108.40.206: bytes=32 time=15ms TTL=56
Reply from 220.127.116.11: bytes=32 time=14ms TTL=56