In adelphia.security-issues - article <FNSdneSSCfBHkTTfRVn-
***@adelphia.com>, on Thu, 09 Jun 2005 23:45:28 -0400, John E.
Malmberg says...
Post by John E. MalmbergPost by Murray Watson[followup corrected to adelphia.security-issues]
Yep, I should have checked.
Post by Murray WatsonIn adelphia.powerlink - article <lIidnRY93Yc7GTjfRVn-
Malmberg says...
The dsbl.org has had 69.164.71.189 listed since May 17th.
Still listed with dsbl.org, but senderbase is now showing no activity
and it's spamcop.net listing has also expired.
Post by Murray WatsonThe trace route to the affected server is showing that it is now going
through a Time Warner network to get to it. Is that an indication of
what Adelphia customers in this area are going to get when the sale is
closed?
I don't see Timewarner in the trace, everyting I see drops off at
69.160.186.138.
9 p3-00-00-00.p0.chi91.adelphiacom.net
(66.109.3.26) 108 ms 104 ms 105 ms
10 eqix.chcg.twtelecom.net
(206.223.119.36) 103 ms 104 ms 104 ms
11 core-01-so-4-1-0-0.chcg.twtelecom.net
(66.192.244.37) 105 ms 97.6 ms 99.6 ms
Could be just one of many peering relationships. I do not see it on all
my traceroutes, but they are on the one to that host.
-John
Very odd. Does all of your traffic go through Chicago? If so, part of
the answer to your speed issues probably lies in why you're routed
through Chicago?
You're both in NH right? Same regional hub? There are some wacky
routing problems as further indicated below.
This is what I get from here (Atlanta is my hub):
67.22.121.33 RTT: 16ms TTL:170 (67-22-121-33.atlaga.adelphia.net ok)
66.109.14.217 RTT: 16ms TTL:170 (unk-426d0ed9.adelphiacom.net probable bogus rDNS: No DNS)
66.109.1.205 RTT: 16ms TTL:170 (a1-00-00-00.c1.atl90.adelphiacom.net ok)
66.109.0.29 RTT: 29ms TTL:170 (as-02-00-00.c0.dca91.adelphiacom.net ok)
66.109.0.77 RTT: 33ms TTL:170 (a3-00-00-00.c1.nyc90.adelphiacom.net ok)
66.109.0.253 RTT: 36ms TTL:170 (p3-01-00-00.c0.nyc90.adelphiacom.net probable bogus rDNS: No DNS)
66.109.1.22 RTT: 43ms TTL:170 (p3-00-00-00.a0.alb75.adelphiacom.net ok)
* * * failed
24.48.204.206 RTT: 49ms TTL:170 (No rDNS)
69.160.186.138 RTT: 54ms TTL:170 (No rDNS)
10.29.120.1 RTT: 58ms TTL:170 (No rDNS)
* * * failed
* * * failed
* * * failed
This is with AS numbers as opus1(LA) sees it, note the "null" and AS7132 is SBC
5 ge1-40.fr1.lax.llnw.net (69.28.172.98) [AS7132] 33.201 ms
6 adelphia.ge2-16.fr1.lax.llnw.net (69.28.144.150) [AS7132] 30.271 ms
7 a1-02-00-00.c0.lax91.adelphiacom.net (66.109.3.129) [AS6983] 44.919 ms
8 p3-00-01-00.c1.lax91.adelphiacom.net (66.109.0.198) [AS6983] 32.224 ms
9 as-01-00-00.c0.dca91.adelphiacom.net (66.109.0.202) [AS6983] 89.838 ms
10 a3-00-00-00.c1.nyc90.adelphiacom.net (66.109.0.77) [AS6983] 95.697 ms
11 p3-01-00-00.c0.nyc90.adelphiacom.net (66.109.0.253) [AS6983] 96.674 ms
12 p3-00-00-00.a0.alb75.adelphiacom.net (66.109.1.22) [AS6983] 130.851 ms
13 * * *
14 24.48.204.206 (24.48.204.206) [(null)] 111.321 ms
15 69.160.186.138 (69.160.186.138) [AS7132] 119.133 ms
from XO (Atlanta)
1 ge5-3-0d4.RAR2.Atlanta-GA.us.xo.net (65.106.2.33) 4 msec 8 msec 4 msec
2 p1-0-0.RAR2.Washington-DC.us.xo.net (65.106.0.5) 16 msec 16 msec 16 msec
3 p1-0.IR1.Ashburn-VA.us.xo.net (65.106.3.138) 16 msec 16 msec 20 msec
4 ge-6-18.car3.Washington1.Level3.net (4.68.127.229) 20 msec 20 msec 20 msec
5 ae-1-55.bbr1.Washington1.Level3.net (4.68.121.129) 20 msec 20 msec 20 msec
6 as-1-0.bbr2.NewYork1.Level3.net (64.159.1.85) 24 msec 24 msec 24 msec
7 ae-20-56.car2.NewYork1.Level3.net (4.68.97.181) 20 msec
ae-20-54.car2.NewYork1.Level3.net (4.68.97.117) 24 msec
ae-10-51.car2.NewYork1.Level3.net (4.68.97.21) 24 msec
8 65.59.196.38 24 msec 20 msec 20 msec
9 a1-01-00-00.c0.nyc90.adelphiacom.net (66.109.1.13) 20 msec 20 msec 20 msec
10 p3-00-00-00.a0.alb75.adelphiacom.net (66.109.1.22) 32 msec 32 msec 32 msec
11 * * *