Tracing route to
www.matchbook.com [204.188.169.6]
over a maximum of 30 hops:
4 52 ms 54 ms 61 ms gi1-1.ccr01.bwi01.atlas.cogentco.com [38.112.18.
17]
5 58 ms 51 ms 64 ms te9-3.mpd01.dca01.atlas.cogentco.com [154.54.25.
86]
6 54 ms 54 ms 72 ms te8-3.mpd01.iad01.atlas.cogentco.com [154.54.24.
98]
7 57 ms 49 ms 54 ms te1-2.ccr02.iad01.atlas.cogentco.com [154.54.26.
93]
8 56 ms 63 ms 67 ms sl-bb21-prl-9-2.sprintlink.net [144.232.8.205]
9 62 ms 57 ms 59 ms sl-crs1-dc-0-13-0-0.sprintlink.net [144.232.25.1
2]
10 67 ms 68 ms 77 ms sl-crs1-ffx-0-15-0-0.sprintlink.net [144.232.24.
53]
11 82 ms 79 ms 82 ms sl-crs2-orl-0-15-2-0.sprintlink.net [144.232.24.
58]
12 79 ms 79 ms 84 ms sl-gw14-orl-15-0-0.sprintlink.net [144.232.0.108
]
13 * * * Request timed out.
14 * 173 ms * cwag-rin5-s2.candw.ag [208.158.6.139]
15 * 162 ms * 209.59.68.102
16 * * * Request timed out.
17 156 ms 160 ms * 204.188.169.2
18 * 157 ms 165 ms 204.188.169.6
Looks like the problem is getting to Matchbook's ISP just fine, ie sprintlink carries it to orlando and then the connection to the carrier to Antigua is hosed. That carrier is likely Cable and Wireless (c and w in line 14 above). In the internet business some say that C and W really stands for Clueless and Witless. This doesn't look like Matchbook's fault.
Matchbook connectivity?
