gistfile1.txt

Ticket: #141419
OHtele Support
No connectivity to Xeriom.net
Created: 27 October 2011 08:09 PM    Updated: 27 October 2011 08:09 PM
DEPARTMENT
OHtele Support

OWNER
Unassigned

TYPE
Issue

STATUS


PRIORITY



Craig Webster
User
Posted on: 27 October 2011 08:09 PM
It's been 9 days since this ticket has had a response. It's still open.

Can you please let me know what the maintenance was for, when I was informed about it, and why it's taken so long to get this information?
    
Craig Webster
User
Posted on: 24 October 2011 07:35 PM
Hi,

This high priority ticket has been open for nearly a week now. Any chance of an update?

Cheers,
Craig
    
Craig Webster
User
Posted on: 18 October 2011 11:16 AM
Phoned to get a quick update and told that the team had finished their work bout 30 minutes ago but there was no connectivity still. After some subsequent work connectivity has been restored and I seem to be able to access my network again.

Can you please let me know what the maintenance was for and when I was informed about it? I need to pass this information on to my clients who are understandably somewhat grumpy about a 12 hour maintenance with total lack of connectivity that I didn't tell them about.

Cheers,
Craig
    
Steven Watson
Staff
Posted on: 18 October 2011 09:17 AM
Hi Craig,

As we spoke on the phone earlier, I informed you that there was currently maintenance going on down in London through our company. I apologise for this, but i will ring you back and update you as soon as possible.
Regards,

Steven Watson

Datacentre Support Technician | Connected with Our Customers

M247 Ltd, registered in England & Wales #4968341. 1 Ball Green, Cobra Court, Manchester, M32 0QT
    
Craig Webster
User
Posted on: 18 October 2011 08:50 AM
Hey,

I'm having problems connecting to Xeriom.net from several places, wondering if there's a problem that you know about or if it's a problem at our end?

Here are a few traceroutes which seem to show traffic getting as far as the OHTele.com network but not to the Xeriom network.

From my home:

1 10.0.1.1 (10.0.1.1) 2.266 ms 1.001 ms 0.784 ms
2 10.240.76.1 (10.240.76.1) 83.740 ms 12.725 ms 9.353 ms
3 bmly-core-1a-ae1-2442.network.virginmedia.net (81.100.1.37) 8.306 ms 16.745 ms 7.493 ms
4 popl-bb-1a-as6-0.network.virginmedia.net (212.43.162.57) 9.917 ms 9.851 ms 11.571 ms
5 manc-bb-1b-as1-0.network.virginmedia.net (212.43.162.86) 14.816 ms 14.083 ms 29.474 ms
6 manc-bb-1a-ae0-0.network.virginmedia.net (62.253.187.177) 15.786 ms 54.317 ms 15.860 ms
7 tcma-ic-1-ae0-0.network.virginmedia.net (212.43.163.226) 15.554 ms 15.362 ms 17.788 ms
8 virginmedia-pni.ge-1-.bb1.man1.uk.gbxs.net (212.250.14.174) 25.016 ms 22.421 ms 21.532 ms
9 xe-4-3-0.bb1.man2.uk.gbxs.net (193.27.64.154) 123.582 ms 114.215 ms 229.435 ms
10 no-rdns-yet.ohtele.com (89.238.140.101) 23.587 ms 37.539 ms 23.670 ms
11 no-rdns-yet.ohtele.com (89.238.140.126) 24.721 ms 25.293 ms 26.653 ms

From Amazon EC2:

1: ip-10-229-40-3.eu-west-1.compute.internal 0.625ms 
2: ec2-79-125-0-82.eu-west-1.compute.amazonaws.com 0.408ms 
3: ec2-79-125-0-5.eu-west-1.compute.amazonaws.com 0.417ms 
4: 178.236.0.59 0.424ms 
5: 178.236.0.74 1.169ms asymm 8 
6: 178.236.3.123 14.591ms 
7: 178.236.3.38 16.731ms 
8: ae-1.asd9nqp1.nl.ip.tdc.net 13.904ms 
9: ae2-0.ldn4nqp1.uk.ip.tdc.net 18.651ms 
10: cpe.xe-4-1-0-223.ldn4nqp1.customer.tele.dk 27.804ms 
11: Vlan2.bb1.man1.uk.gbxs.net 35.237ms asymm 14 
12: xe-4-3-0.bb1.man2.uk.gbxs.net 303.098ms 

A similar outage occurred on September 23rd, and I have similar traceroutes from then too. When not having a problem the route looks something like this: https://gist.github.com/9d3acb9737b87bfcf5fe

Is this something that you can help with?