Anyone else experiencing problem with the site?
#1
Anyone else experiencing problem with the site?
Trace route to "64.65.56.121" over a maximum of 30 hops:
1. hop: 192.168.254.1: 1 ms
2. hop: 192.168.254.254: 3 ms
3. hop: 162.39.13.233: 12 ms
4. hop: 162.39.13.225: 10 ms
5. hop: 151.213.33.5 (h5.33.213.151.ip.alltel.net): 12 ms
6. hop: timed out.
7. hop: 151.213.254.68 (h68.254.213.151.ip.alltel.net): 10 ms
8. hop: 151.213.254.65 (h65.254.213.151.ip.alltel.net): 16 ms
9. hop: 151.213.254.64 (h64.254.213.151.ip.alltel.net): 10 ms
10. hop: 12.122.10.198 (tbr1.attga.ip.att.net): 59 ms
11. hop: timed out.
12. hop: 12.122.5.141 (cr2.ormfl.ip.att.net): 58 ms
13. hop: 12.122.21.78 (tbr2.ormfl.ip.att.net): 55 ms
14. hop: timed out.
15. hop: 12.118.175.66: 51 ms
16. hop: 151.213.254.65 (h65.254.213.151.ip.alltel.net): 17 ms
17. hop: timed out.
18. hop: 66.132.255.42: 54 ms
19. hop: timed out.
20. hop: 64.65.56.121 (ns.camaroz28.com): 53 ms
1. hop: 192.168.254.1: 1 ms
2. hop: 192.168.254.254: 3 ms
3. hop: 162.39.13.233: 12 ms
4. hop: 162.39.13.225: 10 ms
5. hop: 151.213.33.5 (h5.33.213.151.ip.alltel.net): 12 ms
6. hop: timed out.
7. hop: 151.213.254.68 (h68.254.213.151.ip.alltel.net): 10 ms
8. hop: 151.213.254.65 (h65.254.213.151.ip.alltel.net): 16 ms
9. hop: 151.213.254.64 (h64.254.213.151.ip.alltel.net): 10 ms
10. hop: 12.122.10.198 (tbr1.attga.ip.att.net): 59 ms
11. hop: timed out.
12. hop: 12.122.5.141 (cr2.ormfl.ip.att.net): 58 ms
13. hop: 12.122.21.78 (tbr2.ormfl.ip.att.net): 55 ms
14. hop: timed out.
15. hop: 12.118.175.66: 51 ms
16. hop: 151.213.254.65 (h65.254.213.151.ip.alltel.net): 17 ms
17. hop: timed out.
18. hop: 66.132.255.42: 54 ms
19. hop: timed out.
20. hop: 64.65.56.121 (ns.camaroz28.com): 53 ms
AT&T appears to by having some issues. Just trying to see if it's a localized where our peering point is, or more general.
Last edited by jpolz; 02-29-2008 at 11:18 AM.
#9
I'm no techie, so I don't know. No second machine is available to me either. All I can tell you is that it is a new problem and only on this site. I'm not saying that it isn't on my end, just letting you know what I know.
#13
We have hundreds of people on the site at the exact same time you are, and no one else is reporting any kinds of errors like what you are. I did some testing and I am not encountering what you are explaining either.
We'll keep an eye out for similar problems that others may experience, but other than that, I wish we knew what else to tell you. Everything seems fine otherwise.
We'll keep an eye out for similar problems that others may experience, but other than that, I wish we knew what else to tell you. Everything seems fine otherwise.
#15
We have hundreds of people on the site at the exact same time you are, and no one else is reporting any kinds of errors like what you are. I did some testing and I am not encountering what you are explaining either.
We'll keep an eye out for similar problems that others may experience, but other than that, I wish we knew what else to tell you. Everything seems fine otherwise.
We'll keep an eye out for similar problems that others may experience, but other than that, I wish we knew what else to tell you. Everything seems fine otherwise.