Web Hosting Talk : Web Hosting Main Forums : Industry Announcements : Providers and Network Outages and Updates : Tomsyer (savvis) down

[beachcompcom]

Seems to be a routing issue.

tracert www.tomsyer.net

Tracing route to tomsyer.net [209.67.216.235]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms [10.0.0.1]
2 8 ms 37 ms 7 ms 10.10.32.1
3 9 ms 7 ms 22 ms ip096-001.the-beach.net [12.43.96.1]
4 10 ms 33 ms 10 ms 12.119.94.29
5 12 ms 14 ms 15 ms gbr4-p100.ormfl.ip.att.net [12.123.218.66]
6 22 ms 23 ms 54 ms tbr1-p012302.attga.ip.att.net [12.122.2.181]
7 22 ms 21 ms 22 ms ggr1-p340.attga.ip.att.net [12.122.12.30]
8 22 ms 21 ms 22 ms dcr1-so-4-0-0.atlanta.savvis.net [192.205.32.118]
9 39 ms 42 ms 79 ms bcr1.Dallas.savvis.net [208.172.130.63]
10 41 ms 55 ms 40 ms ohr1-pos-4-0.FortWorthda1.savvis.net [208.172.131.82]
11 40 ms 43 ms 40 ms csr1-ve241.FortWorthda1.savvis.net [216.39.64.42]
12 40 ms 40 ms 39 ms chr2-g1-0.FortWorthda1.savvis.net [216.39.64.41]
13 42 ms 41 ms 42 ms csr1-ve241.FortWorthda1.savvis.net [216.39.64.42]
14 39 ms 39 ms 41 ms chr2-g1-0.FortWorthda1.savvis.net [216.39.64.41]
15 42 ms 41 ms 40 ms csr1-ve241.FortWorthda1.savvis.net [216.39.64.42]
16 46 ms 61 ms 39 ms chr2-g1-0.FortWorthda1.savvis.net [216.39.64.41]
17 41 ms 41 ms 42 ms csr1-ve241.FortWorthda1.savvis.net [216.39.64.42]
18 41 ms 40 ms 42 ms chr2-g1-0.FortWorthda1.savvis.net [216.39.64.41]
19 41 ms 42 ms 44 ms csr1-ve241.FortWorthda1.savvis.net [216.39.64.42]
20 94 ms 75 ms 40 ms chr2-g1-0.FortWorthda1.savvis.net [216.39.64.41]
21 * 83 ms 42 ms csr1-ve241.FortWorthda1.savvis.net [216.39.64.42]
22 39 ms 40 ms 39 ms chr2-g1-0.FortWorthda1.savvis.net [216.39.64.41]
23 41 ms 52 ms 42 ms csr1-ve241.FortWorthda1.savvis.net [216.39.64.42]
24 41 ms 42 ms 39 ms chr2-g1-0.FortWorthda1.savvis.net [216.39.64.41]
25 45 ms 80 ms 70 ms csr1-ve241.FortWorthda1.savvis.net [216.39.64.42]
26 113 ms 124 ms 139 ms chr2-g1-0.FortWorthda1.savvis.net [216.39.64.41]
27 166 ms * 179 ms csr1-ve241.FortWorthda1.savvis.net [216.39.64.42]
28 123 ms 125 ms 131 ms chr2-g1-0.FortWorthda1.savvis.net [216.39.64.41]
29 157 ms 145 ms * csr1-ve241.FortWorthda1.savvis.net [216.39.64.42]
30 40 ms 44 ms 39 ms chr2-g1-0.FortWorthda1.savvis.net [216.39.64.41]





Pinging tomsyer.net [209.67.216.235] with 32 bytes of data:

Reply from 216.39.64.41: TTL expired in transit.
Reply from 216.39.64.41: TTL expired in transit.
Reply from 216.39.64.41: TTL expired in transit.
Reply from 216.39.64.41: TTL expired in transit.

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

[mkc]

Nagios showed my LT box at savvis down for the last few minutes too.. flutterng and high packet loss now.

[Cirrostratus]

Hello,

I am seeing some issues from charter but I am not seeing any sort of packet loss when I hit it from any of my other remote locations. I thought the problem was with just me.

I will raise a ticket with Savvis neteng to look into this.

Thanks

Jeremy

[mkc]

It is clear atm, but I'll post routes from a couple places if it starts dropping again.

[Cirrostratus]

mkc

Could you tell me what provider you are on seeing the problems from? Is it ATT or Charter based?

Thanks

Jeremy

[Cirrostratus]

Hello,

I am able to hit the sites now that I was unable to 10mins ago. I know my problems where between charter and others but I am not sure of you other guys.

Thanks

Jeremy

[mkc]

I run nagios monitoring off servint and it showed up-down x 2, about 3 minutes apart each time, so it seems it had some issues there.

When I pinged right now, though, servint and defenderhosting show 0 packet loss over 100 pings.

From cox (my isp), 108 packets transmitted, 95 received, 12% packet loss, time 107529ms

The route is cox.net --> level3.net -> savvis.net, but I'm not sure if that is charter or att?

[Cirrostratus]

I have opened a ticket with neteng about this as I saw it flap a second ago. Trying to source out if this is an issue with Savvis or another carrier inbetween myself and them.

Thanks

Jeremy

[mkc]

BTW, thanks for looking into this. I'm very happy with you as a provider overall

[Cirrostratus]

Not a problem. I have not seen any flap in the last 10 mins but I am going to keep watching for now. This only seems to be effecting one of our 209.67.208.0/20 range.

Thanks

Jeremy

[phpdeveloper]

The issue still seems to be present. Anyone can confirm?

[Dr.sloth]

Tomsyer seems to be up for me :|

[jaspink]

Originally posted by phpdeveloper
The issue still seems to be present. Anyone can confirm?

Seems to still be an issue... our 209.67.214.XX server is not responding - in Savvis

[Cirrostratus]

Originally posted by jaspink
Seems to still be an issue... our 209.67.214.XX server is not responding - in Savvis

Hello,

phpdevelopers servers where offline for other reasons un-related to the network problems that occured the other day. We are currently showing no problems with the 209.67.214.0/24 range.

Thanks

Jeremy

[LDKS]

Offline to me, ip 209.67.215.xxx