#1
|
|||
|
Lumen/Lightower handoff is dirty again
bear2.Boston1.Level3.net probably has a bad line card. If you pass this to lightower they can pass it to their upstream peer to investigate.
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | dsldevice.attlocal.net - 0 | 105 | 105 | 8 | 21 | 78 | 11 | |99-184-16-1.lightspeed.rswlga.sbcglobal.net - 0 | 105 | 105 | 19 | 33 | 93 | 20 | | 76.239.205.93 - 0 | 105 | 105 | 29 | 41 | 96 | 31 | | 12.242.113.45 - 1 | 101 | 100 | 29 | 46 | 101 | 61 | | 4.68.62.225 - 1 | 101 | 100 | 29 | 47 | 102 | 61 | | ae-1-11.bear2.Boston1.Level3.net - 92 | 23 | 2 | 73 | 101 | 130 | 73 | | FIBERTECH-N.bear2.Boston1.Level3.net - 33 | 46 | 31 | 51 | 63 | 134 | 79 | | ae3-bstpmalljp1.lightower.net - 32 | 47 | 32 | 53 | 65 | 133 | 57 | | 160.72.248.57.lightower.net - 27 | 53 | 39 | 0 | 64 | 123 | 62 | | ae0-brtnmas6j81.lightower.net - 23 | 58 | 45 | 53 | 67 | 135 | 53 | | 144.121.39.122.lightower.net - 21 | 58 | 46 | 52 | 66 | 137 | 62 | | No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 22 | 0 | 0 | 0 | 0 | 0 | |________________________________________________| ______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider | ||
#2
|
|||
|
I'm pinging login.eqemulator.net. Here's another MTR with the host names unresolved:
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.254 - 0 | 100 | 100 | 14 | 20 | 77 | 17 | | 99.184.16.1 - 0 | 100 | 100 | 29 | 37 | 94 | 36 | | 76.239.205.93 - 0 | 100 | 100 | 35 | 41 | 100 | 38 | | 12.242.113.45 - 0 | 100 | 100 | 33 | 47 | 109 | 38 | | 4.68.62.225 - 3 | 93 | 91 | 25 | 42 | 109 | 60 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | 166.90.184.30 - 34 | 45 | 30 | 51 | 66 | 128 | 60 | | 144.121.35.37 - 31 | 46 | 32 | 0 | 68 | 111 | 62 | | 160.72.248.57 - 25 | 53 | 40 | 52 | 66 | 135 | 53 | | 65.254.31.58 - 34 | 45 | 30 | 0 | 65 | 123 | 60 | | 144.121.39.122 - 40 | 40 | 24 | 55 | 68 | 138 | 56 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | |________________________________________________| ______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider | ||
#3
|
|||
|
I'm pinging login.eqemulator.net. Here's another MTR with the host names unresolved:
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.1.254 - 0 | 100 | 100 | 14 | 20 | 77 | 17 | | 99.184.16.1 - 0 | 100 | 100 | 29 | 37 | 94 | 36 | | 76.239.205.93 - 0 | 100 | 100 | 35 | 41 | 100 | 38 | | 12.242.113.45 - 0 | 100 | 100 | 33 | 47 | 109 | 38 | | 4.68.62.225 - 3 | 93 | 91 | 25 | 42 | 109 | 60 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | 166.90.184.30 - 34 | 45 | 30 | 51 | 66 | 128 | 60 | | 144.121.35.37 - 31 | 46 | 32 | 0 | 68 | 111 | 62 | | 160.72.248.57 - 25 | 53 | 40 | 52 | 66 | 135 | 53 | | 65.254.31.58 - 34 | 45 | 30 | 0 | 65 | 123 | 60 | | 144.121.39.122 - 40 | 40 | 24 | 55 | 68 | 138 | 56 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 | |________________________________________________| ______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider | ||
#4
|
|||
|
The fact that it allowed double posts probably demonstrates how bad inbound traffic is looking. I haven't been able to log in for hours.
You can also add a poison provider community to your BGP session to stop advertising your ASN to Lumen/Level3. This will force traffic to reach Lightower via another provider, which will route inbound traffic away from that bad Level3 device. | ||
#5
|
|||
|
Thanks for help diagnosing this
Been having issues like this on an off since I started playing here but have not been able to log in most of the day.
Am hoping this is not a regular occurrence as I love the servers and community so far. | ||
#6
|
|||
|
It is a regular occurence.
| ||
#7
|
|||
|
Seems to be the same thing again tonight. Ran a tracert and made it to the same IP before timing out ( 144.121.39.122.lightower.net )
Wish I could remember how to do more or knew more about this, but only know basics... | ||
#8
|
|||
|
Login server is unavailable every every night during prime time now.
| ||
#9
|
|||
|
Perfectly clean if I test over my tmobile android usb tethered:
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 192.168.42.129 - 0 | 213 | 213 | 1 | 3 | 7 | 3 | | dsldevice.attlocal.net - 0 | 213 | 213 | 4 | 9 | 174 | 8 | |99-184-16-1.lightspeed.rswlga.sbcglobal.net - 0 | 213 | 213 | 20 | 26 | 207 | 25 | | 76.239.205.93 - 0 | 213 | 213 | 25 | 32 | 424 | 29 | | 12.242.113.45 - 0 | 213 | 213 | 24 | 39 | 521 | 31 | | 4.68.62.225 - 1 | 206 | 204 | 25 | 38 | 283 | 43 | | No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 | | FIBERTECH-N.bear2.Boston1.Level3.net - 0 | 213 | 213 | 48 | 58 | 459 | 52 | | ae3-bstpmalljp1.lightower.net - 0 | 213 | 213 | 51 | 63 | 569 | 56 | | 160.72.248.57.lightower.net - 0 | 213 | 213 | 50 | 60 | 537 | 56 | | ae0-brtnmas6j81.lightower.net - 0 | 213 | 213 | 50 | 60 | 506 | 58 | | 144.121.39.122.lightower.net - 0 | 213 | 213 | 50 | 59 | 521 | 54 | | No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 | | No response from host - 100 | 44 | 0 | 0 | 0 | 0 | 0 | |________________________________________________| ______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider | ||
#10
|
|||
|
Sorry I'm an idiot ... the above trace was still going over ATT because my phone was on wifi. Still having the problem ... it was fine all day but screwed me in the evening.
| ||
|
|