Just received this email:
View attachment 1852453
I blocked that email account as it's compromised. Thanks for reporting it.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Just received this email:
View attachment 1852453
View attachment 1852509
Seems to have settled. I checked Afrihosts status. Nothing posted.
Good day,No internet in Umtentweni KZN.
@Afrigirl
@Frogfoot Fibre
All lights green.
We need to work please.
Edit: Whole area down Seapark down Hibberdene down @Frogfoot Fibre throughout all ISP's.
@Afrigirl @AfriNatic
Hi, I am having intermittent issues with Microsoft services hosted on their Azure Front Door CDN (msedge) service over IPv6. This issue has been happening for a few days now, both on the new BNGs and old BNGs. I've rebooted both my ONT and my router. I'm using Afrihost's DNS servers. This issue persisted on both the new and old BNGs, across different IPv6 prefixes. It seems to work fine over IPv4.
Some of the services affected over IPv6:
These all resolve down to s-part-0028.t-0009.t-msedge.net with IPv6 address 2620:1ec:bdf::56
- code.visualstudio.com (Visual Studio Code can't update, and can't load code.visualstudio.com in a normal web browser or via cURL)
- wcpstatic.microsoft.com (microsoft.com, minecraft.net can't TLS handshake to this)
- cdn.botframework.com (azure.microsoft.com can't TLS handshake to this)
- launcher.mojang.com (Minecraft Launcher tries to do update check before showing UI but can't so it doesn't show the UI at all)
- js.monitor.azure.com
- s-part-0028.t-0009.t-msedge.net (commonality across all of these)
When trying to load over HTTPS in the browser, client apps (Visual Studio Code, Minecraft Launcher, etc...) or even via cURL in the terminal, it hangs in the middle of the TLS handshake:
Code:host [~]$ curl -Lvk6 https://s-part-0028.t-0009.t-msedge.net * Host s-part-0028.t-0009.t-msedge.net:443 was resolved. * IPv6: 2620:1ec:bdf::56 * IPv4: (none) * Trying [2620:1ec:bdf::56]:443... * ALPN: curl offers h2,http/1.1 * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):
And when using plaintext HTTP, it hangs while waiting for a response from the server:
Code:host [~]$ curl -Lvk6 http://s-part-0028.t-0009.t-msedge.net * Host s-part-0028.t-0009.t-msedge.net:80 was resolved. * IPv6: 2620:1ec:bdf::56 * IPv4: (none) * Trying [2620:1ec:bdf::56]:80... * Connected to s-part-0028.t-0009.t-msedge.net (2620:1ec:bdf::56) port 80 * using HTTP/1.x > GET / HTTP/1.1 > Host: s-part-0028.t-0009.t-msedge.net > User-Agent: curl/8.14.1 > Accept: */* > * Request completely sent off
Strange part: if you use cURL and it hangs at first, cancel it and immediately run cURL again - sometimes it will actually successfully load and work for a short while after that. And then break again.
I don't know where the issue lies - with Afrihost or with Microsoft (or somewhere else) - but this has been broken for quite a few days![]()
I've also been experiencing the same issue when trying to access Microsoft services even `portal.azure.com` does not work for me
Not sure if anybody else have been having issues
Hi.I've also been experiencing the same issue when trying to access Microsoft services even `portal.azure.com` does not work for me
Not sure if anybody else have been having issues
This is on openserve with Afrihost as the ISPHi.
On which FNO?
Let me try that. What did you set the MTU as for reference?This sounds like its very likely MTU related, I had tons of issues with Microsoft related sites when I turned on IPV6 with CISP, only to realize I forgot to set the MTU lower.
Let me try that. What did you set the MTU as for reference?
Seems like setting it to 1450 work.
Hi.I'm down in Capetown Northern suburbs looks like the same thing we had about two weeks ago
I can tell you it's not suspected it is outHi.
We are putting up a notice, suspected outage.
Just went down here in Durban. Restarted router and ONT, back to normal.Hi.
We are putting up a notice, suspected outage.