Having packet loss on my end.

Anyone else experiencing problems?

Everything good here...

Can you please do a trace for netrillium.net ?

C:\Documents and Settings\roy>tracert netrillium.net

Tracing route to netrillium.net [216.180.241.99]
over a maximum of 30 hops:

1 39 ms 39 ms 35 ms barak-1-lns-4.barak.net.il [62.90.133.4]
2 62 ms 67 ms 69 ms 62.90.133.14
3 41 ms 39 ms 35 ms barak-1-bb-backbone.barak.net.il [206.49.94.115]

4 31 ms 25 ms 25 ms 212.150.232.85
5 148 ms 142 ms 147 ms 212.150.232.70
6 128 ms 112 ms 110 ms 212.150.232.173
7 136 ms 145 ms 193 ms ldn-b2-geth10-0-129.telia.net [213.248.75.205]
8 120 ms 125 ms 128 ms ldn-thoe-b1-pos5-0.telia.net [213.248.74.38]
9 124 ms 130 ms 150 ms ge9-0.mpr2.lhr1.uk.mfnx.net [195.66.226.76]
10 173 ms 174 ms 150 ms so-4-1-0.cr2.lhr3.uk.mfnx.net [208.185.156.2]
11 190 ms 183 ms 175 ms so-7-0-0.cr2.lga1.us.mfnx.net [64.125.31.182]
12 185 ms 191 ms 187 ms so-0-0-0.cr2.lga2.us.mfnx.net [208.184.232.198]

13 195 ms 200 ms 196 ms so-4-0-0.cr2.atl2.us.mfnx.net [208.184.232.157]

14 215 ms 213 ms 222 ms 64.124.17.5.tranxact.com [64.124.17.5]
15 274 ms 271 ms 265 ms atl-core-router-b.dv2.net [209.51.134.66]
16 1140 ms 1151 ms * 209.51.131.14
17 1182 ms 1246 ms 1197 ms 216.180.241.99

I am having the same problems. Cannot connect at all via Terminal Services. I have submitted a trouble ticket.

Tracert goes through fine for me, 100ms on the destination.

Yes, there are issues. Alertra shows in-out in-out from different locations.

Same problem here:

209.51.131.14 | dv2-atl-clark-hinkle-lan2.dv2.net

%loss=90

:rolleyes:

They're definitely having problems.

I am back to normal

This is Tracert for RSMHost, Everything good here:

C:\Documents and Settings\roy>tracert www.rsmhost.com

Tracing route to rsmhost.com [209.51.152.142]
over a maximum of 30 hops:

1 55 ms 61 ms 61 ms barak-1-lns-4.barak.net.il [62.90.133.4]
2 26 ms 25 ms 29 ms 62.90.133.14
3 24 ms 37 ms 60 ms barak-1-bb-backbone.barak.net.il [206.49.94.115]

4 78 ms 64 ms 38 ms 212.150.232.85
5 155 ms 168 ms 176 ms 212.150.232.70
6 172 ms 175 ms 160 ms 212.150.232.173
7 140 ms 140 ms 158 ms ldn-b2-geth10-0-129.telia.net [213.248.75.205]
8 108 ms 137 ms 142 ms ldn-thoe-b1-srp9-0.telia.net [193.45.0.134]
9 141 ms 142 ms 139 ms ge9-0.mpr2.lhr1.uk.mfnx.net [195.66.226.76]
10 145 ms 148 ms 144 ms so-4-1-0.cr2.lhr3.uk.mfnx.net [208.185.156.2]
11 203 ms * 184 ms so-7-0-0.cr2.lga1.us.mfnx.net [64.125.31.182]
12 209 ms 185 ms 194 ms so-0-0-0.cr2.lga2.us.mfnx.net [208.184.232.198]

13 198 ms 216 ms * so-4-0-0.cr2.atl2.us.mfnx.net [208.184.232.157]

14 * 211 ms 233 ms 64.124.17.5.tranxact.com [64.124.17.5]
15 259 ms 293 ms 273 ms DV2-L3-ATL-2.dv2.net [209.51.130.211]
16 209 ms 215 ms 225 ms 209.51.152.142

Trace complete.

There were 2 different servers causing the network to mess up. They have been dealt with.

There were 2 different servers causing the network to mess up. They have been dealt with. :D

It was a DDOS attack caused by two servers. This has been rectified.

Sorry for the inconvenience.