[server-admins] possible routing flaw, user failing to reach crosswire.org

[Karl Kleinpaste]

The same person who reported blank web page actually can't get to
crosswire.org at all, even by IP address.  A couple random attempts to
figure things out ended up using traceroute, and her trace ends like
this...

15 te4-3.ccr02.iad01.atlas.cogentco.com (154.54.31.230) 355.591 ms te8-1.ccr02.iad01.atlas.cogentco.com (154.54.31.234) 359.199 ms te4-3.ccr02.iad01.atlas.cogentco.com (154.54.31.230) 356.994 ms
16 qwest.iad01.atlas.cogentco.com (154.54.10.26) 318.812 ms 322.373 ms 322.955 ms
17 * * *
18 phx-edge-10.inet.qwest.net (205.171.129.38) 506.336 ms 507.384 ms phx-edge-10.inet.qwest.net (205.171.129.42) 505.448 ms

...and then dies, no further success.  That last hop is a Phoenix node.

My similar trace runs fine, and ends thus:

14  ar5.phmaz.ip.att.net (12.123.142.153)  96.017 ms  87.886 ms  89.181 ms
15  12.124.244.190 (12.124.244.190)  97.470 ms  96.821 ms  101.083 ms
16  ip-140-128-242.phx.extremezone.com (64.140.128.242)  104.458 ms  103.788 ms  104.453 ms
17  crosswire.org (64.140.154.250)  102.972 ms  105.292 ms  105.700 ms

Is there a routing glitch?  Is there a way to raise a trouble ticket
about it?

She is coming from 196.215.26.11 (she's in .za), and can be reached at
cherylnell at gmail.com.