Troubles reaching hosts through propagation.net

Can anyone with a host on 64/8 try reaching termforsale.net or
creativesound.ca? We're having troubles reaching either of those from
various hosts on that subnet. Just looking for some more details,
since some hosts on 64/8 can reach it, while others cannot.

We've been trying to get this solved since last Monday, and have just
been getting the runaround from them. If anyone's got a contact
there, or can pass this off to them, I'd greatly appreciate it.

Spake Damian Gerow on 31/10/2002, 10:06:39 -0500:

Can anyone with a host on 64/8 try reaching termforsale.net or
creativesound.ca? We're having troubles reaching either of those from
various hosts on that subnet. Just looking for some more details,
since some hosts on 64/8 can reach it, while others cannot.

A couple of people have pointed out that these sites are multi-homed.
To be a little more specific, our traces are traversing Qwest before
propagation.net. So it's not a filter in Verio.

Here's the more applicable part of a traceroute:

15 peer.plalca01gr00.bb.telus.com (154.11.3.14) 84.508 ms 85.916 ms 85.301 ms
16 svl-core-03.inet.qwest.net (205.171.205.29) 86.780 ms 87.949 ms 87.105 ms
17 svl-core-01.inet.qwest.net (205.171.14.121) 91.981 ms 109.635 ms 85.859 ms
18 iah-core-01.inet.qwest.net (205.171.8.130) 129.400 ms 128.335 ms 128.568 ms
19 iah-core-02.inet.qwest.net (205.171.31.2) 126.871 ms 132.070 ms 133.559 ms
20 dal-core-01.inet.qwest.net (205.171.8.125) 135.519 ms 135.442 ms 131.014 ms
21 dal-edge-07.inet.qwest.net (205.171.25.54) 134.300 ms 136.345 ms 135.117 ms
22 ci-dfw-OC12.cust.qwest.net (65.118.50.2) 135.595 ms 132.445 ms 136.589 ms
23 gige1.fire0.propagation.net (66.34.255.2) 136.786 ms 138.485 ms 133.917 ms

After which it just times out.

Spake Damian Gerow on 31/10/2002, 10:06:39 -0500:

We've been trying to get this solved since last Monday, and have just
been getting the runaround from them. If anyone's got a contact
there, or can pass this off to them, I'd greatly appreciate it.

Thanks to the list, I was able to get a hold of someone who cleared
out the filter. Thanks to all for your traceroutes and help in
tracking down this problem.