Microcuts in server's net traffic

Hello,

We've got a big problem since about 10 days: there are microcuts in our server's network traffic.
The server is "up" for about 10mins, then becomes "down" for about 1min, then becomes "up" again.

While the server is "down", it is not halted, but cannot we reached and cannot reach anything (even servers in the same datacenter).
It does not answer pings, TCP connections, or anything.

Here is a tracert from my PC (in France) while it's "up" :
------------------------------------------------------------------------
  1     2 ms     1 ms     1 ms  192.168.1.1
  2    68 ms    67 ms    67 ms  192.168.254.254
  3    67 ms    67 ms    67 ms  vlq-6k-2-a11.routers.proxad.net [212.27.37.190]
 
  4    66 ms    67 ms    64 ms  th1-6k-2-v804.intf.routers.proxad.net [212.27.50
.37]
  5    68 ms    67 ms    67 ms  cbv-6k-2-v802.intf.routers.proxad.net [212.27.50
.34]
  6    67 ms    67 ms    67 ms  prs-b1-geth6-0.telia.net [213.248.71.141]
  7    67 ms    68 ms    70 ms  prs-bb1-pos6-1-2.telia.net [213.248.65.77]
  8    76 ms    75 ms    75 ms  ldn-bb1-pos7-2-0.telia.net [213.248.64.10]
  9   147 ms   148 ms   148 ms  nyk-bb1-pos0-2-0.telia.net [213.248.65.90]
 10   146 ms   145 ms   148 ms  nyk-bb2-pos0-0-0.telia.net [213.248.80.134]
 11   145 ms   145 ms   143 ms  nyk-i1-pos3-0.telia.net [213.248.82.22]
 12   146 ms   143 ms   143 ms  so-0-1-0.gar4.NewYork1.Level3.net [209.244.160.1
61]
 13   144 ms   146 ms   145 ms  ge-2-1-0.bbr1.NewYork1.Level3.net [64.159.4.145]
 
 14   213 ms   210 ms   211 ms  4.68.128.149
 15   212 ms   210 ms   211 ms  so-10-0.hsa1.SanDiego1.Level3.net [4.68.113.38]
 
 16   211 ms   212 ms   210 ms  Aplus-gw.Level3.net [209.245.56.130]
 17   218 ms   213 ms   212 ms  core01.san-diego.abac.net [216.55.131.2]
 18     *        *        *     Délai d'attente de la demande dépassé.
 19     *        *      212 ms  216-55-160-14.dedicated.abac.net [216.55.160.14]
 
  1     1 ms     1 ms     1 ms  192.168.1.1
  2    68 ms    67 ms    67 ms  192.168.254.254
  3    66 ms    67 ms    68 ms  vlq-6k-2-a11.routers.proxad.net [212.27.37.190]
 
  4    67 ms    66 ms    67 ms  th1-6k-2-v804.intf.routers.proxad.net [212.27.50
.37]
  5    67 ms    67 ms   116 ms  cbv-6k-2-v802.intf.routers.proxad.net [212.27.50
.34]
  6    65 ms    67 ms    67 ms  prs-b1-geth6-0.telia.net [213.248.71.141]
  7    68 ms    67 ms    66 ms  prs-bb1-pos6-1-2.telia.net [213.248.65.77]
  8    73 ms    73 ms    73 ms  ldn-bb1-pos7-2-0.telia.net [213.248.64.10]
  9   147 ms   145 ms   148 ms  nyk-bb1-pos0-2-0.telia.net [213.248.65.90]
 10   148 ms   146 ms   146 ms  nyk-bb2-pos0-0-0.telia.net [213.248.80.134]
 11   144 ms   145 ms   146 ms  nyk-i1-pos3-0.telia.net [213.248.82.22]
 12   142 ms   146 ms   150 ms  so-0-1-0.gar4.NewYork1.Level3.net [209.244.160.1
61]
 13   151 ms   143 ms   146 ms  ge-2-1-0.bbr1.NewYork1.Level3.net [64.159.4.145]
 
 14   251 ms   209 ms   210 ms  4.68.128.149
 15   211 ms   210 ms   209 ms  so-10-0.hsa1.SanDiego1.Level3.net [4.68.113.38]
 
 16   212 ms   213 ms   211 ms  Aplus-gw.Level3.net [209.245.56.130]
 17   215 ms   211 ms   211 ms  [HIDDEN].dedicated.abac.net [HIDDEN]
------------------------------------------------------------------------

And now a tracert while it's "down" :
------------------------------------------------------------------------
1     1 ms     1 ms     1 ms  192.168.1.1
  2    94 ms    70 ms    69 ms  192.168.254.254
  3    68 ms    67 ms     *     vlq-6k-2-a11.routers.proxad.net [212.27.37.190]
 
  4    66 ms    67 ms    70 ms  th1-6k-2-v804.intf.routers.proxad.net [212.27.50
.37]
  5    68 ms    67 ms    67 ms  cbv-6k-2-v802.intf.routers.proxad.net [212.27.50
.34]
  6    67 ms    67 ms    67 ms  prs-b1-geth6-0.telia.net [213.248.71.141]
  7    66 ms    67 ms    67 ms  prs-bb1-pos6-1-2.telia.net [213.248.65.77]
  8    75 ms    75 ms    75 ms  ldn-bb1-pos7-2-0.telia.net [213.248.64.10]
  9   146 ms   148 ms   146 ms  nyk-bb1-pos0-2-0.telia.net [213.248.65.90]
 10   147 ms   146 ms   147 ms  nyk-bb2-pos0-0-0.telia.net [213.248.80.134]
 11   146 ms   143 ms   143 ms  nyk-i1-pos3-0.telia.net [213.248.82.22]
 12   146 ms   145 ms   146 ms  so-0-1-0.gar4.NewYork1.Level3.net [209.244.160.1
61]
 13   145 ms   143 ms   143 ms  ge-2-1-0.bbr1.NewYork1.Level3.net [64.159.4.145]
 
 14   220 ms   209 ms   210 ms  so-0-1-0.mp1.SanDiego1.Level3.net [64.159.1.137]
 
 15   212 ms   211 ms   213 ms  so-8-0.hsa1.SanDiego1.Level3.net [4.68.112.130]
 
 16   211 ms   212 ms   210 ms  Aplus-gw.Level3.net [209.245.56.130]
 17   212 ms   210 ms   211 ms  core01.san-diego.abac.net [216.55.131.2]
 18     *        *        *     Délai d'attente de la demande dépassé. (still down)
 19     *        *        *     Délai d'attente de la demande dépassé. (still down)
 20     *        *        *     Délai d'attente de la demande dépassé. (still down)
 21     *      212 ms   211 ms  [HIDDEN].dedicated.abac.net [HIDDEN] (NOW up again)

------------------------------------------------------------------------

And here is a ping from our server to our hosting company's server while the server is "down" :
64 bytes from www.abac.net (216.55.128.150): icmp_seq=225 ttl=63 time=0.372 ms
64 bytes from www.abac.net (216.55.128.150): icmp_seq=226 ttl=63 time=0.355 ms
64 bytes from www.abac.net (216.55.128.150): icmp_seq=227 ttl=63 time=0.359 ms
64 bytes from www.abac.net (216.55.128.150): icmp_seq=228 ttl=63 time=0.347 ms
64 bytes from www.abac.net (216.55.128.150): icmp_seq=229 ttl=63 time=0.346 ms
64 bytes from www.abac.net (216.55.128.150): icmp_seq=230 ttl=63 time=0.360 ms
--- as you can see there is not traffic at all here, for 70 seconds ---
64 bytes from www.abac.net (216.55.128.150): icmp_seq=300 ttl=63 time=0.393 ms
64 bytes from www.abac.net (216.55.128.150): icmp_seq=301 ttl=63 time=0.337 ms
64 bytes from www.abac.net (216.55.128.150): icmp_seq=302 ttl=63 time=0.353 ms
64 bytes from www.abac.net (216.55.128.150): icmp_seq=303 ttl=63 time=0.349 ms
64 bytes from www.abac.net (216.55.128.150): icmp_seq=304 ttl=63 time=0.350 ms
64 bytes from www.abac.net (216.55.128.150): icmp_seq=305 ttl=63 time=0.338 ms


Can someone explain this ?
I need a solution because our business depends on this server !

Thanks in advance !
Ben
LVL 7
BenMorelAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

grbladesCommented:
Hi BenMorel,
Is it connected to a managed switch?
If it is then you could have a look at the logs on the switch to see if it sees the link going down.

You could try a different cable and even port on the switch.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
BenMorelAuthor Commented:
That was simply a bad network card. Thanks though.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.