Mr Scratch
Expert Member
- Joined
- May 15, 2013
- Messages
- 4,872
- Reaction score
- 1,040
That's via Durban to East Africa.
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: Have you ever been to an airshow?
Web Squad ISP
- Thread starter Gazed416
- Start date
- Status
That's via Durban to East Africa.
Mr Scratch
Expert Member
- Joined
- May 15, 2013
- Messages
- 4,872
- Reaction score
- 1,040
Happening on Web Squad, Vox, CISP and MTN.
Yup. Djibouti to be specific. Guess HE added a new route or something.
Not HE related. Learning far fewer prefixes out of Cloudflare than usual.. probably some sort of network issue on their end.
Interesting. Correct me if I'm wrong, but v101.core2.bcn1.he.net is Barcelona no?
I think HE recycled an IP there and haven't updated the PTR... 1ms is JHB.
Only learning the larger Cloudflare prefixes on transit, so they've definitely pulled quite a bit from their SA routing table. That said, still seeing 150+ prefixes from them at the NAPs, which is about 50% of their table.
Or BCN is American for Johannesburg
Mr Scratch
Expert Member
- Joined
- May 15, 2013
- Messages
- 4,872
- Reaction score
- 1,040
Does Twitter not use a CDN in ZA?
Code:
Tracing route to twitter.com [104.244.42.193]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.0.1
2 4 ms 3 ms 3 ms as-vuma.jb-is-pld-x.za.ws.net.za [160.119.228.x]
3 12 ms 8 ms 22 ms core.vuma-l3.jb1.za.ws.net.za [160.119.224.97]
4 3 ms 3 ms 2 ms core.as-xe-02.jb1.za.ws.net.za [160.119.224.89]
5 3 ms 2 ms 3 ms core.cr-xe-01.jb1.za.ws.net.za [160.119.224.29]
6 3 ms 2 ms 2 ms core.pe-xe-ip01.jb1.za.ws.net.za [160.119.224.18]
7 3 ms 5 ms 2 ms v101.core2.bcn1.he.net [216.66.90.117]
8 160 ms 159 ms 160 ms 10ge2-11.core1.lon2.he.net [184.104.192.113]
9 161 ms 161 ms 160 ms 13414-ld8-ix.equinix.com [185.1.104.86]
10 161 ms 159 ms 160 ms 104.244.42.193
Trace complete.They're supposed to use Fastly CDN (Same as BBC and Twitch (for frontend)).. Looks like the main site is served up through international routes, but site content is still served via local CDNs (although from Edgecast and not Fastly).
abs.twimg.com and pbs.twimg.com are two sources I picked up on their main page, probably a few more.
@websquadza and idea when it will be resolved? I'm starting to run into a lot of issues with Token based 2FA
Edit: I know that you wouldn't know an exact time frame or answer, but a ballpark would be nice. Also, do they even know there is a problem?
Edit 2: Nevermind. My 2FA problem is solved
Edit: I know that you wouldn't know an exact time frame or answer, but a ballpark would be nice. Also, do they even know there is a problem?
Edit 2: Nevermind. My 2FA problem is solved
Last edited:
@websquadza and idea when it will be resolved? I'm starting to run into a lot of issues with Token based 2FA
Edit: I know that you wouldn't know an exact time frame or answer, but a ballpark would be nice. Also, do they even know there is a problem?
Edit 2: Nevermind. My 2FA problem is solved
Nothing we can do about Cloudflare and where they choose to advertise their prefixes- usually these changes on their side are either commercial (like their single thread limitations) or network (offload to less busy nodes) related. As I mentioned yesterday, peering is still up, just learning far fewer prefixes from them. Their NOC just replied with a fairly generic we’re on it answer. No ETA supplied though.
Send me more info about the 2FA issue if it rears it’s head again- might be able to prompt more action from their noc (they’re a lot more responsive than AWS).
Hi Carl, still no answer to the ticket. Again tonight I'm getting big lag on 41.78.188.225 and further downstream.
The question in my ticket is simple: is there something I can do to alleviate the bad line besides reporting it every other night?
This hasn't been an issue a month or two back.
Tonight for example it looks like this:
Code:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| dlinkrouter - 0 | 103 | 103 | 1 | 19 | 90 | 27 |
| as-vuma.cp-gwf-03.za.ws.net.za - 0 | 103 | 103 | 2 | 19 | 76 | 2 |
| core.as-01.cp1.za.ws.net.za - 0 | 103 | 103 | 1 | 16 | 78 | 25 |
| core.cr-01.cp1.za.ws.net.za - 0 | 103 | 103 | 1 | 17 | 75 | 1 |
| core.pe-xe-ip01.cp1.za.ws.net.za - 0 | 103 | 103 | 1 | 7 | 65 | 2 |
| 197.157.79.33 - 0 | 103 | 103 | 1 | 8 | 81 | 4 |
| No response from host - 100 | 103 | 0 | 0 | 0 | 0 | 0 |
| agr2-gwf-cr2-gi0-0-1.wolcomm.net - 0 | 103 | 103 | 1 | 10 | 87 | 3 |
| No response from host - 100 | 103 | 0 | 0 | 0 | 0 | 0 |
| 41.78.188.225 - 53 | 103 | 48 | 48571 | 49246 | 49692 | 49109 |
| agr1-lhx-cr1-te0-1-0.wolcomm.net - 0 | 103 | 103 | 146 | 153 | 201 | 156 |
|gi0-6-1-7.rcr21.b015533-1.lon01.atlas.cogentco.com - 3 | 103 | 100 | 160 | 207 | 268 | 189 |
| be2867.ccr22.lon01.atlas.cogentco.com - 4 | 103 | 99 | 156 | 201 | 258 | 188 |
| be2869.ccr42.lon13.atlas.cogentco.com - 5 | 103 | 98 | 156 | 205 | 247 | 188 |
| be2101.ccr32.bos01.atlas.cogentco.com - 4 | 103 | 98 | 222 | 260 | 332 | 266 |
| be3600.ccr22.alb02.atlas.cogentco.com - 6 | 103 | 96 | 229 | 275 | 312 | 271 |
| be2879.ccr22.cle04.atlas.cogentco.com - 3 | 103 | 99 | 242 | 284 | 318 | 288 |
| be2718.ccr42.ord01.atlas.cogentco.com - 5 | 102 | 97 | 243 | 285 | 323 | 288 |
| be2248.ccr22.ord03.atlas.cogentco.com - 2 | 102 | 100 | 242 | 287 | 338 | 280 |
|be2616.rcr21.b002281-5.ord03.atlas.cogentco.com - 2 | 102 | 100 | 249 | 292 | 358 | 299 |
| 169.254.0.0 - 9 | 102 | 93 | 239 | 259 | 287 | 251 |
| 10.255.18.171 - 7 | 102 | 95 | 238 | 252 | 298 | 262 |
| wotna3.login.wargaming.net - 2 | 102 | 99 | 238 | 260 | 293 | 268 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( [email protected] )This has been escalated to our current transit provider who have escalated it to Cogent. We haven’t received feedback today- I have just sent a follow up.
We’ll be bringing up a new transit provider in Cape Town tomorrow or Friday at latest which will provide a permanent fix.
Finally I’ll send you an update to your ticket now which may provide a temporary fix.
Can you check again? It looks like the Telia route is now preferred.
SpiderGear
Senior Member
IS there an issue with Cloudflare? Traffic is being routed to Djibouti..
mtr -w www.4x4community.co.za
Start: Fri Sep 20 13:30:38 2019
HOST: cacti.localdomain Loss% Snt Last Avg Best Wrst StDev
1.|-- FireFly.localdomain 0.0% 10 0.3 0.4 0.3 0.5 0.0
2.|-- as-vuma.jb-is-bry-01.za.ws.net.za 0.0% 10 3.6 6.4 2.4 26.8 7.4
3.|-- core.vuma-l3.jb1.za.ws.net.za 0.0% 10 6.8 7.0 3.8 11.6 2.4
4.|-- core.as-xe-02.jb1.za.ws.net.za 0.0% 10 1.7 1.8 1.6 1.8 0.0
5.|-- core.cr-xe-01.jb1.za.ws.net.za 0.0% 10 2.1 2.1 1.9 2.7 0.0
6.|-- core.pe-xe-ip01.jb1.za.ws.net.za 0.0% 10 2.1 2.2 1.9 2.8 0.0
7.|-- v101.core2.bcn1.he.net 0.0% 10 2.4 2.4 2.2 2.7 0.0
8.|-- e0-24.core1.dur1.he.net 0.0% 10 9.7 10.0 9.6 11.6 0.5
9.|-- 10ge0-48.core1.mba1.he.net 0.0% 10 56.4 56.4 56.1 57.2 0.0
10.|-- 10ge14-6.core1.jib1.he.net 0.0% 10 134.3 134.6 134.3 135.3 0.0
11.|-- cloudflare.v4.peers.djix.dj 0.0% 10 213.1 216.0 213.0 240.3 8.5
12.|-- 104.25.9.20 0.0% 10 213.6 213.8 212.9 219.3 1.9
mtr -w www.4x4community.co.za
Start: Fri Sep 20 13:30:38 2019
HOST: cacti.localdomain Loss% Snt Last Avg Best Wrst StDev
1.|-- FireFly.localdomain 0.0% 10 0.3 0.4 0.3 0.5 0.0
2.|-- as-vuma.jb-is-bry-01.za.ws.net.za 0.0% 10 3.6 6.4 2.4 26.8 7.4
3.|-- core.vuma-l3.jb1.za.ws.net.za 0.0% 10 6.8 7.0 3.8 11.6 2.4
4.|-- core.as-xe-02.jb1.za.ws.net.za 0.0% 10 1.7 1.8 1.6 1.8 0.0
5.|-- core.cr-xe-01.jb1.za.ws.net.za 0.0% 10 2.1 2.1 1.9 2.7 0.0
6.|-- core.pe-xe-ip01.jb1.za.ws.net.za 0.0% 10 2.1 2.2 1.9 2.8 0.0
7.|-- v101.core2.bcn1.he.net 0.0% 10 2.4 2.4 2.2 2.7 0.0
8.|-- e0-24.core1.dur1.he.net 0.0% 10 9.7 10.0 9.6 11.6 0.5
9.|-- 10ge0-48.core1.mba1.he.net 0.0% 10 56.4 56.4 56.1 57.2 0.0
10.|-- 10ge14-6.core1.jib1.he.net 0.0% 10 134.3 134.6 134.3 135.3 0.0
11.|-- cloudflare.v4.peers.djix.dj 0.0% 10 213.1 216.0 213.0 240.3 8.5
12.|-- 104.25.9.20 0.0% 10 213.6 213.8 212.9 219.3 1.9
MDE
Expert Member
Nothing here
No Issues... Addressed above. We're still peering and learning about 150-160 prefixes from them (you'll see this if you try 1.1.1.1). We usually learn more prefixes from them. It looks like Cloudflare are serving quite a few sites from random locations. Happened earlier this year when they served everything through Durban for a while.. Trend seems to be when they bring up a new node, everything is fed from there. Maybe it's them load balancing of sorts. We can't dictate where they advertise a prefix. For now, large chunks of their 104.16.0.0/12 prefix are missing from their SA advertisements at all peering points (JHB, CPT and KZN). Basically, they've decided (for some reason) that it's not worth handing over these IPs to any ISP directly in SA (which kind of defeats the purpose of a CDN).
@websquadza and idea when it will be resolved? I'm starting to run into a lot of issues with Token based 2FA
Edit: I know that you wouldn't know an exact time frame or answer, but a ballpark would be nice. Also, do they even know there is a problem?
Edit 2: Nevermind. My 2FA problem is solved
Nothing here
Update: We've received some additional Cloudflare feedback from a partner:
Cloudflare hasn't provided an ETA on resolving this issue, but are committed to getting SA CDNs back to capacity ASAP.
Hi guys, it's weekend and it appears new issues again, getting the below error when running Speedtest to Coreix London servers, also web pages take long to load which is bizarre (like a DNS delay). Speedtest download speeds look good locally and internationally and ping seems normal:
No issues here testing from a laptop over WiFi. Have you checked your Local network? For reference, test run now on Vumatel Trenched. https://www.speedtest.net/result/8607462842
- Status