SixXS::Sunset 2017-06-06

Problems with SCARLET POP
[lu] Shadow Hawkins on Wednesday, 01 September 2004 14:00:20
Hello, I currently see problems to connect to SCARLET: traceroute to 213.204.193.2 (213.204.193.2), 30 hops max, 38 byte packets 1 eth1.cloche.gw.luxadmin.org (195.206.107.254) 0.190 ms 0.125 ms 0.091 ms 2 80.92.66.1 (80.92.66.1) 0.285 ms 0.267 ms 0.249 ms 3 80.92.67.100 (80.92.67.100) 0.633 ms 0.828 ms 0.762 ms 4 62.72.104.210 (62.72.104.210) 26.385 ms 1.123 ms 2.425 ms 5 pos7-3-cr2.BRU.router.colt.net (212.74.68.145) 6.423 ms 12.653 ms 8.050 ms 6 212.74.66.1 (212.74.66.1) 8.700 ms 14.248 ms 9.942 ms 7 * sara.ams-ix.juniper-1.network.scarlet.nl (195.69.144.130) 125.248 ms * 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * There seems to be major outages in EUROPE. Currently affecting KPN Eurorings AS286, COLT Internet Backbone AS8220 and maybe some others. Will Sixxs count my Tunnel as down, even if it isn't my fault??? And even if the problem may be inside the POPs network??? Best regards, Marc
Problems with SCARLET POP
[ch] Jeroen Massar SixXS Staff on Wednesday, 01 September 2004 14:06:37
traceroute to 195.206.107.254 (195.206.107.254), 64 hops max, 44 byte packets 1 ge-0-0-0-7.jun.intx.network.scarlet.nl (213.204.193.1) 0.610 ms 0.375 ms 0.315 ms 2 g8-0-cr1.AMS.router.colt.net (195.69.144.236) 0.521 ms 0.485 ms 0.463 ms 3 pos3-0-ar1.LUX.erp.router.colt.net (212.74.68.146) 8.510 ms 9.149 ms 8.742 ms 4 * * * You mean that the ISP you are using for IPv4 doesn't know exactly how to deliver packets back to you?
There seems to be major outages in EUROPE. Currently affecting KPN Eurorings
AS286, COLT Internet Backbone AS8220 and maybe some others. Will Sixxs count my Tunnel as down, even if it isn't my fault???
It is your fault, get yourself a better IPv4 provider.
And even if the problem may be inside the POPs network???
First you say that it is a problem at those ISP's then you blame Scarlet, how very nice of you. PS: "If you want to ask a question to the SixXS Staff, either operational issues, abuse and/or other questions, then these should be directed to the contact address. The SixXS Staff don't regulary browse the forums, thus if you want to ask them something use the contact address." Guess why we put that up there...
Problems with SCARLET POP
[lu] Shadow Hawkins on Friday, 03 September 2004 17:27:10
It is your fault, get yourself a better IPv4 provider.
Why should I get a better, perhaps you should get a better one. But that's not what I wanted to say! There are situation where neither one of the 2 Endpoint Operators can do anything about connectivity problems somewhere between them!
First you say that it is a problem at those ISP's then you blame Scarlet, how very nice of you.
When you look at the traceroute, it ends somewhere inside Scarlet's Network. I never said the problem was located there, only that I have problems to connect THERE!!! Which is a difference! Then at the end, I must say, that you answer is not the answer I expected from an organisation promoting IPv6.
Problems with SCARLET POP
[ch] Jeroen Massar SixXS Staff on Friday, 03 September 2004 17:41:11
> It is your fault, get yourself a better IPv4 provider.
Why should I get a better, perhaps you should get a better one.
The ISP I am using really works perfectly well, they fulfill their SLA perfectly. I have nothing to complain at all.
There are situation where neither one of the 2 Endpoint Operators can do anything about connectivity problems somewhere between them!
Of course you can, well you can't but the ISP you are getting the connectivity from can: * Monitoring their network * Having multiple upstreams. And as COLT is one of those known problematic providers, I have nothing else to say there but: call them and let them fix their network.
When you look at the traceroute, it ends somewhere inside Scarlet's Network. I never said the problem was located there, only that I have problems to connect THERE!!! Which is a difference!
Because the packets can't get back to you, welcome to the wonderful world of the Internet which uses BGP and thus sometimes asymetric paths for routing. This sounds more like filtering port 80 on your machine and saying then blaming the ISP's that websites don't work.
Then at the end, I must say, that you answer is not the answer I expected from an organisation promoting IPv6.
What do you expect then? That we are going to call your ISP and resolve your problems while it is not our problem? If it really was a SixXS problem, why didn't you contact the SixXS Staff and notified them of this issue? You did notice the "If you want to ask a question to the SixXS Staff, either operational issues, abuse and/or other questions, then these should be directed to the contact address. The SixXS Staff don't regulary browse the forums, thus if you want to ask them something use the contact address." notice when you posted onto the forum I hope? Next to that we are indeed promoting IPv6, even though we don't make advertisements etc. But your issue is an IPv4 (read again, there is a 4 there, not a 6) issue and it has nothing to do with any of the networks that provides POPs to SixXS. It would be the same as a user in japan complaining that somewhere between tokio and los angeles a route is failing causing him not to be able to connect to SixXS website, unfortunatly we cannot do anything about those problems.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker