?
Joined: Jul 2001
Posts: 3,303
Likes: 23
From: Calgary
Yup...and the server appears to be getting slower and slower all the time.
Hey Paul....I wasn't aware we had any members this close to Peterborough? I was there last week and spent a week In P'boro (born and raised there), and then a week in Stamford before heading back to Canada. Had I known, we woulda/coulda met up!
Asif
Hey Paul....I wasn't aware we had any members this close to Peterborough? I was there last week and spent a week In P'boro (born and raised there), and then a week in Stamford before heading back to Canada. Had I known, we woulda/coulda met up!
Asif
Registered User
Joined: Sep 2002
Posts: 20,574
Likes: 0
From: On a street corner
I didn't check it out tonight but the other night I did a bit of investigation into what was occurring.
The ip address for www.s2ki.com (64.62.178.153) was not being propagated out to the internet i.e. your ISPs didn't know how to get to it. In case it was a single node failure I checked out whether the entire calss A address range was being propagated and the looking glass facility at Lynx couldn't see it.
Lynx is the UK international routing gateway for those not in networks. If anywhere in the UK will be able to see it is there. So if it loses the route you can bet your ISP will have done.
The natural assumption therefore is that the BGP border router that the s2ki server sits near was failing or one of the gateway routers between the server and the external AS router failed to publish the route or was down entirely.
Amazing what 5 mins of trouble shooting can do - either that or another reason which, with the visibility I have from here, I can't establish.
Jeez - I gotta get a life.
The ip address for www.s2ki.com (64.62.178.153) was not being propagated out to the internet i.e. your ISPs didn't know how to get to it. In case it was a single node failure I checked out whether the entire calss A address range was being propagated and the looking glass facility at Lynx couldn't see it.
Lynx is the UK international routing gateway for those not in networks. If anywhere in the UK will be able to see it is there. So if it loses the route you can bet your ISP will have done.
The natural assumption therefore is that the BGP border router that the s2ki server sits near was failing or one of the gateway routers between the server and the external AS router failed to publish the route or was down entirely.
Amazing what 5 mins of trouble shooting can do - either that or another reason which, with the visibility I have from here, I can't establish.
Jeez - I gotta get a life.
Registered User
Joined: Nov 2002
Posts: 16,126
Likes: 3
From: Lanarkshire
If I read you correctly Kelk, then any sites in the 0.xxx.xxx.xxx range to 127.xxx.xxx.xx would be unavailable at the same time as the S2Ki outage.
My company's main websites are in that range are were available at that time.
You've said "If anywhere in the UK will be able to see it is there." but I'm not sure if this means that UK addresses, (which ours are), will still be seen.
Want to clarify?
My company's main websites are in that range are were available at that time.
You've said "If anywhere in the UK will be able to see it is there." but I'm not sure if this means that UK addresses, (which ours are), will still be seen.
Want to clarify?
Trending Topics
Registered User
Joined: Sep 2002
Posts: 20,574
Likes: 0
From: On a street corner
To be fair I have been a little misleading.
The address range I checked was the 64.62.178.x / 24 obviously no one AS has the monopoly of the entire list of class A addresses. That would be getting on for half the ip addresses in the world before IPv6 becomes ratified and deployed worldwide rather than on test nets. Sorry if I was off the mark, its late and I've had a couple of manic days at work.
The global location of ip address allocation is distributed by the likes or Arin in the US and RIPE for Europe.
If you are within the AS then you would be able to see the ip addresses, or if the BGP gateway router is working within the area you would be able to see it. Hence you could see your work ips as they were not being distributed by the same router that is responsible for 64.62.178.x / 24.
There are several good books out there on the market for a longer (and no where near as summarized as my description) on the market. Look at Amazon for BGP v4 and that will bring a healthy list out.
I am sure there are others who will add to my v. brief top level overview here and great, shared knowledge is a good thing.
And I repeat I'm really really tired.
The address range I checked was the 64.62.178.x / 24 obviously no one AS has the monopoly of the entire list of class A addresses. That would be getting on for half the ip addresses in the world before IPv6 becomes ratified and deployed worldwide rather than on test nets. Sorry if I was off the mark, its late and I've had a couple of manic days at work.
The global location of ip address allocation is distributed by the likes or Arin in the US and RIPE for Europe.
If you are within the AS then you would be able to see the ip addresses, or if the BGP gateway router is working within the area you would be able to see it. Hence you could see your work ips as they were not being distributed by the same router that is responsible for 64.62.178.x / 24.
There are several good books out there on the market for a longer (and no where near as summarized as my description) on the market. Look at Amazon for BGP v4 and that will bring a healthy list out.
I am sure there are others who will add to my v. brief top level overview here and great, shared knowledge is a good thing.
And I repeat I'm really really tired.
