Afrihost - Pure Fibre Feedback Thread

Status
Not open for further replies.
Hi there anyone having issues with news server downloads all my stuff seems to stuck at 99% no matter what I grab and I have multiple providers.
 
Hi there anyone having issues with news server downloads all my stuff seems to stuck at 99% no matter what I grab and I have multiple providers.

What NZB client are you using. It could be the client that is having issues or the articles are missing from the usenet servers and unable to complete.
 
Is there any Afrihost/Frogfoot issue in the Cape Town southern suburbs? Our area has been down for about the last 30min, with no posts up on the status pages.

My router flipped to my Afrihost data SIM card at 13h19
 
Is there any Afrihost/Frogfoot issue in the Cape Town southern suburbs? Our area has been down for about the last 30min, with no posts up on the status pages.

My router flipped to my Afrihost data SIM card at 13h19

Hey,

Yes there is currently an outage.

Dear Frogfoot Customer,

Please be advised of the following network outage:


Outage ReferenceFRG3033228
Outage TitleOutage | CPT | Cape Town Southern Peninsula | Partial
RegionCape Town
AreaSunnydale, Wynberg, Noordhoek, Fish Hoek, Blouberg
Precincts Affected
Incident Start Date2022-08-03 13:19:00.0
Outage StatusResolution In-Progress
 
Hi. There seems to be a problem in Lenasia. This morning around 8 to 8:20 the openserv fiber was down. Came back up and now it’s back down. I am from the Lenasia area. Can afrihost please look into this
 
Hi. There seems to be a problem in Lenasia. This morning around 8 to 8:20 the openserv fiber was down. Came back up and now it’s back down. I am from the Lenasia area. Can afrihost please look into this

Hi,

There is an outage affecting clients in Lenasia.

Openserve has a network fault logged for the outage already. No ETA currently.
 
AH fibre just die completely? swapped to Cybersmart pppoe and all is fine. Could not traceroute beyond AH's network now.
WCape
 
Not seeing any drops in the graphs. Do you have an example trace for me?

swapped back and its still dead so i'm on CS now again

this was to 1.1.1.1


Code:
 2  gateway.lan (192.168.88.1)  2.490 ms  1.935 ms  1.933 ms
 3  router.lan (192.168.0.1)  2.965 ms  2.962 ms  2.850 ms
 4  * * *
 5  165-73-14-113.ip.afrihost.co.za (165.73.14.113)  8.428 ms 165-73-14-137.ip.afrihost.co.za (165.73.14.137)  7.843 ms 165-73-14-113.ip.afrihost.co.za (165.73.14.113)  8.422 ms
 6  169-1-21-132.ip.afrihost.co.za (169.1.21.132)  6.924 ms 169-1-21-148.ip.afrihost.co.za (169.1.21.148)  8.530 ms  8.508 ms
 7  169-1-21-133.ip.afrihost.co.za (169.1.21.133)  8.205 ms 169-1-21-132.ip.afrihost.co.za (169.1.21.132)  5.062 ms  5.052 ms
 8  169-1-21-133.ip.afrihost.co.za (169.1.21.133)  4.272 ms 169-1-21-86.ip.afrihost.co.za (169.1.21.86)  4.262 ms  8.855 ms
 9  169-1-21-86.ip.afrihost.co.za (169.1.21.86)  4.019 ms 100.64.80.54 (100.64.80.54)  5.032 ms  8.822 ms
10  100.64.80.54 (100.64.80.54)  3.819 ms 169-1-21-86.ip.afrihost.co.za (169.1.21.86)  4.237 ms  8.317 ms
11  169-1-21-86.ip.afrihost.co.za (169.1.21.86)  3.994 ms 169-1-21-87.ip.afrihost.co.za (169.1.21.87)  8.796 ms 169-1-21-86.ip.afrihost.co.za (169.1.21.86)  4.927 ms
12  169-1-21-87.ip.afrihost.co.za (169.1.21.87)  5.470 ms * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
 
swapped back and its still dead so i'm on CS now again

this was to 1.1.1.1


Code:
 2  gateway.lan (192.168.88.1)  2.490 ms  1.935 ms  1.933 ms
 3  router.lan (192.168.0.1)  2.965 ms  2.962 ms  2.850 ms
 4  * * *
 5  165-73-14-113.ip.afrihost.co.za (165.73.14.113)  8.428 ms 165-73-14-137.ip.afrihost.co.za (165.73.14.137)  7.843 ms 165-73-14-113.ip.afrihost.co.za (165.73.14.113)  8.422 ms
 6  169-1-21-132.ip.afrihost.co.za (169.1.21.132)  6.924 ms 169-1-21-148.ip.afrihost.co.za (169.1.21.148)  8.530 ms  8.508 ms
 7  169-1-21-133.ip.afrihost.co.za (169.1.21.133)  8.205 ms 169-1-21-132.ip.afrihost.co.za (169.1.21.132)  5.062 ms  5.052 ms
 8  169-1-21-133.ip.afrihost.co.za (169.1.21.133)  4.272 ms 169-1-21-86.ip.afrihost.co.za (169.1.21.86)  4.262 ms  8.855 ms
 9  169-1-21-86.ip.afrihost.co.za (169.1.21.86)  4.019 ms 100.64.80.54 (100.64.80.54)  5.032 ms  8.822 ms
10  100.64.80.54 (100.64.80.54)  3.819 ms 169-1-21-86.ip.afrihost.co.za (169.1.21.86)  4.237 ms  8.317 ms
11  169-1-21-86.ip.afrihost.co.za (169.1.21.86)  3.994 ms 169-1-21-87.ip.afrihost.co.za (169.1.21.87)  8.796 ms 169-1-21-86.ip.afrihost.co.za (169.1.21.86)  4.927 ms
12  169-1-21-87.ip.afrihost.co.za (169.1.21.87)  5.470 ms * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *

Everything or just to 1.1.1.1?
 
swapped back and its still dead so i'm on CS now again

this was to 1.1.1.1


Code:
 2  gateway.lan (192.168.88.1)  2.490 ms  1.935 ms  1.933 ms
 3  router.lan (192.168.0.1)  2.965 ms  2.962 ms  2.850 ms
 4  * * *
 5  165-73-14-113.ip.afrihost.co.za (165.73.14.113)  8.428 ms 165-73-14-137.ip.afrihost.co.za (165.73.14.137)  7.843 ms 165-73-14-113.ip.afrihost.co.za (165.73.14.113)  8.422 ms
 6  169-1-21-132.ip.afrihost.co.za (169.1.21.132)  6.924 ms 169-1-21-148.ip.afrihost.co.za (169.1.21.148)  8.530 ms  8.508 ms
 7  169-1-21-133.ip.afrihost.co.za (169.1.21.133)  8.205 ms 169-1-21-132.ip.afrihost.co.za (169.1.21.132)  5.062 ms  5.052 ms
 8  169-1-21-133.ip.afrihost.co.za (169.1.21.133)  4.272 ms 169-1-21-86.ip.afrihost.co.za (169.1.21.86)  4.262 ms  8.855 ms
 9  169-1-21-86.ip.afrihost.co.za (169.1.21.86)  4.019 ms 100.64.80.54 (100.64.80.54)  5.032 ms  8.822 ms
10  100.64.80.54 (100.64.80.54)  3.819 ms 169-1-21-86.ip.afrihost.co.za (169.1.21.86)  4.237 ms  8.317 ms
11  169-1-21-86.ip.afrihost.co.za (169.1.21.86)  3.994 ms 169-1-21-87.ip.afrihost.co.za (169.1.21.87)  8.796 ms 169-1-21-86.ip.afrihost.co.za (169.1.21.86)  4.927 ms
12  169-1-21-87.ip.afrihost.co.za (169.1.21.87)  5.470 ms * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *

Looks like it was related to the nat static.

There were more than 1 active session on the radius causing the issue. Should be sorted now.
 
Looks like it was related to the nat static.

There were more than 1 active session on the radius causing the issue. Should be sorted now.
before it happened the DIR-825 stopped responding, could not reach it / ping it so I rebooted it.
 
before it happened the DIR-825 stopped responding, could not reach it / ping it so I rebooted it.

Yes that would have caused it. The session had to time out first before the new one started. Since nat routing will still go via the old session so the new IP's traffic won't go past the nat box.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X