Receive up to $504 promo credit ($180 w/Welcome Unlimited, $360 w/ 5G Start, or $504 w/5G Do More, 5G Play More, 5G Get More or One Unlimited for iPhone plan (Welcome Unlimited and One Unlimited for iPhone plans can't be mixed w/other Unlimited plans; all lines on the account req'd on respective plans)) when you add a new smartphone line with your own 4G/5G smartphone on an eligible postpaid plan between 2/10/23 and 4/5/23. Promo credit applied over 36 months; promo credits end if eligibility requirements are no longer met.
$699.99 (128 GB only) device payment purchase or full retail purchase w/ new smartphone line on One Unlimited for iPhone (all lines on account req'd on plan), 5G Start, 5G Do More, 5G Play More or 5G Get More plan req'd. Less $699.99 promo credit applied over 36 mos.; promo credit ends if eligibility req’s are no longer met; 0% APR.
akc.org I've used it for years and suddenly, I keep getting time-out connection errors. Viewers-- Firefox/Safari and IExplorer
using Macs wireless and ethernet + ethernet windows machine as well. What caused this and how to we make it work again? Others are able to access the site without problem. Has Verizon somehow blocked the site?
Verizon is not blocking that website. Are you still having trouble reaching it? If you are, try running a Traceroute and post up the results you get for us. Here's a trace on a Verizon Business DSL connection I manage that can reach the site.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\>tracert akc.org
Tracing route to akc.org [22.214.171.124]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.254.254
2 31 ms 30 ms 30 ms 10.41.21.1
3 29 ms 29 ms 31 ms P2-1.BFLONY-LCR-01.verizon-gni.net [126.96.36.199]
4 42 ms 43 ms 42 ms P11-0-0.BFLONY-LCR-02.verizon-gni.net [188.8.131.52]
5 43 ms 43 ms 44 ms so-3-0-0-0.NY325-BB-RTR2.verizon-gni.net [184.108.40.206]
6 41 ms 42 ms 42 ms so-2-3-0-0.NY325-BB-RTR1.verizon-gni.net [220.127.116.11]
7 42 ms 41 ms 43 ms 0.xe-3-0-0.BR3.NYC4.ALTER.NET [18.104.22.168]
8 41 ms 43 ms 43 ms sl-crs2-nyc-0-1-2-0.sprintlink.net [22.214.171.124]
9 52 ms 52 ms 51 ms sl-crs2-pen-0-4-5-0.sprintlink.net [126.96.36.199]
10 52 ms 51 ms 50 ms sl-crs2-rly-0-2-5-0.sprintlink.net [188.8.131.52]
11 51 ms 51 ms 51 ms sl-crs2-dc-0-4-0-2.sprintlink.net [184.108.40.206]
12 51 ms 51 ms 50 ms sl-st30-ash-0-2-0-0.sprintlink.net [220.127.116.11]
13 50 ms 50 ms 50 ms sl-timewarner-374159-0.sprintlink.net [18.104.22.168]
14 60 ms 60 ms 61 ms rdu1-ar4-xe-2-0-0-0.us.twtelecom.net [22.214.171.124]
15 63 ms 62 ms 62 ms akc.org [126.96.36.199]
C:\Documents and Settings\>
so when you get this.... what's next?
traceroute to www.akc.org (188.8.131.52), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 62.718 ms 0.669 ms 0.665 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
The purpose of the Tracert is to see where the connection is timing out. This doesn't always work because some nodes are programmed not to respond to ping requests as a way of preventing denial of service attacks
There are really two possibilities.
The IP address of DSL modem is leased, and while it is relatively static, it can and usually does change. You may now have a IP address that has an unsavory past, and consequently is blocked. Often unused IP addresses are used to hack, and/or attack web sites, and as a result end up blocked at the site. Unfortunately at some point most such addresses eventually get assigned to users, but the block will remain in place until someone does something to remove it. I've had that happen frequently after I moved and/or changed ISP's..
That is usually done by contacting the site administrator, and pointing out that the IP address is now valid, and is assigned to Verizon Communications.
The other possibility (and if you really are seeing more than 30 'hops', there is either a DNS problem, or router problem somewhere upstream, and it is doubtful there is much you can do except wait for it to be fixed. If it is has happened, odds are you are not the only one to notice!
Thanks for that Mattheww.... I know that others are able to access the site with no problems, and when I tested
a proxy ip server service, it worked properly. So, given that info, do I ask Verizon to replace my antique Westell or
change out routers....the westell is connected to a Netgear router as when we got our DSL service, wireless was
fairly new <g>