API tools faq
paste
Propheticus

Ziggo zeer onstabiele ping

Propheticus
Oct 15th, 2013
211
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.36 KB | None | 0 0
raw download clone embed print report
  1. // Pingen naar websites (meerdere geprobeerd, zelfde resultaat) resulteert in ping spikes naar 200-450 ms. Dit is ook zeer goed merkbaar in online games...de lagpsikes hinderen het spelplezier aanzienlijk.
  2.  
  3. C:\Windows\system32>ping -t nu.nl
  4.  
  5. Pinging nu.nl [62.69.166.254] with 32 bytes of data:
  6. Reply from 62.69.166.254: bytes=32 time=26ms TTL=249
  7. Reply from 62.69.166.254: bytes=32 time=37ms TTL=249
  8. Reply from 62.69.166.254: bytes=32 time=14ms TTL=249
  9. Reply from 62.69.166.254: bytes=32 time=53ms TTL=249
  10. Reply from 62.69.166.254: bytes=32 time=15ms TTL=249
  11. Reply from 62.69.166.254: bytes=32 time=43ms TTL=249
  12. Reply from 62.69.166.254: bytes=32 time=65ms TTL=249
  13. Reply from 62.69.166.254: bytes=32 time=15ms TTL=249
  14. Reply from 62.69.166.254: bytes=32 time=14ms TTL=249
  15. Reply from 62.69.166.254: bytes=32 time=13ms TTL=249
  16. Reply from 62.69.166.254: bytes=32 time=21ms TTL=249
  17. Reply from 62.69.166.254: bytes=32 time=23ms TTL=249
  18. Reply from 62.69.166.254: bytes=32 time=141ms TTL=249
  19. Reply from 62.69.166.254: bytes=32 time=10ms TTL=249
  20. Reply from 62.69.166.254: bytes=32 time=15ms TTL=249
  21. Reply from 62.69.166.254: bytes=32 time=15ms TTL=249
  22. Reply from 62.69.166.254: bytes=32 time=12ms TTL=249
  23. Reply from 62.69.166.254: bytes=32 time=54ms TTL=249
  24. Reply from 62.69.166.254: bytes=32 time=12ms TTL=249
  25. Reply from 62.69.166.254: bytes=32 time=12ms TTL=249
  26. Reply from 62.69.166.254: bytes=32 time=25ms TTL=249
  27. Reply from 62.69.166.254: bytes=32 time=10ms TTL=249
  28. Reply from 62.69.166.254: bytes=32 time=13ms TTL=249
  29. Reply from 62.69.166.254: bytes=32 time=53ms TTL=249
  30. Reply from 62.69.166.254: bytes=32 time=28ms TTL=249
  31. Reply from 62.69.166.254: bytes=32 time=11ms TTL=249
  32. Reply from 62.69.166.254: bytes=32 time=96ms TTL=249
  33. Reply from 62.69.166.254: bytes=32 time=26ms TTL=249
  34. Reply from 62.69.166.254: bytes=32 time=15ms TTL=249
  35. Reply from 62.69.166.254: bytes=32 time=27ms TTL=249
  36. Reply from 62.69.166.254: bytes=32 time=14ms TTL=249
  37. Reply from 62.69.166.254: bytes=32 time=14ms TTL=249
  38. Reply from 62.69.166.254: bytes=32 time=27ms TTL=249
  39. Reply from 62.69.166.254: bytes=32 time=24ms TTL=249
  40. Reply from 62.69.166.254: bytes=32 time=32ms TTL=249
  41. Reply from 62.69.166.254: bytes=32 time=34ms TTL=249
  42. Reply from 62.69.166.254: bytes=32 time=13ms TTL=249
  43. Reply from 62.69.166.254: bytes=32 time=51ms TTL=249
  44. Reply from 62.69.166.254: bytes=32 time=15ms TTL=249
  45. Reply from 62.69.166.254: bytes=32 time=19ms TTL=249
  46. Reply from 62.69.166.254: bytes=32 time=26ms TTL=249
  47. Reply from 62.69.166.254: bytes=32 time=23ms TTL=249
  48. Reply from 62.69.166.254: bytes=32 time=13ms TTL=249
  49. Reply from 62.69.166.254: bytes=32 time=191ms TTL=249
  50. Reply from 62.69.166.254: bytes=32 time=25ms TTL=249
  51. Reply from 62.69.166.254: bytes=32 time=28ms TTL=249
  52. Reply from 62.69.166.254: bytes=32 time=24ms TTL=249
  53. Reply from 62.69.166.254: bytes=32 time=453ms TTL=249
  54. Reply from 62.69.166.254: bytes=32 time=22ms TTL=249
  55. Reply from 62.69.166.254: bytes=32 time=14ms TTL=249
  56. Reply from 62.69.166.254: bytes=32 time=23ms TTL=249
  57. Reply from 62.69.166.254: bytes=32 time=22ms TTL=249
  58. Reply from 62.69.166.254: bytes=32 time=22ms TTL=249
  59. Reply from 62.69.166.254: bytes=32 time=37ms TTL=249
  60. Reply from 62.69.166.254: bytes=32 time=26ms TTL=249
  61. Reply from 62.69.166.254: bytes=32 time=16ms TTL=249
  62. Reply from 62.69.166.254: bytes=32 time=37ms TTL=249
  63. Reply from 62.69.166.254: bytes=32 time=13ms TTL=249
  64. Reply from 62.69.166.254: bytes=32 time=10ms TTL=249
  65. Reply from 62.69.166.254: bytes=32 time=15ms TTL=249
  66. Reply from 62.69.166.254: bytes=32 time=23ms TTL=249
  67. Reply from 62.69.166.254: bytes=32 time=76ms TTL=249
  68. Reply from 62.69.166.254: bytes=32 time=171ms TTL=249
  69. Reply from 62.69.166.254: bytes=32 time=25ms TTL=249
  70. Reply from 62.69.166.254: bytes=32 time=12ms TTL=249
  71. Reply from 62.69.166.254: bytes=32 time=210ms TTL=249
  72. Reply from 62.69.166.254: bytes=32 time=12ms TTL=249
  73. Reply from 62.69.166.254: bytes=32 time=25ms TTL=249
  74.  
  75. Ping statistics for 62.69.166.254:
  76. Packets: Sent = 68, Received = 68, Lost = 0 (0% loss),
  77. Approximate round trip times in milli-seconds:
  78. Minimum = 10ms, Maximum = 453ms, Average = 40ms
  79. Control-C
  80. ^C
  81. C:\Windows\system32>
  82.  
  83.  
  84.  
  85. //Ping van pc naar Ubee modemrouter gaat zonder problemen of spikes:
  86.  
  87. C:\Windows\system32>ping -t 192.168.178.1
  88.  
  89. Pinging 192.168.178.1 with 32 bytes of data:
  90. Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
  91. Reply from 192.168.178.1: bytes=32 time<1ms TTL=64
  92. Reply from 192.168.178.1: bytes=32 time<1ms TTL=64
  93. Reply from 192.168.178.1: bytes=32 time<1ms TTL=64
  94. Reply from 192.168.178.1: bytes=32 time<1ms TTL=64
  95. Reply from 192.168.178.1: bytes=32 time<1ms TTL=64
  96. Reply from 192.168.178.1: bytes=32 time<1ms TTL=64
  97. Reply from 192.168.178.1: bytes=32 time<1ms TTL=64
  98. Reply from 192.168.178.1: bytes=32 time<1ms TTL=64
  99. Reply from 192.168.178.1: bytes=32 time<1ms TTL=64
  100. Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
  101. Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
  102. Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
  103. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  104. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  105. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  106. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  107. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  108. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  109. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  110. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  111. Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
  112. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  113. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  114. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  115. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  116. Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
  117. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  118. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  119. Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
  120. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  121. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  122. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  123. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  124. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  125. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  126. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  127. Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
  128. Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
  129. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  130. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  131. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  132. Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
  133. Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
  134. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  135. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  136. Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
  137. Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
  138. Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
  139. Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
  140. Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
  141. Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
  142.  
  143. Ping statistics for 192.168.178.1:
  144. Packets: Sent = 52, Received = 52, Lost = 0 (0% loss),
  145. Approximate round trip times in milli-seconds:
  146. Minimum = 0ms, Maximum = 3ms, Average = 1ms
  147. Control-C
  148. ^C
  149. C:\Windows\system32>
  150.  
  151.  
  152. //Omdat de ping van PC naar Modemrouter géén spikes vertoont en de pings voorbij het modemrouter wél vermoed ik dat het probleem of
  153. //a: bij het Ubee modemrouter of
  154. //b: in het netwerk ligt.
Advertisement
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!