Packet Loss Support

[GlitchKing]

Hello,

I'm trying to narrow down what my problem is, I'm assuming its' the ISP's fault. Basically, I have a huge amount of packet loss and I'm seeking help in why that is.

Here is some basic traceroute and ping test I performed:

C:\Windows\system32>tracert xbox.com

Tracing route to xbox.com [134.170.29.210]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router.asus.com [192.168.1.1]
  2    18 ms    18 ms    18 ms  66.11.241.1
  3    20 ms    18 ms    18 ms  static-host-66-18-36-245.epbinternet.com [66.18.
36.245]
  4     *        *        *     Request timed out.
  5    22 ms    21 ms    21 ms  atl-edge-24.inet.qwest.net [67.133.228.253]
  6    22 ms    21 ms    21 ms  atl-pcor-04.inet.qwest.net [67.14.14.170]
  7    36 ms    36 ms    35 ms  63.148.138.162
  8    34 ms    33 ms    34 ms  ae3-0.atb-96cbe-1a.ntwk.msn.net [207.46.33.212]

  9     *        *        *     Request timed out.
 10    43 ms    43 ms    36 ms  ae1-0.bn1-96c-2b.ntwk.msn.net [204.152.141.39]
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *     191.234.78.51  reports: Destination net unreachable.

Trace complete.

C:\Windows\system32>ping -n 15 xbox.com

Pinging xbox.com [134.170.29.210] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 191.234.78.51: Destination net unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 134.170.29.210:
    Packets: Sent = 15, Received = 1, Lost = 14 (93% loss),

Every server that connects through EPBInternet has these same results. When I do another website, such as google.com, I get different results.

C:\Windows\system32>tracert google.com

Tracing route to google.com [198.231.29.45]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router.asus.com [192.168.1.1]
  2    19 ms    18 ms    18 ms  66.11.241.1
  3    23 ms    23 ms    23 ms  ge-0-0-5.cr1.nsvltnit.iristransport.net [204.29.
13.41]
  4    24 ms    23 ms    25 ms  198.231.29.45

Trace complete.

C:\Windows\system32>ping -n 15 google.com

Pinging google.com [198.231.29.45] with 32 bytes of data:
Reply from 198.231.29.45: bytes=32 time=24ms TTL=61
Reply from 198.231.29.45: bytes=32 time=22ms TTL=61
Reply from 198.231.29.45: bytes=32 time=22ms TTL=61
Reply from 198.231.29.45: bytes=32 time=22ms TTL=61
Reply from 198.231.29.45: bytes=32 time=23ms TTL=61
Reply from 198.231.29.45: bytes=32 time=22ms TTL=61
Reply from 198.231.29.45: bytes=32 time=23ms TTL=61
Reply from 198.231.29.45: bytes=32 time=23ms TTL=61
Reply from 198.231.29.45: bytes=32 time=23ms TTL=61
Reply from 198.231.29.45: bytes=32 time=22ms TTL=61
Reply from 198.231.29.45: bytes=32 time=24ms TTL=61
Reply from 198.231.29.45: bytes=32 time=24ms TTL=61
Reply from 198.231.29.45: bytes=32 time=23ms TTL=61
Reply from 198.231.29.45: bytes=32 time=23ms TTL=61
Reply from 198.231.29.45: bytes=32 time=23ms TTL=61

Ping statistics for 198.231.29.45:
    Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 22ms, Maximum = 24ms, Average = 22ms

All websites routed through "epbinternet.com" have packet loss, when it uses "iristransport.net" there are no issues, mostly.

Contacted my ISP, they said they're not connected to EPBinternet. They have a monopoly here and no other ISP's can offer services.

What is the problem? :'(

Thank you!

 

[Zargon]

a device not answering a trace route is NOT the same thing as packet loss.

 

[GlitchKing]

a device not answering a trace route is NOT the same thing as packet loss.

And why would a device not answer a traceroute? Is this my fault or the ISP?

 

[RadiclDreamer]

And why would a device not answer a traceroute? Is this my fault or the ISP?

Some people still think that by not allowing ICMP they are doing something to secure their networks, thankfully this way of thinking is dying out.

 

[JackMDS]

It does not matter this or that, anything beyond step One on your Trace above is beyond your control.

 

[Zargon]

Some people still think that by not allowing ICMP they are doing something to secure their networks, thankfully this way of thinking is dying out.

agree

its still not uncommon, that big MPLS clouds don't have it turned on

And why would a device not answer a traceroute? Is this my fault or the ISP?

its a configuration on the carriers gear, and its likely intentional.

 

[Emulex]

Typically a router that drops icmp or a firewall that blocks them. Sometimes inline firewalls like the cell phone providers use which do deep packet inspection tend to skip over icmp.

 

[Mushkins]

I get the exact same results, regardless. Microsoft has whatever webserver xbox.com is on blocking pings (with good reason) and as others have said tracert having * * * gaps is simply indicative of a hop on the route blocking ICMP.

If you're experiencing packet loss, we're not going to be able to see it with ping or tracert tests in this instance.

 

[inachu]

Check and see if IPVIKING is showing if xbox is under attack.