VLapikov469304 (Community Member) asked a question.
Hey Guys,
I am trying to reach https://analysiscenter.veracode.com/ url, but it ends up with timeout error. Reaching this url is part of SSO login we have setup in our company.
"nslookup analysiscenter.veracode.com" returns 192.157.28.40.
But "ping 192.157.28.40" consistently returns "Request timeout".
This is traceroute:
traceroute to 192.157.28.40 (192.157.28.40), 64 hops max, 52 byte packets
1 mpfr-8n7rvt2 (192.168.1.1) 1.410 ms 1.007 ms 0.985 ms
2 rwga-8mn7wz1 (192.168.100.1) 1.637 ms 1.468 ms 1.198 ms
3 mm-1-224-122-178.mgts.dynamic.pppoe.byfly.by (178.122.224.1) 3.817 ms 4.157 ms 3.787 ms
4 93.84.80.57 (93.84.80.57) 5.616 ms 4.796 ms 6.063 ms
5 core1.net.belpak.by (93.85.80.45) 5.606 ms
core2.net.belpak.by (93.85.80.57) 5.379 ms 6.444 ms
6 ie1.net.belpak.by (93.85.80.50) 5.309 ms 7.446 ms 7.411 ms
7 asbr8.net.belpak.by (93.85.80.94) 4.016 ms 3.495 ms 3.864 ms
8 war-b2-link.telia.net (62.115.47.110) 18.083 ms 14.505 ms 11.937 ms
9 hbg-bb3-link.telia.net (213.155.135.16) 30.993 ms
hbg-bb4-link.telia.net (213.155.134.118) 32.792 ms
hbg-bb3-link.telia.net (213.155.135.16) 29.293 ms
10 hbg-b1-link.telia.net (213.155.135.85) 29.225 ms
hbg-b1-link.telia.net (62.115.141.113) 32.936 ms
hbg-b1-link.telia.net (213.155.135.81) 30.950 ms
11 be3044.rcr11.b015763-1.ham01.atlas.cogentco.com (130.117.14.37) 30.075 ms 27.035 ms 30.332 ms
12 be3220.ccr41.ham01.atlas.cogentco.com (154.54.39.37) 34.556 ms
be3221.ccr42.ham01.atlas.cogentco.com (154.54.57.109) 27.384 ms
be3220.ccr41.ham01.atlas.cogentco.com (154.54.39.37) 32.862 ms
13 be2815.ccr41.ams03.atlas.cogentco.com (154.54.38.205) 34.962 ms 37.093 ms 37.968 ms
14 be12488.ccr42.lon13.atlas.cogentco.com (130.117.51.41) 43.471 ms 46.046 ms 45.917 ms
15 be2099.ccr31.bos01.atlas.cogentco.com (154.54.82.34) 112.537 ms 112.597 ms 112.018 ms
16 te0-3-1-0.rcr51.b002133-1.bos01.atlas.cogentco.com (154.54.46.134) 117.081 ms 120.079 ms
te0-2-1-5.rcr51.b002133-1.bos01.atlas.cogentco.com (66.28.4.254) 117.109 ms
17 38.140.156.171 (38.140.156.171) 120.261 ms
38.140.156.170 (38.140.156.170) 116.244 ms 112.727 ms
18 1.1.1.2 (1.1.1.2) 115.264 ms 112.454 ms 115.414 ms
19 *
.png){kind=logo}
Hi @VLapikov469304 (Community Member) - thank you for reporting this to us! According to https://status.veracode.com/ it seems that the platform is operating normally at this point while some performance issues have occurred on March 21 and March 22. Can you let us know if you're still having issues accessing Analysis Center?