Announcement

Collapse
No announcement yet.

Possible Connectivity Issues to phoronix-test-suite.com

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Possible Connectivity Issues to phoronix-test-suite.com

    Hello,

    Is there a connectivity problem to phoronix-test-suite.com ? When I do the ping, it takes 10-30 sec for it to work. Then, ping works, but with a packet loss.
    64 bytes from rome.phoronix.com (192.211.48.82): icmp_seq=848 ttl=28 time=71.8 ms
    64 bytes from rome.phoronix.com (192.211.48.82): icmp_seq=849 ttl=28 time=75.0 ms
    64 bytes from rome.phoronix.com (192.211.48.82): icmp_seq=850 ttl=28 time=68.0 ms
    64 bytes from rome.phoronix.com (192.211.48.82): icmp_seq=851 ttl=28 time=71.5 ms
    64 bytes from rome.phoronix.com (192.211.48.82): icmp_seq=977 ttl=28 time=70.6 ms
    ^C
    --- phoronix-test-suite.com ping statistics ---
    978 packets transmitted, 66 received, 93% packet loss, time 1185672ms
    rtt min/avg/max/mdev = 65.649/71.936/93.271/4.025 ms


    My script that builds a test suite relies on the connectivity. It fails due to the issue.

    Thanks

  • #2
    There are no known issues. Do you have a traceroute or anything to narrow down?
    Michael Larabel
    http://www.michaellarabel.com/

    Comment


    • #3
      traceroute phoronix-test-suite.com
      traceroute to phoronix-test-suite.com (192.211.48.82), 30 hops max, 60 byte packets
      1 Fios_Quantum_Gateway.fios-router.home (192.168.1.1) 0.401 ms 0.511 ms 0.619 ms
      2 * * *
      3 B3334.NWRKNJ-LCR-22.verizon-gni.net (130.81.26.34) 6.544 ms 6.375 ms B3334.NWRKNJ-LCR-21.verizon-gni.net (130.81.26.32) 6.633 ms
      4 * * *
      5 0.ae2.BR1.EWR6.ALTER.NET (140.222.237.225) 17.510 ms 0.ae1.BR1.EWR6.ALTER.NET (140.222.237.223) 15.993 ms 15.895 ms
      6 ae-12.edge5.Newark1.Level3.net (4.68.73.65) 14.746 ms 7.820 ms 7.553 ms
      7 ae-32-0.ear1.Dallas1.Level3.net (4.69.210.141) 43.186 ms 43.087 ms 43.110 ms
      8 HIVELOCITY.ear1.Dallas1.Level3.net (4.71.220.242) 43.398 ms HIVELOCITY.ear1.Dallas1.Level3.net (4.14.16.38) 48.924 ms 45.431 ms
      9 * * *
      10 * * *
      11 * * *
      12 * * *
      13 * * *
      14 * * *
      15 * * *
      16 * * *
      17 * * *
      18 * * *
      19 * * *
      20 * * *
      21 * * *
      22 * * *
      23 * * *
      24 * * *
      25 * * *
      26 * * *
      27 * * *
      28 * * *
      29 * * *
      30 * * *

      Comment


      • #4
        Is the IP you are having the issue with the one you are connecting from this forum? (Ending in .5) Is it still happening right now?
        Michael Larabel
        http://www.michaellarabel.com/

        Comment


        • #5
          I have a a couple of computers connected to the router. The traceroute output I sent previously was fro the machine that I am trying to run the tests on.
          And this is the output from the machine I am connecting from. The issue is happening right now.
          tracert phoronix-test.suite.com

          Tracing route to phoronix-test.suite.com [198.58.118.167]
          over a maximum of 30 hops:

          1 20 ms 20 ms 14 ms 10.220.16.1
          2 * * * Request timed out.
          3 * * * Request timed out.
          4 * * * Request timed out.
          5 * * * Request timed out.
          6 * * * Request timed out.
          7 17 ms 16 ms 20 ms 100.65.14.177
          8 18 ms 18 ms 17 ms 52.93.29.29
          9 36 ms 22 ms 15 ms 100.100.8.60
          10 50 ms 49 ms 50 ms 100.91.177.44
          11 49 ms 44 ms 53 ms 100.91.160.30
          12 52 ms 54 ms 52 ms 100.91.160.41
          13 45 ms 45 ms 50 ms 100.91.198.40
          14 53 ms 46 ms 53 ms 100.91.198.27
          15 52 ms 46 ms * 54.239.43.175
          16 48 ms 49 ms 49 ms 54.239.46.11
          17 50 ms 46 ms 45 ms 100.91.143.15
          18 52 ms 47 ms 56 ms 176.32.125.234
          19 53 ms 49 ms 46 ms 176.32.124.186
          20 49 ms 53 ms 54 ms ipv4.de-cix.dfw.us.as63949.linode.com [206.53.202.7]
          21 47 ms 53 ms 47 ms 45.79.12.7
          22 55 ms 52 ms 53 ms li647-167.members.linode.com [198.58.118.167]

          Trace complete.

          Comment


          • #6
            is it working better for you now?
            Michael Larabel
            http://www.michaellarabel.com/

            Comment


            • #7
              Unfortunately, I am still having the problem.

              Comment


              • #8
                Originally posted by ybp2000 View Post
                Unfortunately, I am still having the problem.
                Hmmm, are you able to try a different connection to see if it's an ISP issue perhaps? Just double checked server side no issues and also the folks in the data center checked over my configurations and verified everything should be okay. So not too sure what else would be going on besides something awkward with your ISP.
                Michael Larabel
                http://www.michaellarabel.com/

                Comment


                • #9
                  I tried another machine.


                  tracert phoronix-test-suite.com

                  Tracing route to phoronix-test-suite.com [192.211.48.82]
                  over a maximum of 30 hops:

                  1 <1 ms <1 ms <1 ms Fios_Quantum_Gateway.fios-router.home [192.168.1.1]
                  2 7 ms 4 ms 8 ms rome.phoronix.com [192.211.48.82]

                  Trace complete.

                  C:\WINDOWS\system32>ping phoronix-test-suite.com

                  Pinging phoronix-test-suite.com [192.211.48.82] with 32 bytes of data:
                  Request timed out.
                  Request timed out.
                  Request timed out.
                  Request timed out.

                  Ping statistics for 192.211.48.82:
                  Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
                  =============================================
                  C:\WINDOWS\system32>ping rome.phoronix.com

                  Pinging rome.phoronix.com [192.211.48.82] with 32 bytes of data:
                  Request timed out.
                  Request timed out.
                  Request timed out.
                  Reply from 192.211.48.82: bytes=32 time=43ms TTL=53

                  Ping statistics for 192.211.48.82:
                  Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
                  Approximate round trip times in milli-seconds:
                  Minimum = 43ms, Maximum = 43ms, Average = 43ms

                  Comment


                  • #10
                    Is it working if you ping openbenchmarking.org or phoronix.com instead?
                    Michael Larabel
                    http://www.michaellarabel.com/

                    Comment

                    Working...
                    X