Servint down AGAIN!

TotalChoice · #1 12-22-2003, 03:25 AM

Looks like another outage @ servint.

Anyone else having issues there?

ultrafex · #2 12-22-2003, 03:36 AM

Confirmed.

It seems WCG can't route.

TotalChoice · #3 12-22-2003, 03:40 AM

We have had so many outages of late, they need to really get it together.

TotalChoice · #4 12-22-2003, 03:43 AM

update from Servint -

Hi,

all the servers on our facility are currently up. They are unreachable
due to communication problems with our Network Provider. Engineering is
currently working to resolve the problem as quickly as possible.

-Jorge
ServInt NOC

kb9tyc · #5 12-22-2003, 04:03 AM

This is really begining to suck. Traceroute from io.com works. It did the other night when it was down also. You would think they would at least notify people of the cause. I never received anything from the last outage. I suppose I shouldn't complain since I didn't ask.

traceroute to servint.net (209.50.251.77), 30 hops max, 38 byte packets
1 iocom-pnet-FA0-0.iocomcorp.net (206.224.79.77) 0.460 ms 0.319 ms 0.398 ms
2 pnet-gw.iocomcorp.net (206.224.79.82) 0.686 ms 0.404 ms 0.439 ms
3 hagg-01-t3-1-0-0-0.ausu.twtelecom.net (64.132.190.45) 1.622 ms 1.418 ms 1.515 ms
4 66-192-253-160.gen.twtelecom.net (66.192.253.160) 2.478 ms 1.446 ms 1.380 ms
5 core-01-so-1-0-0-0.dlfw.twtelecom.net (168.215.53.93) 6.253 ms 5.634 ms 5.646 ms
6 core-02-so-0-0-0-0.chcg.twtelecom.net (66.192.255.88) 27.881 ms 28.056 ms 29.718 ms
7 core-01-ge-0-2-1-2.chcg.twtelecom.net (66.192.244.64) 27.873 ms 27.874 ms 28.243 ms
8 peer-03-so-2-3-0-0.chcg.twtelecom.net (66.192.244.54) 28.081 ms 29.272 ms 28.044 ms
9 chi1-br1-f4-0-99.gnaps.net (206.223.119.41) 33.765 ms 28.585 ms 28.743 ms
10 qcy1-rs38k-p1-16-1.gnaps.net (199.232.42.97) 51.627 ms 51.420 ms 52.005 ms
11 ash-m20-at0-2-0.gnaps.net (199.232.44.53) 63.886 ms 63.835 ms 95.903 ms
12 f3-0.br1.mcl1.cent.net (199.232.56.26) 64.928 ms 64.564 ms 64.540 ms
13 www.servint.net (209.50.251.77) 65.217 ms 64.806 ms 64.715 ms