<kib> http://pastebin.ca/231411 <-- that one is clearly an isp routing problem
<kib> he only gets one hope ouside his router before it dies
<AnMaster> yeah
<AnMaster> but works fine for other hosts
<AnMaster> odd
<kib> well it's a routing issue
<AnMaster> yep, just that he is one of our opers
<kib> parts of the internet have no routes for that isp
<AnMaster> so getting him on would be realy nice
<kib> his ISP can't figure out how to get to abovenet to get to staminus
<AnMaster> ok
<AnMaster> damn he disconnected, have to tell him again
<AnMaster> later on
<AnMaster> other person turned out to be using same ISP
<AnMaster> ok that is solved then :)
<kib> but it's his ISP dropping the route...he never gets outside his own ISP..so that means his ISP has no clue how to get to the IP..doesnt even know which direction to start with
<AnMaster> will tell him to call support
<kib> so if this seems to be a common thread on one ISP then you know where to complain
<kib> it could be more then one ISP but they might use a common backbone
<AnMaster> yeah
<kib> I am sure these guys also can't reach certian ther blocks of IPs
<AnMaster> run into these problems before?
<kib> but the list they can't reach might not be very big
<kib> but enough to block staminus
<AnMaster> why would a ISP block some hosts like that?
<AnMaster> makes no sense to me
<kib> they probably didn't block them
<kib> they probably lost a link to the one and only peer with a router going that way
<kib> or their routing tables are screwed up
<kib> my guess is that it's a problem they are working to fix even now
<kib> traceroute to 72.20.46.115 (72.20.46.115), 64 hops max, 40 byte packets
<kib> 1 adsl-70-229-108-206.dsl.sgnwmi.sbcglobal.net (70.229.108.206) 0.357 ms 0.272 ms 1.115 ms
<kib> 2 adsl-70-229-109-254.dsl.sgnwmi.sbcglobal.net (70.229.109.254) 55.813 ms 62.715 ms 52.191 ms
<kib> 3 dist1-vlan60.sgnwmi.ameritech.net (67.38.60.242) 45.321 ms 111.241 ms 54.184 ms
<kib> 4 bb2-fa2-0-0.sgnwmi.ameritech.net (67.38.60.116) 46.354 ms 44.060 ms 70.624 ms
<kib> 5 bb2-p4-1.sfldmi.sbcglobal.net (151.164.240.205) 43.669 ms 130.691 ms 145.866 ms
<kib> 6 core2-p7-0.crchil.sbcglobal.net (151.164.43.195) 102.213 ms 72.858 ms 51.697 ms
<kib> 7 bb1-p11-0.emhril.ameritech.net (151.164.240.194) 54.400 ms 108.338 ms 128.107 ms
<kib> 8 bb2-p0-0.emhril.sbcglobal.net (151.164.43.253) 125.559 ms 53.878 ms 56.155 ms
<kib> 9 ex2-p5-0.eqchil.sbcglobal.net (151.164.42.139) 119.250 ms 91.312 ms 116.738 ms
<kib> 10 asn6461-abovenet.eqchil.sbcglobal.net (151.164.251.46) 57.416 ms 53.837 ms 60.074 ms
<kib> 11 so-1-0-0.cr1.ord2.us.above.net (64.125.30.146) 54.206 ms 132.251 ms 83.700 ms
<kib> 12 so-4-0-0.mpr3.sjc2.us.above.net (64.125.30.213) 101.699 ms 158.322 ms 110.311 ms
<kib> 13 so-0-0-0.mpr2.sjc2.us.above.net (64.125.27.246) 109.748 ms 114.473 ms 139.391 ms
<kib> 14 so-4-3-0.mpr1.lax9.us.above.net (64.125.27.6) 148.309 ms 126.757 ms 145.885 ms
<kib> see how mine stays on my ISP then hands off to abovenet
<kib> which is what staminius uses
<kib> so what probably happens is that those ISPs can no longer reach abovenet for one reason or another
<kib> or their routing tables are messed up so the routers just dont know how to reach it
<kib> routing tables are like road signs...a packet arrives at a router the router looks and sees where the packet wants to go and checks the rouing tables to see which paths will lead there..then picks the one with the leaast load
<kib> if none are found the packet dies in that router
<kib> so that first pastebin indicates that the packet gets lost one hope outside his own local router
<kib> since hie local router knows what to do...everything not on the local lan goes up to the ISP
<kib> but then the ISP doesn't know what to do with it