Web sQuad ISP - Feedback Thread #2

What DNS you using? Can you also provide an MTR?
Sorry, was distracted looking at coffee machines.
I'm using AdGuard with Google and Cloudflare as downstream, parallel requests.
It seems the DNS is resolving, but on a traceroute its dying after hop 3.
I'm downloading winmtr now.

Tracing route to onlinecoffeeshop.co.za [172.67.156.222]
over a maximum of 30 hops:

1 9 ms 1 ms 7 ms 192.168.3.1
2 90 ms 8 ms 8 ms core.bng-xe-02.jb1.za.wecom.net.za [160.119.230.1]
3 6 ms 9 ms 5 ms 160.119.224.92
4 * * * Request timed out.
5 * * * Request timed out.

(goes up to 16 hops all the same as 4 and 5)
 
Sorry, was distracted looking at coffee machines.
I'm using AdGuard with Google and Cloudflare as downstream, parallel requests.
It seems the DNS is resolving, but on a traceroute its dying after hop 3.
I'm downloading winmtr now.

Tracing route to onlinecoffeeshop.co.za [172.67.156.222]
over a maximum of 30 hops:

1 9 ms 1 ms 7 ms 192.168.3.1
2 90 ms 8 ms 8 ms core.bng-xe-02.jb1.za.wecom.net.za [160.119.230.1]
3 6 ms 9 ms 5 ms 160.119.224.92
4 * * * Request timed out.
5 * * * Request timed out.

(goes up to 16 hops all the same as 4 and 5)

WinMTR:

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.3.1 -    0 |  144 |  144 |    0 |    0 |    1 |    0 |
|      core.bng-xe-02.jb1.za.wecom.net.za -    0 |  144 |  144 |    2 |    2 |    3 |    2 |
|                          160.119.224.92 -    1 |  140 |  139 |    2 |    2 |    6 |    2 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   28 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
Sorry, was distracted looking at coffee machines.
I'm using AdGuard with Google and Cloudflare as downstream, parallel requests.
It seems the DNS is resolving, but on a traceroute its dying after hop 3.
I'm downloading winmtr now.

Tracing route to onlinecoffeeshop.co.za [172.67.156.222]
over a maximum of 30 hops:

1 9 ms 1 ms 7 ms 192.168.3.1
2 90 ms 8 ms 8 ms core.bng-xe-02.jb1.za.wecom.net.za [160.119.230.1]
3 6 ms 9 ms 5 ms 160.119.224.92
4 * * * Request timed out.
5 * * * Request timed out.

(goes up to 16 hops all the same as 4 and 5)
You don't happen to be able to get a reverse trace here?
 
You don't happen to be able to get a reverse trace here?
No... not sure how to do that on Windows... ping -a didn't do it, but maybe this will help...

On WebSquad:
Code:
C:\Users\justi>nslookup onlinecoffeeshop.co.za
Server:  MikroTik
Address:  172.17.0.2

Non-authoritative answer:
Name:    onlinecoffeeshop.co.za
Addresses:  2606:4700:3035::6815:db2
          2606:4700:3030::ac43:9cde
          172.67.156.222
          104.21.13.178
          
C:\Users\justi>ping 104.21.13.178

Pinging 104.21.13.178 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

On Vodacom:
Code:
C:\Users\justi>nslookup onlinecoffeeshop.co.za
Server:  hh72.home
Address:  fe80::ca2a:f1ff:fe1e:7fd3

Non-authoritative answer:
Name:    onlinecoffeeshop.co.za
Addresses:  2606:4700:3030::ac43:9cde
          2606:4700:3035::6815:db2
          172.67.156.222
          104.21.13.178
          
C:\Users\justi>ping 104.21.13.178

Pinging 104.21.13.178 with 32 bytes of data:
Reply from 104.21.13.178: bytes=32 time=46ms TTL=48
Reply from 104.21.13.178: bytes=32 time=125ms TTL=48
Reply from 104.21.13.178: bytes=32 time=145ms TTL=48
Reply from 104.21.13.178: bytes=32 time=156ms TTL=48
 
Just started working! Thanks.
Same here. Up and running.
Thanks for the update, we managed to track down a stale route, on one edge that was, by all appearances, perfectly operational (one of our first checks was to ensure that the prefix you're all on was actually visible throughout the network and on all our edge devices). Combined with a number of unrelated issues (cloudflare dropping prefixes, multiple FNO outages etc), it's been a bit of a tough search. We are investigating a little deeper to see how this would have happened.
 
Thanks for the update, we managed to track down a stale route, on one edge that was, by all appearances, perfectly operational (one of our first checks was to ensure that the prefix you're all on was actually visible throughout the network and on all our edge devices). Combined with a number of unrelated issues (cloudflare dropping prefixes, multiple FNO outages etc), it's been a bit of a tough search. We are investigating a little deeper to see how this would have happened.
Its interesting that this hasn't solved my onlinecoffeeshop.co.za issue... everything else seems ok (not that i've done extensive testing) but I can still only access this site while on my backup connections.

Edit: nevermind... its suddenly started working!
 
Its interesting that this hasn't solved my onlinecoffeeshop.co.za issue... everything else seems ok (not that i've done extensive testing) but I can still only access this site while on my backup connections.

Edit: nevermind... its suddenly started working!
that site works my side... for what it's worth
 
Just a heads up for tomorrow morning (Vuma Change Control):
Change Reference:#11588
Start Date:13 September 2023 @ 02h00
End Date:13 September 2023 @ 06h00
Area/s Affected:Affected sites:
  • Amarosa
  • Roodekrans
Change Grade:Major
Network Type Affected:GPON (Core)
Change Description:DWDM implementation Phase 2
Change Impact:Residents will experience no connectivity during this time
 
Still nothing that can be done to improve Apple services? It’s fairly quick on Liquid (at the office). Was a joke trying to stream the launch last night.
 
@websquadza Please can you provide an update? It's been almost 2 days since you said you'd have an update.

I appreciate the help, but I'm literally just waiting for your feedback before I pull the trigger on a new LTE contract. MTN Afrihost is dead half the time (agent insisted the issue is the placement of my router even though I've erected an outdoor antenna) and prepaid LTE is chowing my moolah.
 
Also noticed my traffic to Cloudflare's 1.1.1.1 & 1.0.0.1 is going up to JHB?

While my neighbour on Vox is still going to the CPT data center?
 
@websquadza Please can you provide an update? It's been almost 2 days since you said you'd have an update.

I appreciate the help, but I'm literally just waiting for your feedback before I pull the trigger on a new LTE contract. MTN Afrihost is dead half the time (agent insisted the issue is the placement of my router even though I've erected an outdoor antenna) and prepaid LTE is chowing my moolah.
Thanks for your patience here. The beast that is Openserve moves slowly, and we've also reached out to another network to see if they can assist. I understand you want to pull the trigger on a solution, so I will ensure we get you some feedback asap.
 
Thanks for your patience here. The beast that is Openserve moves slowly, and we've also reached out to another network to see if they can assist. I understand you want to pull the trigger on a solution, so I will ensure we get you some feedback asap.
Thanks a lot, much appreciated.

Will installing a different FNO affect Openserve's likelihood of being willing to install?

If that's the case and the other FNO is Frogfoot then I'd rather wait it out for a few months with an LTE contract while waiting for Openserve to install. Frogfoot is notoriously unreliable on my neighborhood group with regular outages. At my previous accomodation in the same area I had Openserve for many years and it was rock solid even during extended power outages of a few days.
 
Top
Sign up to the MyBroadband newsletter
X