New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
They do, sort of, if you have a transit session. Not very useful as you cannot manipulate Asian traffic but better than nothing.
As for Amazon, i guess it does not matter for your service, they will shortly backhaul to other locations if the route is better - much like Softlayer does. Interconnects are already online for VPC peering, just not for external transit.
I would not bother much with South America, it is a nightmare - everyone runes their own cables and the land cables are generally pretty bad. There is a reason this is GLBX/Telecom Italias biggest market... way far from their homes.
@William we do quite well in South America actually, and FL-IX costs us nothing. The big thing we see in SA is route fluctuations (during peak, every minute) between multiple PoPs for the same connection. Two of the ISPs that are particularly bad are on FL-IX.
And yes we do have PCCW but as their communities are useless for us we don't announce with them. If I could, I would restrict routes to Asia, and export only to peers. No helping it.
That is overloading and you see that a lot on the Telmex backbone - The cables are pretty old and do not have much capacity compared to submarine fiber.
It does not help either that being Spanish speaking a LOT of traffic ends up on similar endpoints/US, Brazil can be better at times. Central Panama is the exception but also only due to existing datacenter infrastructure, sort of open market and multiple cables on each side.
FL-IX makes sense, yea, but it does not mean they will peer with you - Telmex just like DTAG is on a lot of exchanges, but with private peering only.
ISP Cox from San Diego
Target Name: lg.x4b.net
IP: 103.77.224.2
Date/Time: 5/18/2017 6:47:01 AM
1 2 ms 7 ms [192.168.0.1]
2 11 ms 15 ms [10.151.120.1]
3 20 ms 13 ms [68.6.14.0]
4 12 ms 13 ms elcnsysc01-tec-141.sd.sd.cox.net [68.6.8.58]
5 141 ms 19 ms ae55.bar2.SanDiego1.Level3.net [4.16.106.5]
6 129 ms 27 ms ae-0-11.bar1.SanDiego1.Level3.net [4.69.146.65]
7 * 19 ms ae-3-3.ebr1.LosAngeles1.Level3.net [4.69.140.102]
8 * * [-]
9 31 ms 35 ms Telia-level3-60G.LosAngeles1.Level3.net [4.68.73.22]
10 76 ms 28 ms las-b22-link.telia.net [62.115.140.255]
11 44 ms 22 ms ae9.telia.lax.us.AS40676.net [23.238.223.13]
12 * * [-]
13 28 ms 20 ms node-103-77-224-2.reverse.x4b.me [103.77.224.2]
@William very interesting. You look to know your shit.
I'll settle for FL-IX for now providing my peer can get their router configured correctly so I can AS0 away.
Well, yea, Rage4/Opennic/My anycast/Spanish learning/Spanish friends/Coworkers in Argentina... it is nightmare down there for routing and BW pricing.
From CA, USA
traceroute to lg.x4b.net (103.77.224.2), 30 hops max, 60 byte packets 1 vps97.he.hostfav.com (x.x.x.x) 0.952 ms 0.960 ms 0.988 ms 2 v1626.core3.fmt2.he.net (x.x.x.x) 7.800 ms 7.839 ms 7.873 ms 3 10ge7-9.core1.sjc2.he.net (184.105.222.14) 6.661 ms 6.336 ms * 4 sjo-b21-link.telia.net (213.248.67.105) 2.300 ms 2.354 ms 2.390 ms 5 las-b21-link.telia.net (62.115.125.142) 9.496 ms palo-b22-link.telia.net (62.115.125.10) 2.551 ms palo-b22-link.telia.net (62.115.143.120) 2.440 ms 6 las-b22-link.telia.net (62.115.125.199) 13.392 ms las-b22-link.telia.net (62.115.125.205) 12.318 ms las-b22-link.telia.net (62.115.119.99) 13.325 ms 7 ae9.telia.lax.us.AS40676.net (23.238.223.13) 12.699 ms 12.757 ms 12.670 ms 8 * * * 9 node-103-77-224-2.reverse.x4b.me (103.77.224.2) 13.567 ms 13.600 ms 13.579 ms@SplitIce NL-2 was requested from BSNL india
Now the routes goes like this
Hamburg, Germany
Here's a few more...
OVH BHS
Colocrossing, Chicago
Input Output Flood, Phoenix
Traceroute from Keminet, Albania:
traceroute to lg.x4b.net (103.77.224.2), 30 hops max, 60 byte packets 1 * * * 2 80.78.69.229 (80.78.69.229) 1.645 ms 1.774 ms 1.588 ms 3 pg-bar.p.cg.yu (195.66.161.33) 4.131 ms 4.011 ms 3.969 ms 4 195.29.240.29 (195.29.240.29) 49.919 ms hdr11-gdr02-3.ip.t-com.hr (195.29.241.129) 15.908 ms 195.29.240.29 (195.29.240.29) 49.872 ms 5 gtr11-gdr11.ip.t-com.hr (195.29.110.222) 17.011 ms gtr11-gdr11-2.ip.t-com.hr (195.29.240.62) 17.616 ms 17.600 ms 6 te0-1-0-6.rcr21.zag01.atlas.cogentco.com (149.6.30.153) 18.504 ms te0-1-1-6.rcr21.zag01.atlas.cogentco.com (149.6.30.161) 19.615 ms te0-7-0-7.rcr21.zag01.atlas.cogentco.com (149.6.30.17) 19.007 ms 7 be2594.ccr21.vie01.atlas.cogentco.com (130.117.3.169) 27.122 ms 26.980 ms 26.844 ms 8 telia.vie01.atlas.cogentco.com (130.117.14.90) 40.623 ms 40.840 ms 40.871 ms 9 win-bb2-link.telia.net (213.155.132.128) 45.029 ms win-bb2-link.telia.net (62.115.136.236) 44.974 ms win-bb2-link.telia.net (62.115.112.208) 45.078 ms 10 hbg-bb4-link.telia.net (213.155.132.238) 49.392 ms hbg-bb1-link.telia.net (62.115.133.143) 54.415 ms hbg-bb4-link.telia.net (62.115.139.233) 48.748 ms 11 adm-bb4-link.telia.net (80.91.248.240) 53.297 ms adm-bb4-link.telia.net (80.91.246.200) 53.609 ms adm-bb4-link.telia.net (213.155.136.150) 53.146 ms 12 adm-b2-link.telia.net (213.155.137.195) 53.893 ms adm-b2-link.telia.net (62.115.141.9) 53.948 ms adm-b2-link.telia.net (62.115.141.3) 53.439 ms 13 psychz-ic-322887-adm-b2.c.telia.net (213.248.66.57) 51.197 ms 50.856 ms 50.942 ms 14 edge-gs-ams.as40676.net (104.216.181.18) 51.320 ms 53.572 ms 50.840 ms 15 node-103-77-224-2.reverse.x4b.me (103.77.224.2) 51.437 ms 50.861 ms 52.117 msThis is from a dedicated server located in Istanbul, Turkey
The second one is from a residential connection in Istanbul, Turkey
Traceroute from Hamilton Ontario Canada - ISP: Rogers Communications
FROM Level3; CL
OVH Warsaw
From Orange Jordan
From Eastern Washington, a university network. (Washington State K-20 Telecommunications Network)
|------------------------------------------------------------------------------------------| | WinMTR statistics | | Host - % | Sent | Recv | Best | Avrg | Wrst | Last | |------------------------------------------------|------|------|------|------|------|------| | 10.102.2.1 - 0 | 10 | 10 | 0 | 0 | 1 | 0 | | 192.168.250.1 - 0 | 10 | 10 | 0 | 0 | 0 | 0 | | 146.187.0.2 - 0 | 10 | 10 | 0 | 0 | 0 | 0 | | te0-0-24.ewu-bacc.infra.wa-k20.net - 0 | 10 | 10 | 1 | 1 | 1 | 1 | | No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | ae9--311.seawescore1.infra.wa-k20.net - 0 | 10 | 10 | 8 | 8 | 9 | 9 | |ae0--311.icar-sttl1-1.infra.pnw-gigapop.net - 0 | 10 | 10 | 8 | 8 | 9 | 8 | |ae-0.university-of-washington-pacific-northwest-gigapop.sttlwa01.us.bb.gin.ntt.net - 0 | 10 | 10 | 8 | 8 | 9 | 8 | | ae-35.r05.sttlwa01.us.bb.gin.ntt.net - 0 | 10 | 10 | 9 | 9 | 10 | 9 | | ae-1.r04.sttlwa01.us.bb.gin.ntt.net - 0 | 10 | 10 | 8 | 8 | 9 | 8 | | ae3.cr2-sea2.ip4.gtt.net - 0 | 10 | 10 | 8 | 10 | 31 | 8 | | et-3-3-0.cr2-lax2.ip4.gtt.net - 0 | 10 | 10 | 35 | 35 | 36 | 35 | | et-1-1-1.tinet.lax.us.as40676.net - 0 | 10 | 10 | 35 | 36 | 41 | 36 | | No response from host - 100 | 2 | 0 | 0 | 0 | 0 | 0 | | node-103-77-224-2.reverse.x4b.me - 0 | 10 | 10 | 34 | 34 | 35 | 35 | |________________________________________________|______|______|______|______|______|______| WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud ProviderAnd from our datacenter in Seattle:
From Zen, UK:
I assume you already have OVH so I won't bother with those
EDIT: I pm'd you like 10-15 traceroutes
Telia's communities suck. Message me on Skype if you need help with route optimization
level 3 ar..
traceroute Protocol [ip]: ip Target IP address: 103.77.224.2 Source address: Numeric display [n]: n Timeout in seconds [3]: 1 Probe count [3]: 2 Minimum Time to Live [1]: 1 Maximum Time to Live [30]: 30 Port Number [33434]: Loose, Strict, Record, Timestamp, Verbose[none]: Type escape sequence to abort. Tracing the route to node-103-77-224-2.reverse.x4b.me (103.77.224.2) VRF info: (vrf in name/id, vrf out name/id) 1 ae1-300G.ar5.MIA1.gblx.net (67.17.94.249) 128 msec 124 msec 2 * * 3 * * 4 mai-b1-link.telia.net (213.248.84.80) [AS 1299] 144 msec 148 msec 5 vultr-ic-318945-mai-b1.c.telia.net (62.115.151.5) [AS 1299] 196 msec * 6 * as20473-gw.mia12.ip4.gtt.net (173.205.61.214) [AS 3257] 312 msec 7 vl803-ds1-j2-r108.mia1.choopa.net (104.156.242.202) [AS 20473] 140 msec 144 msec 8 * * 9 * * 10 * * 11 * * 12 * * 13 * * 14 * * 15 * * 16 * * 17 * * 18 * * 19 * *From Panama City, Panama:
traceroute to lg.x4b.net (103.77.224.2), 64 hops max, 52 byte packets 1 192.168.2.2 (192.168.2.2) 1.186 ms 0.983 ms 0.895 ms 2 * * * 3 10.48.42.105 (10.48.42.105) 40.203 ms 55.914 ms 17.150 ms 4 10.48.42.149 (10.48.42.149) 12.907 ms 22.108 ms 14.295 ms 5 xe-5-1-5.0-brx-teracore02.cwc.com (63.245.3.97) 67.144 ms 63.245.70.65 (63.245.70.65) 53.399 ms 60.325 ms 6 xe-1-0-0.usa.miami.fl.us.nam-core01.cwc.com (63.245.5.64) 55.878 ms xe-1-1-0.0-boca-raton.fl.us.brx-teracore01.cwc.com (63.245.5.138) 60.831 ms xe-8-2-1.cr2-mia1.ip4.gtt.net (216.221.158.125) 66.943 ms 7 as20473-gw.mia12.ip4.gtt.net (173.205.61.214) 57.466 ms 59.864 ms 62.384 ms 8 vl803-ds1-j2-r108.mia1.choopa.net (104.156.242.202) 83.210 ms 73.243 ms 117.475 ms 9 * vultr-ic-318945-mai-b1.c.telia.net (62.115.151.5) 64.747 ms 54.773 ms 10 vl803-ds1-j2-r108.mia1.choopa.net (104.156.242.202) 80.563 ms 75.561 ms node-103-77-224-2.reverse.x4b.me (103.77.224.2) 58.370 msDifferent ISP, same city:
Tracing route to lg.x4b.net [103.77.224.2] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 * * * Request timed out. 3 3 ms 2 ms 2 ms 200.90.140.197 4 2 ms 2 ms 2 ms 64.214.150.197 5 48 ms 70 ms 48 ms ae0-300G.ar5.MIA1.gblx.net [67.17.99.233] 6 * * * Request timed out. 7 * * * Request timed out. 8 55 ms 53 ms 55 ms mai-b1-link.telia.net [213.248.84.80] 9 49 ms 49 ms 49 ms vultr-ic-318945-mai-b1.c.telia.net [62.115.151.5] 10 63 ms 66 ms 71 ms vl803-ds1-j2-r108.mia1.choopa.net [104.156.242.202] 11 * * * Request timed out. 12 49 ms 49 ms 49 ms node-103-77-224-2.reverse.x4b.me [103.77.224.2]Time4VPS
My ISP (AS47524) has something weird going inside but I'm not sure what.
They seem to force your traffic outbound over Tata while not using them inbound at all - That is TTNet and Tellcom... weird, but not TOO unusual.
Is your external IP one of the ranges listed there?
http://bgp.he.net/AS47524#_prefixes
The internal hops are typical for 4G over long distance to a central core and similar, useless and weird with no hostnames set but yea. If you use other DNS you might want to trace with the ISPs DNS enabled, they might resolve PTR for these.
telecentro
From a crappy Virgin Media connection:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.3.1 - 0 | 17 | 17 | 0 | 0 | 2 | 0 |
| 192.168.0.1 - 0 | 17 | 17 | 2 | 4 | 19 | 2 |
| 10.216.68.1 - 8 | 13 | 12 | 8 | 14 | 28 | 19 |
|leed-core-2a-xe-003-0.network.virginmedia.net - 8 | 13 | 12 | 11 | 16 | 30 | 22 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| brnt-ic-1-ae0-0.network.virginmedia.net - 0 | 17 | 17 | 19 | 39 | 89 | 19 |
| m686-mp2.cvx1-b.lis.dial.ntli.net - 0 | 17 | 17 | 17 | 26 | 67 | 17 |
| 213.46.174.118 - 8 | 13 | 12 | 18 | 24 | 36 | 23 |
| ldn-bb3-link.telia.net - 8 | 13 | 12 | 17 | 25 | 37 | 26 |
| ldn-b1-link.telia.net - 8 | 13 | 12 | 17 | 24 | 37 | 26 |
| psychz-ic-322891-ldn-b1.c.telia.net - 8 | 13 | 12 | 19 | 26 | 43 | 26 |
| edge-gs-lon.as40676.net - 8 | 13 | 12 | 23 | 26 | 36 | 26 |
| node-103-77-224-2.reverse.x4b.me - 0 | 17 | 17 | 18 | 27 | 68 | 18 |
|________________________________________________|______|______|______|______|______|______|
Kinda broken traceroute from Germany (Telefonica O2 ADSL)
5 ae10-0.0001.corx.01.dus.de.net.telefonica.de (62.53.10.83) 8.711 ms ae10-0.0001.corx.02.dus.de.net.telefonica.de (62.53.11.128) 8.181 ms ae10-0.0001.corx.01.dus.de.net.telefonica.de (62.53.10.83) 8.432 ms 6 ae21-0.0001.dbrx.02.dus.de.net.telefonica.de (62.53.0.27) 8.540 ms ae20-0.0001.dbrx.02.dus.de.net.telefonica.de (62.53.0.11) 12.434 ms ae21-0.0001.dbrx.02.dus.de.net.telefonica.de (62.53.0.27) 8.678 ms 7 ae4-0.0002.prrx.02.dus.de.net.telefonica.de (62.53.0.206) 7.629 ms 8.076 ms ae3-0.0002.prrx.02.dus.de.net.telefonica.de (62.53.0.204) 7.817 ms 8 ae4.gradusix2.net.telefonicaglobalsolutions.com (213.140.51.60) 8.262 ms 8.301 ms 8.059 ms 9 94.142.99.213 (94.142.99.213) 20.121 ms 132.988 ms 149.768 ms 10 tinet-ae8-0-grtpareq2.net.telefonicaglobalsolutions.com (213.140.52.178) 159.866 ms 180.902 ms 194.895 ms 11 xe-8-3-0.cr0-lon1.ip4.gtt.net (89.149.183.178) 242.629 ms xe-8-2-5.cr0-lon1.ip4.gtt.net (89.149.133.90) 355.214 ms xe-8-3-0.cr0-lon1.ip4.gtt.net (89.149.183.178) 335.061 ms 12 77.67.124.46 (77.67.124.46) 408.545 ms 402.789 ms 511.782 ms 13 * * edge-gs-lon.as40676.net (104.216.182.18) 440.772 ms 14 node-103-77-224-2.reverse.x4b.me (103.77.224.2) 413.241 ms 424.967 ms 307.141 ms@vpsGOD strange you actually have a better connection to NL. Most of India has better connections to UK. Reverted. Thanks.
@salakis agreed, that is broken. Could you take a look now?
here u go
traceroute to lg.x4b.net (103.77.224.2), 30 hops max, 60 byte packets 1 * * * 2 * * * 3 profuse-solutions.as40676.any2ix.coresite.com (206.72.211.46) 0.525 ms 0.517 ms 0.501 ms 4 * * * 5 node-103-77-224-2.reverse.x4b.me (103.77.224.2) 0.859 ms 0.846 ms 0.854 msThat contains literally no useful information...