NT9 ... Any update?

[Scroller]

How is NT9 coming along? It's been going up and down for the last few hours? Thanks!

To the best of my knowledge, nt9 is fine. Alex did not pass on any info about a problem.

[Scroller]

*strange* ... we have been having problem accessing all the machines the whole morning actually ... it's been going up and down ... or is the router patch that's causing the problem?

we can't ping or tracert any of the hsphere.cc domains but can do so for our service domain ...

Unable to resolve target system name nt10.hsphere.cc.

Tracing route to nt10.episode12.net [65.57.227.129] over a maximum of 30 hops:
1 <10 ms <10 ms <10 ms 192.168.1.1
2 <10 ms 16 ms <10 ms 202.172.39.129
3 15 ms 16 ms <10 ms 202.172.36.173
4 <10 ms 15 ms 16 ms fe2-cs1.gwnnet.net [202.172.32.189]
5 <10 ms 16 ms 16 ms ge0-cr1.gwnnet.net [202.172.32.205]
6 16 ms 15 ms 16 ms 61.8.233.137
7 31 ms 16 ms 16 ms ge-1-0-0.r00.sngpsi01.sg.bb.verio.net [61.8.234.93]
8 219 ms 219 ms 234 ms p1-0-1-2.r81.mlpsca01.us.bb.verio.net [129.250.4.149]
9 234 ms 250 ms 234 ms p16-1-1-0.r20.mlpsca01.us.bb.verio.net [129.250.2.247]
10 234 ms 234 ms 235 ms p16-1-1-0.r20.snjsca04.us.bb.verio.net [129.250.5.9]
11 219 ms 234 ms 235 ms interconnect-eng.SanJose1.Level3.net [209.245.146.241]
12 235 ms 234 ms 219 ms so-5-0-0.gar1.SanJose1.level3.net [209.244.3.137]
13 235 ms 234 ms 234 ms so-7-0-0.mp1.SanJose1.Level3.net [64.159.1.73]
14 359 ms 328 ms 359 ms so-0-2-0.mp1.Orlando1.Level3.net [64.159.0.29]
15 359 ms 313 ms 328 ms gige10-0.hsa1.Orlando1.Level3.net [64.159.0.34]
16 281 ms 297 ms 297 ms 67.30.136.2
17 344 ms 312 ms 328 ms 66.103.132.6
18 313 ms * 313 ms 65.57.227.129
Trace complete.


Unable to resolve target system name nt9.hsphere.cc.



Tracing route to nt9.episode12.net [216.157.129.2] over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms 192.168.1.1
2 16 ms <10 ms 15 ms 202.172.39.129
3 16 ms <10 ms 16 ms 202.172.36.173
4 15 ms <10 ms 16 ms fe2-cs1.gwnnet.net [202.172.32.189]
5 16 ms <10 ms 15 ms ge0-cr1.gwnnet.net [202.172.32.205]
6 16 ms 31 ms 16 ms 61.8.233.137
7 16 ms 15 ms 16 ms ge-1-0-0.r00.sngpsi01.sg.bb.verio.net [61.8.234.93]
8 203 ms 234 ms 203 ms p1-0-1-2.r81.mlpsca01.us.bb.verio.net [129.250.4.149]
9 235 ms 234 ms 250 ms p16-1-1-0.r20.mlpsca01.us.bb.verio.net [129.250.2.247]
10 250 ms 234 ms 235 ms p16-1-1-0.r20.snjsca04.us.bb.verio.net [129.250.5.9]
11 234 ms 235 ms 234 ms interconnect-eng.SanJose1.Level3.net [209.245.146.241]
12 281 ms 219 ms 234 ms so-5-0-0.gar1.SanJose1.level3.net [209.244.3.137]
13 250 ms 234 ms 234 ms so-7-0-0.mp1.SanJose1.Level3.net [64.159.1.73]
14 328 ms 328 ms 313 ms so-0-2-0.mp1.Orlando1.Level3.net [64.159.0.29]
15 313 ms 328 ms 359 ms gige10-2.hsa1.Orlando1.Level3.net [209.247.11.38]
16 297 ms 281 ms 297 ms 67.30.136.2
17 312 ms 329 ms 312 ms 66.103.132.6
18 * * 313 ms 216.157.129.2

Trace complete.

[Scroller]

actually michael wrote this ...

http://www.matrixwebhosting.net/foru...&highlight=nt9

"It looks like NT9 is having "issues" with the update, we have someone going over to the datacenter to look in on it, it should be online shortly. We’ll update the situation here when more information becomes available. For the time being the server is offline for all services, we apologies for the inconvenience."

I was able to tracert to nt9.hsphere.cc, I am offnetwork on my laptop.

over a maximum of 30 hops:

1 3 ms 3 ms 3 ms 192.168.0.1
2 13 ms 11 ms 14 ms 10.108.0.1
3 12 ms 14 ms 11 ms srp1-0.orldflwrpk-rtr2.cfl.rr.com [24.95.224.39

4 13 ms 17 ms 14 ms srp4-0.orldfldvsn-rtr4.cfl.rr.com [24.95.224.10

5 22 ms 22 ms 23 ms pop1-tby-P0-2.atdn.net [66.185.136.173]
6 23 ms 23 ms 20 ms bb1-tby-P0-0.atdn.net [66.185.136.160]
7 58 ms 41 ms 41 ms bb2-atm-P7-0.atdn.net [66.185.152.245]
8 27 ms 40 ms 41 ms pop2-atm-P1-0.atdn.net [66.185.147.211]
9 38 ms 40 ms 40 ms level3.atdn.net [66.185.138.34]
10 67 ms 40 ms 48 ms so-4-1-0.bbr1.Atlanta1.level3.net [209.247.9.16
]
11 48 ms 75 ms 55 ms so-0-2-0.mp1.Orlando1.Level3.net [64.159.0.29]
12 53 ms 61 ms 49 ms gige11-0.hsa1.Orlando1.Level3.net [209.247.11.4
]
13 71 ms 66 ms 51 ms 67.30.136.2
14 50 ms 52 ms 50 ms 66.103.132.6
15 63 ms 63 ms 65 ms nt9.hsphere.cc [216.157.129.2]

Trace complete.

[Scroller]

I'm getting very poor results ...



Pinging nt9.hsphere.cc [216.157.129.2] with 32 bytes of data:

Request timed out.
Reply from 216.157.129.2: bytes=32 time=313ms TTL=105
Reply from 216.157.129.2: bytes=32 time=313ms TTL=105
Request timed out.

Ping statistics for 216.157.129.2:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

Approximate round trip times in milli-seconds:
Minimum = 313ms, Maximum = 313ms, Average = 156ms



Pinging nt10.hsphere.cc [65.57.227.129] with 32 bytes of data:
Request timed out.
Reply from 65.57.227.129: bytes=32 time=313ms TTL=105
Request timed out.
Reply from 65.57.227.129: bytes=32 time=344ms TTL=105

Ping statistics for 65.57.227.129:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 313ms, Maximum = 344ms, Average = 164ms

As I stated before, I am off network.

Pinging nt9.hsphere.cc [216.157.129.2] with 32 bytes of data:

Reply from 216.157.129.2: bytes=32 time=62ms TTL=108
Reply from 216.157.129.2: bytes=32 time=62ms TTL=108
Reply from 216.157.129.2: bytes=32 time=62ms TTL=108
Reply from 216.157.129.2: bytes=32 time=61ms TTL=108

Ping statistics for 216.157.129.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 61ms, Maximum = 62ms, Average = 61ms

Pinging nt10.hsphere.cc [65.57.227.129] with 32 bytes of data:

Reply from 65.57.227.129: bytes=32 time=74ms TTL=108
Reply from 65.57.227.129: bytes=32 time=62ms TTL=108
Reply from 65.57.227.129: bytes=32 time=61ms TTL=108
Reply from 65.57.227.129: bytes=32 time=62ms TTL=108

Ping statistics for 65.57.227.129:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 61ms, Maximum = 74ms, Average = 64ms

[admin]

Scroller, I have not seen any issues after the update yesterday, I just pinged and did a tracert and all seems to be coming back fine. Not seeing any issues on IPmon from it ether.