Reporting a Service Outage

Status
Not open for further replies.

jtwhite

Community Advocate
Community Support
Messages
1,381
Reaction score
30
Points
0
It looks like a simple DNS problem. It should resolve itself soon.

For staff's reference:
C:\Users\Justin>ping ufcirclek.x10hosting.com

Pinging ufcirclek.x10hosting.com [74.63.233.26] with 32 bytes of data:
Reply from 74.63.233.26: bytes=32 time=60ms TTL=49
Reply from 74.63.233.26: bytes=32 time=58ms TTL=49
Reply from 74.63.233.26: bytes=32 time=58ms TTL=49
Reply from 74.63.233.26: bytes=32 time=59ms TTL=49

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

C:\Users\Justin>ping chopin.x10hosting.com

Pinging chopin.x10hosting.com [216.245.205.67] with 32 bytes of data:
Reply from 216.245.205.67: bytes=32 time=55ms TTL=48
Reply from 216.245.205.67: bytes=32 time=58ms TTL=48
Reply from 216.245.205.67: bytes=32 time=59ms TTL=48
Reply from 216.245.205.67: bytes=32 time=59ms TTL=48

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

EDIT: I received confirmation from Corey that this is in fact a DNS issue. This will be fixed when Chopin is finished migrating. You can check the status here: http://status.x10hosting.com
 
Last edited:
Status
Not open for further replies.
Top