Skipperblogs status

Real-time information on system performance and availability

All systems are operational

Past Incidents

Tuesday 1st August 2023

AIS False status of the AIS system

After the major update of the core application, the status of the AIS tracking system was reporting a Partial Outage of the system. Actually the system was and is working properly but the miss reading of this system status was due to an error of the self-test function.

Sunday 12th March 2023

Support Support server update

We are updating the support server, but the operation takes longer than usual. This impacts support tickets submission via Skipperblogs dashboard but not tickets via e-mail. We are working on putting the service back up.

  • We were able to finish updating the service and put the server back online. The support service is operational. The outage lasted about 20min during which no ticket we're submitted or lost.

  • Saturday 15th October 2022

    Frontend Websites Incident on Skipperblogs subdomains websites

    We have an issue with the SSL certificate running for subdomains. Some websites are unavailable for the moment. We are investigating.

  • We are sorry. Earlier today between around 10:50UTC and 11:50UTC the main server running Skipperblogs websites failed in a routine work. We have identified that the automatic renew for sudomains SSL certificates had a bad configuration and could not renew the certificates for certain websites.

    This lead to several websites to be inaccessible for about 1 hour displaying a error message when trying to connect to it. We will set up a monitor to watch this routine task. This way we can be notified more quickly in case of a problem.

    We apologize deeply for the interruption you had today. Now — back to making the service even better and more stable than ever.

  • Tuesday 13th September 2022

    Core application Authentication problem

    During the last core application update, a problem disrupted the authentication system and it was not possible to log in the dashboard. A cookie name configuration for the session was wrong. The interruption lasted about 30minutes and the issue is now solved. I'm really sorry to have hold you up today!