person that stays in Springs?Springs'er?
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
person that stays in Springs?Springs'er?
Howdy@websquadza I don't like this L2TP tunnel for my static IP neh.
I had Claude help me diagnose it, and he says it's you guys
Some useful feedback from my end:
- Direct over Vuma I get about 1 Gbps down, through the tunnel about 290, and upload is 210 either way. (using fast.com)
- No router (as a reminder, MikroTik CCR1009-8G-1S-1S+) core went above about 37% during the tunneled test, and the tunnel work was spread across all of them.
- 1540-byte packets reach their tunnel server unfragmented, so the tunnel can carry full 1500-byte packets.
Seeing a drop off in speed when using the tunnel vs leaving it disabled, over NNTP too
what does https://redirector.googlevideo.com/report_mapping?di=no give you?Guys, Youtube/Google services are still a nightmare, 2 weeks now. Work fine on other ISPs
Unfortunately not on the cards at the moment. Not for lack of wanting. Rather, at the moment, we don't have the capacity to maintain a platform we don't really know enough about, reliably and consistently. There are a number of usenet providers with a local presence, and with the ability to support their platforms.Usenet server available yet?
Seeing super high latency on openserve - youtube is buffering as well which never happens
View attachment 1945154
View attachment 1945155
Apologies, only seeing these now. what ips were you monitoring here? we're investigating this a little further to see what happened@websquadza did something break in JHB? Looks like everything is being routed via CPT
We picked up an upstream transit issue, which we've escalated with the vendor. We've dropped them since this morning. Please confirm if things are looking better.Im getting really bad packet loss over night when using battlenet, Here is the IP and stats below.
Request timed out.
Reply from 37.244.28.101: bytes=32 time=222ms TTL=47
Request timed out.
Ping statistics for 37.244.28.101:
Packets: Sent = 106, Received = 93, Lost = 13 (12% loss),
Approximate round trip times in milli-seconds:
Minimum = 222ms, Maximum = 229ms, Average = 222ms
Basically cannot use it like this.
Same server when connected to my VPN on Neotels network is flawless.
Reply from 37.244.28.101: bytes=32 time=183ms TTL=51
Reply from 37.244.28.101: bytes=32 time=182ms TTL=51
Ping statistics for 37.244.28.101:
Packets: Sent = 111, Received = 111, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 181ms, Maximum = 336ms, Average = 210ms
Yes i know its probably taking a different route etc but i dont want to have to connect to a VPN to make something work that should just be working normally. Please advise.
Standard 8.8.8.8 and 1.1.1.1. But saw this across the connectionApologies, only seeing these now. what ips were you monitoring here? we're investigating this a little further to see what happened
thanks for confirming, you didn't happen to catch an MTR at the time of the incident?Standard 8.8.8.8 and 1.1.1.1. But saw this across the connection
Got a bit more latency but no more packet loss.We picked up an upstream transit issue, which we've escalated with the vendor. We've dropped them since this morning. Please confirm if things are looking better.
What region are you in? testing from JHB, I'm seeing 163ms to 37.244.28.101, which is the highest we should see. Do you have an MTR?Got a bit more latency but no more packet loss.
Ping statistics for 37.244.28.101:
Packets: Sent = 107, Received = 107, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 226ms, Maximum = 368ms, Average = 326ms
thanks for confirming, you didn't happen to catch an MTR at the time of the incident?
can you drop me a pm with your account, need to see what IP you're assigned, so we can investigate your prefix.Im JHB based,
Tracert below. Thanx
Tracing route to 37.244.28.101 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 2 ms 2 ms 2 ms 100.101.230.2
3 2 ms 2 ms 2 ms 100.99.198.5
4 3 ms 3 ms 2 ms 160.119.224.6
5 3 ms 2 ms 2 ms 160.119.224.3
6 3 ms 3 ms 2 ms 160.119.224.54
7 18 ms 18 ms 18 ms 160.119.232.183
8 19 ms 19 ms 19 ms 63-222-113-24.static.as3491.net [63.222.113.24]
9 357 ms 353 ms 294 ms Hun0-0-0-1.br01.ldn01.as3491.net [63.218.12.46]
10 158 ms 159 ms 158 ms ae19.edge17.lon1.sp.lumen.tech [4.68.110.41]
11 337 ms 349 ms 341 ms ae2.3204.edge7.ams1.neo.colt.net [171.75.9.210]
12 274 ms 298 ms 310 ms blizzard-en.edge7.amsterdam1.level3.net [212.72.41.90]
13 220 ms 217 ms 220 ms ae2-br04-eqam3.as57976.net [137.221.78.182]
14 330 ms 342 ms 325 ms et-0-0-1-br02-eqam3.as57976.net [137.221.65.176]
15 164 ms 164 ms 164 ms et-0-0-1-pe04-eqam3.as57976.net [137.221.78.69]
16 280 ms 277 ms 310 ms ams-eqam3-ia-bons-04.as57976.net [137.221.66.47]
17 * * * Request timed out.
18 326 ms 321 ms 313 ms 37.244.28.101
If you can also pm me your public IP, I want to see what could be causing this for youUnfortunately not. Google and Quad9 are still high but Cloudflare seems to face resolved to the norm