Guess what time it is. 90006 Time (NTT Failure)

Here ya go support rep. Maybe this time you can escalate this or any of the other 100's of examples that have good useful data to a Network Admin, DC Tech, or your Upstream provider. This is a low time and hardware should be at far lower load and stress as prime.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Redacted for Privacy - 0 | 61 | 61 | 0 | 1 | 8 | 1 |
| Redacted for Privacy - 0 | 60 | 60 | 8 | 13 | 22 | 13 |
| Redacted for Privacy - 0 | 60 | 60 | 9 | 14 | 22 | 19 |
| thyrmo-core1-bnd11.fidnet.com - 0 | 61 | 61 | 10 | 14 | 35 | 13 |
| wplnmo-core1-bnd10.fidnet.com - 0 | 61 | 61 | 10 | 15 | 27 | 15 |
| salmmo-core1-bnd4.fidnet.com - 0 | 61 | 61 | 12 | 18 | 26 | 24 |
| sllvmo-lcore2-bnd10.fidnet.com - 0 | 61 | 61 | 13 | 18 | 45 | 23 |
| 216-229-73-159.fidnet.com - 0 | 60 | 60 | 14 | 21 | 32 | 20 |
| 216-229-74-116.fidnet.com - 0 | 60 | 60 | 14 | 20 | 31 | 19 |
| 216-229-73-111.fidnet.com - 0 | 61 | 61 | 15 | 20 | 37 | 17 |
| stl-asr9010-bnd15.fidnet.com - 0 | 60 | 60 | 16 | 22 | 32 | 20 |
| 67-60-16-121.cpe.sparklight.net - 0 | 60 | 60 | 28 | 32 | 38 | 30 |
| 10.224.253.233 - 0 | 61 | 61 | 35 | 39 | 53 | 37 |
| chi-b23-link.ip.twelve99.net - 0 | 60 | 60 | 28 | 34 | 52 | 33 |
| ae-25.r08.chcgil09.us.bb.gin.ntt.net - 0 | 60 | 60 | 28 | 32 | 42 | 33 |
| ae-4.r23.chcgil09.us.bb.gin.ntt.net - 0 | 61 | 61 | 28 | 37 | 71 | 41 |
| ae-1.r24.snjsca04.us.bb.gin.ntt.net - 53 | 21 | 10 | 0 | 106 | 138 | 87 |
| ae-4.r00.scrmca02.us.bb.gin.ntt.net - 46 | 22 | 12 | 85 | 112 | 147 | 85 |
|xe-0-1-0-1-1.r00.scrmca02.us.ce.gin.ntt.net - 46 | 22 | 12 | 0 | 107 | 145 | 96 |
| 204.2.229.230 - 86 | 14 | 2 | 0 | 116 | 135 | 97 |
| 204.2.229.9 - 46 | 22 | 12 | 86 | 102 | 145 | 95 |

Thanks for your diligence. I suppose the reason why SE will not speak to the issue is for fear of lawsuits maybe?

Quote:

---

Originally Posted by Julisia

Thanks for your diligence. I suppose the reason why SE will not speak to the issue is for fear of lawsuits maybe?

---

It's more likely that they're working on the problem and either the status is constantly moving or they don't have anything to report other than what was already put out. "Fear of lawsuits"? It's outright stupid to assume they'd be legally liable, considering the ToS absolves them of any guarantee of being *able* to reach their servers. Don't like it? The door's behind the "Cancel Subscription" button on the Mog Station.

Quote:

---

Originally Posted by ijuakos_xqwzts

It's more likely that they're working on the problem and either the status is constantly moving or they don't have anything to report other than what was already put out. "Fear of lawsuits"? It's outright stupid to assume they'd be legally liable, considering the ToS absolves them of any guarantee of being *able* to reach their servers. Don't like it? The door's behind the "Cancel Subscription" button on the Mog Station.

---

Okay, I'm not stupid okay? ;-;

Maybe SE fears a lawsuit against their upstream provider by speaking ill of them. - that's what I meant.
Players have no standing to file suit as you so aptly put it.

Why are the NTT networks such a POS? I'm constantly getting horrible latency on their nodes. Useless company.

Just 90006'd out of the game and back into a 4000+ queue and it's still morning. This is clearly their fault, stop blaming all the errors on our connections.

Quote:

---

Originally Posted by Macleod

Just 90006'd out of the game and back into a 4000+ queue and it's still morning. This is clearly their fault, stop blaming all the errors on our connections.

---

They've had plenty of data from all of us on the forums for the past weeks / months. They're clearly turning a blind eye to the problem.

Quote:

---

Originally Posted by Annabellechu

They've had plenty of data from all of us on the forums for the past weeks / months. They're clearly turning a blind eye to the problem.

---

I'm beginning to think they have backed themselves in a corner have no idea what to do.

Funny how this lobby is called "Technical Support" and there's absolutely zero support on the matter - even when there's plain evidence of where the problem is.

Is there a phone number or email we can use to poke / push NTT to fix their shit?