Maybe someone needs to fix their cron? Same as yesterday logging a ticket for this crap.
Ticket Created #COOL-20260205-2592395
Edit:
and magically back after the odd 30 to 60 mins like other two incidents.
Event one:
Tuesday: config regression - Tuesday at 6:56 AM
From netops:
Looks like a config regression on OpenServe's side, L3MTU at 1500.
I got our AM on the tech's to fix it ASAP
Underlying issue fixed by Openserve, should all be back to normal. Please test and let me know.
Event two:
Openserve has confirmed the incident with Reference 170ATK040226 - Wednesday at 12:45 PM
OS dying again? Line just dropped.
We are getting more reports, and will reach out to Openserve to investigate further
Openserve has confirmed the incident with Reference 170ATK040226
Announcement Link:
https://coolideas.co.za/announcements/75819
Affected areas will be updated once we know more
Event Three:
Same as previous two - auth loss, pado packets, line drop (see below)
Openserve has confirmed the incident with Reference 170ATK040226
Announcement Link:
https://coolideas.co.za/announcements/75819
Affected areas will be updated once we know more
Maybe someone needs to fix their cron? Same as yesterday logging a ticket for this crap.
Ticket Created #COOL-20260205-2592395
Edit:
and magically back after the odd 30 to 60 mins like other two incidents.
Event one:
Tuesday: config regression - Tuesday at 6:56 AM...