On 5/22/24 14:44, Paul Rolland wrote:
Yep, it hurts :(
1. Gi0-3.rtr-01.PAR.witbe.net 0.0% 179 0.3 0.3 0.2 10.4 0.7
2. 193.251.248.21 0.0% 179 3.3 1.3 0.8 19.1 2.1
3. bundle-ether305.partr2.saint-den 6.7% 179 87.1 4.5 1.1 156.7 17.4
4. prs-b1-link.ip.twelve99.net 22.3% 179 9.9 10.4 9.6 48.3 4.4
5. prs-bb2-link.ip.twelve99.net 2.2% 179 10.4 10.3 9.8 27.3 1.3
6. mei-b5-link.ip.twelve99.net 1.1% 178 17.3 18.1 17.2 115.1 7.4
7. prs-bb1-link.ip.twelve99.net 27.5% 178 370.6 365.9 334.7 381.8 8.3
8. ldn-bb1-link.ip.twelve99.net 68.5% 178 366.8 363.0 340.8 379.2 8.3
9. nyk-bb2-link.ip.twelve99.net 11.8% 178 377.6 362.4 322.2 451.0 12.3
10. palo-b24-link.ip.twelve99.net 50.8% 178 359.1 364.1 342.8 397.1 8.6
11. port-b3-link.ip.twelve99.net 0.0% 178 177.4 178.0 177.1 188.6 1.9
12. tky-b3-link.ip.twelve99.net 75.7% 178 355.2 364.0 339.8 377.5 8.0
13. tky-b2-link.ip.twelve99.net 50.0% 178 338.7 350.5 321.8 370.9 11.1
14. sng-b7-link.ip.twelve99.net 87.6% 178 307.8 318.6 306.8 332.0 6.7
15. sng-b5-link.ip.twelve99.net 86.4% 178 314.4 315.3 293.6 330.1 10.2
16. epsilon-ic-382489.ip.twelve99-cu 55.7% 177 364.8 362.9 346.5 391.8 9.1
17. 180.178.74.221 59.9% 177 357.6 366.9 343.4 562.7 25.8
18. swi-01-sin.noc.witbe.net 62.9% 176 374.7 366.4 346.6 381.3 8.3
1299 is now routing Paris to Singapore via US and Pacific...
The good news is that the Yemeni government have approved repairs for
EIG and SEACOM. The bad news is that those approvals don't yet extend to
AAE-1, whose cut is the one causing you that pain.
It's unclear when, or if, Yemen will give permission to repair AAE-1.
The market is speculating mid-June, but there is no hard data to support
that.
Not sure if transition 6 to 7 is what was expected, with a 350ms increase...
Well, on Arelion's network, PAO-SIN = 260ms:
Tracing the route to 180.178.74.221
1 sjo-b23-link.ip.twelve99.net (62.115.115.217) 2 msec 2 msec 2 msec
2 *
tky-b2-link.ip.twelve99.net (62.115.123.141) 187 msec 162 msec
3 * * *
4 * *
62.115.115.62 251 msec
5 *
hnk-b3-link.ip.twelve99.net (62.115.143.241) 257 msec *
6 sng-b4-link.ip.twelve99.net (62.115.116.146) 280 msec * 222 msec
7 * * *
8 * * *
9 180.178.74.221 265 msec 262 msec *
For the moment, it looks like you've switched to Zayo for transit in
Paris, so unclear what Arelion's on network would do PAO-CDG:
Tracing the route to 81.88.96.250
1 sjo-b23-link.ip.twelve99.net (62.115.115.217) 2 msec 2 msec 2 msec
2 ae71.zayo.ter1.sjc7.us.zip.zayo.com (64.125.15.150) 2 msec * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 ae1.mcs1.cdg12.fr.eth.zayo.com (64.125.29.87) 148 msec * 158 msec
10 v3.ae10.ter3.eqx2.par.as8218.eu (64.125.30.183) 150 msec 151 msec
151 msec
11 ae6.ter4.eqx2.par.core.as8218.eu (83.167.55.43) 151 msec 152 msec
152 msec
12 ae0.ter3.itx5.par.core.as8218.eu (83.167.55.10) 148 msec 148 msec
148 msec
13 witbe-gw1.ter1.itx5.par.cust.as8218.eu (158.255.117.19) 151 msec
153 msec 153 msec
14 Gi0-3.rtr-01.PAR.witbe.net (81.88.96.250) 152 msec * 151 msec
HE did/does that too, prefering to avoid any direct route from EU to Asia.
Well, right now, of the modern cables that had capacity and reasonable
pricing, only SMW-5 remains up... and SMW-5 is just about out of
capacity as well.
SMW-6 is currently under construction, so that is not yet an option (the
Red Sea debacle notwithstanding).
Subsea systems that need to cross the Middle East and Egypt to connect
Europe and Africa to South (East) Asia are generally problematic because
of the complexities of having to deal with Egypt, and now, the Red Sea.
That translates into capacity availability (or lack thereof in times
like these) and cost. This creates an incentive for operators to route
South (East) Asia through the U.S. to get to Europe, until the situation
resolves itself, or new cables with new/cheaper capacity pop up.
Mark.
