Can you log a fault? Sounds like packet loss issue. Will ask the techs on duty to escalate
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What's the most interesting small town you've visited in South Africa?
Web sQuad ISP - Feedback Thread #2
- Thread starter websquadza
- Start date
@websquadza Spotify issues are back :'(
Edit: I found a way around it for now at least, using a UK HTTP proxy from my VPN provider that's working well
Edit: I found a way around it for now at least, using a UK HTTP proxy from my VPN provider that's working well
Last edited:
You aren’t by any chance able to catch a source IP? I know a lot of ISPs moaned to Akamai; wonder if they’re not breaking things while troubleshooting.
CrypticZA
Expert Member
- Joined
- Sep 21, 2019
- Messages
- 4,626
- Reaction score
- 2,627
Spotify uses Akamai who serves Spotify traffic from 1) their own cache and 2) from Mweb's caches.
Some ISP's have asked Akamai is remove their ASN from resolving to Mweb cache which has solved this issue. I was part of the testing for this with some other Cool Ideas guys and whenever we connected to Mweb cache we would buffer like crazy, but when we connected to Akamai at Tereco we were perfect. Both Afrihost and CISP i know spoke to Akamai and all our traffic is now coming from them and not Mweb.
I tried, Spotify is a bloody mess of net traffic, to put it mildly.
I haven't actually seen any Akamai ranges at all.
When I'm not having issues, I only see Google Cloud ones.
Code:
172.217.170.129
151.101.62.248
151.101.62.250
34.149.154.214
142.251.47.98
192.178.54.34
35.186.224.18
104.199.65.124When I'm having issues I see a few Optinet IPs
Code:
197.80.130.67
197.80.130.80
197.80.130.155
197.80.130.120
Tinuva
The Magician
That is 197.80.xxx is mweb akamai caches.
Looks like Akamai are still serving content from the Optinet caches when it suits them. We've dropped Akamai's support team a follow up to the last mail where they said they would drop Optinet/Mweb as a source.
The culprit is definitely the Optinet/Mweb caches, but getting Akamai to actually permanently drop these as a source is proving to be difficult. We're on their case though.
Tinuva
The Magician
Also depends on the DNS server he is using.
eg.
Code:
root@stax:~# dig r-live-cache.akamaized.net @1.1.1.1
; <<>> DiG 9.16.42-Debian <<>> r-live-cache.akamaized.net @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40128
;; flags: qr rd ra; QUERY: 1, ANSWER: 10, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;r-live-cache.akamaized.net. IN A
;; ANSWER SECTION:
r-live-cache.akamaized.net. 341 IN CNAME a1075.dscw16.akamai.net.
a1075.dscw16.akamai.net. 18 IN A 197.80.130.160
a1075.dscw16.akamai.net. 18 IN A 197.80.130.24
a1075.dscw16.akamai.net. 18 IN A 197.80.130.64
a1075.dscw16.akamai.net. 18 IN A 197.80.130.18
a1075.dscw16.akamai.net. 18 IN A 197.80.130.25
a1075.dscw16.akamai.net. 18 IN A 197.80.130.16
a1075.dscw16.akamai.net. 18 IN A 197.80.130.19
a1075.dscw16.akamai.net. 18 IN A 197.80.130.17
a1075.dscw16.akamai.net. 18 IN A 197.80.130.65
;; Query time: 3 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Mon Oct 16 14:07:37 SAST 2023
;; MSG SIZE rcvd: 233
S7wede
Expert Member
- Joined
- Dec 23, 2007
- Messages
- 1,458
- Reaction score
- 208
Good day. I'm having a very weird issue where my routing is taking me to Europe via Hong Kong. Is there any reason why when I ping 185.60.112.158 it takes me all the way to China on hop 7?
Howdy, I see you're downstream of our network. Hop 7 is actually in Teraco Isando; however what you're seeing here is some network asymmetry and that the return path traffic for this downstream isn't coming in via our network. Forward traffic is outbound to us, but return is another route. Hop 7 is a PTP IP, so likely not routed locally for our partner upstream. Drop me a PM with your details and I'll reach out to your ISP's engineer quickly.
@websquadza everything be dead
Edit: Back up, that was a long outage. Did Parklands **** the bed again?
Edit: dead again, hopefully it's not another 30m
Edit: dead again
Edit: Back up, that was a long outage. Did Parklands **** the bed again?
Edit: dead again, hopefully it's not another 30m
Edit: dead again
Last edited:
Sorry for missing this. Have things stabilised? I’m not seeing any open NWIs; but happy to take a look
Long story short it's been 3 days since Linklayer said I could get websquad to setup my Internet (after tech5 completely dropped every ball) and I still don't have Internet access, router/ont traceroute cannot hit sites but falsely reports having an Internet connection. Asked for feedback yesterday, nothing. Asked for feedback today, nothing.
Being told to try turning a device off and connect another router were never going to solve this issue but I did them anyway. Logic has obviously left the building.
I feel some regret for not going with cool ideas because they have always been very good with initial setups...
Being told to try turning a device off and connect another router were never going to solve this issue but I did them anyway. Logic has obviously left the building.
I feel some regret for not going with cool ideas because they have always been very good with initial setups...
What is "but falsely reports having an Internet connection" ?
Drop me a PM with your details and ticket number; will take a look and see what’s happening
ONT Device shows the user it has Internet access but thiis is clearly wrong...
Attachments
You should be connecting via your router and not Ont. the Ont will have management internet access; but this won’t help you as a user as the ISP service is not linked. Please send your details and ticket number on a pm so I can escalate internally.
Thanks this has been fixed by Jason, smart guy there who noticed the routing after authentication wasn't correct.
I think you need to work on this though, it should not be necessary to post on mybroadband to get issues dealt with. I was even reluctant to post here because I assumed it was a big thing that might be on the FNO's side.
As outside was the only place I was getting cell signal, I got sunburnt, I spent time plugging in unnecessary devices, making phone calls, and even looking for workspaces or LTE alternates because come Monday I would need a stable connection to do my job. I'm happy it was solved but it seems like the ball was dropped and I hope someone learns something from this. So yeah I'm not exactly happy about this but it is sorted so thank you.
What routing as an issue? Generally this is all plug-and-play with the WAN port on the router getting an IP from the port on the ONT that's bridged to your ISP - and your router giving your devices an IP over DHCP and then routing between the 2 networks.
However, glad you sorted. We use Websquad for our office and never had difficulty. Always runs smoothly.
BouncyNinja
Executive Member
- Joined
- Oct 15, 2009
- Messages
- 5,225
- Reaction score
- 2,522
This looks like one of Vodacoms routers?? Make sure to disable remote management , if it is, and then burn it
