Major service disruption

About this page

If you experience any technical difficulties, please bring them to my attention at pihole[@]freek[.]ws. I will troubleshoot to fix any issues that may arise as soon as possible. Thank you.

  • pihole-nl.freek.ws (185.147.34.122)

    Major Outage
  • pihole-uk.freek.ws (185.187.240.11)

    Operational

Ongoing Incidents

  • Pi-hole NL down

    Lasted for 3 months
    Affected Service: pihole-nl.freek.ws (185.147.34.122) May 12, Sat

    Investigating
    Pi-hole NL is currently down, I will investigate the matter.

    08:32, May 08 CEST

    Investigating
    This is taking a little longer than expected. I've opened a forum topic at the Pi-hole forums to get support. You can track it's status here:
    https://discourse.pi-hole.net/t/pi-hole-not-serving-requests-over-ipv6-remotely
    In the mean time I recommend disabling Pi-hole NL and solely using Pi-hole UK for now.

    20:47, May 12 CEST

Recent Incidents

  • Affected Service: pihole-nl.freek.ws (185.147.34.122) April 12, Thu

    Investigating
    Again, there are intermittent connection issues to pihole-NL (*sigh*). This is starting to look like a recurring event in my calendar. Again, it looks like it's being caused by the provider, as the node is unreachable from any control panel. I keep you guys posted.

    12:28, Apr 06 CEST

    Fixing
    Reply from hosting provider:

    "Hello,

    There is a problem with the network switch, upstream are working on it.

    Thanks"

    17:08, Apr 06 CEST

    Identified
    Update by provider:

    Dear Customer,



    We are aware of a network connectivity disruption affecting our Netherlands location. We are trying to determine the cause of the issue and are working with our upstream provider.



    We have limited insight at the moment and there are delays with communication. We apologize for any inconvenience caused.



    Please stand by for updates.



    Thank you,

    23:28, Apr 06 CEST

    Resolved
    Switch seems to be have replaced, no response from provider. Closing this for now. Let's hope for the best.

    13:19, Apr 12 CEST
  • Affected Service: pihole-nl.freek.ws (185.147.34.122) April 04, Wed

    Investigating
    I've been observing some intermittent connection issues to the NL resolver again. This time, it looks like it's being caused by my hosting provider. Stay tuned for further updates.

    14:15, Mar 31 CEST

    Update
    Look at this graph: https://i.imgur.com/eAgSqAP.png
    Something's funky, but I don't know what it is yet.

    14:28, Mar 31 CEST

    Identified
    The response of my hosting provider is as follows:
    "Thank you for the info. We are aware of intermittent connectivity issues in the Netherlands and are working with the upstream provider to resolve this."
    I.e. the issue is not on my side/out of my hands. I keep you guys posted.

    16:57, Mar 31 CEST

    Monitoring
    Reply from hosting provider:

    "Hi,

    At this time it seems the issue is resolved as we have not observed any further packet loss, but there is no update from the upstream yet.

    We will continue monitoring the situation."

    19:34, Apr 01 CEST

    Resolved
    Closing this incident as the upstream issues seem to be resolved. No confirmation from provider though.

    13:13, Apr 04 CEST
  • Affected Service: pihole-nl.freek.ws (185.147.34.122) March 14, Wed

    Monitoring
    I've been observing some intermittent connection issues to the NL resolver. The last time this took place was between March 9th at 00:29 AM till 02:40 AM. During this time period, the server itself was up but the webinterface was not responding to requests. I am unsure whether or not DNS requests are also affected, hence I have put more logging in place. I will be monitoring this over the course of this weekend.

    11:05, Mar 09 CEST

    Identified
    Currently the webinterface is unreachable again. I've identified the issue and will work on resolving it asap. DNS service is unaffected and remains operational.

    19:08, Mar 10 CEST

    Resolved
    The changes I made seem to have resolved the issue, therefore I am closing this incident.

    13:13, Mar 14 CEST
  • No incidents reported